drwaw: No stealth bomb here! do look at the time of posts and the responses. Also remember you cannot install AC unless you uninstall recent versions of dotnet ( other than 2.0) on a win 2000 machine..
more than 10 Concurrent connections is common in a busy office. Remember your access will be denied uncles one of the 10 who connected to the "server" completely logs off from network( not just close AC) .Often it means shutting own or re-booting a computer. Ac 4.X is painfully slow to reload ( compared to older version) .. Portions of AC may be accessed by different people (front desk, docs who keep program open in more than one room,schedulers, people verifying presc. etc.So it is really easy to exceed 10 concurrent connections. This is why we need clear directions on how to install AC on windows 2000 server , windows 2003 server or windows 2008 server.
You are going on a far different tangent. Your original statement was that AC4 would not install on a Win2K machine, which it obviously does. Now you are talking about Win2K server. I have not had a problem with reloading (?restarting) AC4.
Win 2K is not the ideal platform. I have an old machine I use for other purposes, and since it is part of the network, it needed to run AC4, it did, but that is not it's purpose, that is a secondary benefit (it is mostly for an old state vaccine program.
I would not argue that if you have a lot of machines, running a server will allow you to have more than 10 connections. We commonly have connected 3 different people in 5 different computers and have not had a lockup. Each person has their own windows logon (win xp), so while the theory of concurrent connections may be real, I suspect it is actual computers logged on.
I totally agree with Berts comments, BTW
