So, you have 20 open Archive batches at one time, with different Users trying to pull up new Customer Information all at once?

How many users are trying to access the same screen at the same time do you think? I would think the slowness in a specific area of the program would be directly proportionate to this number, although I cannot say for sure.

How long is the longest time you have to wait for the Customer Screen to come up? How long is the shortest time?

Your computer systems have more than enough power and memory, as does your Server. Is the Server's 30gig HDD partitioned to make it more efficient?

Is Opportunistic Locking turned OFF on the W2K Server? It should be.

Has the Server been optimized for the most efficient resource use? I will not be able to specify exactly what this would involve, as your network technician should know about these setup issues, but any and all settings to do with maximum performance over a 10 User network should be implemented.

Is there a virus checker enabled and running all the time on the Server? How about on the stations? This could drastically affect the speed of certain functions, if the processes have to wait until a vc is done all the time.

Certainly, 100BaseT would be much faster when accessing data over a network than it's predecessor, 10BaseT. I am surprised that with the technology on your workstations and Server that this was not implemented, however, I cannot say if it will help drastically or not.

It is good that you are still running Win98 on your stations though - it seems to be the most effective O/S speedwise.

Unfortunately, we do not do the install of Adagio in the End User environment - our Dealers do, so I do not know what the maximum number of users successfully installed is - and then, it is likely we would only hear of the ones that were having a problem - not successful installations!

Apart from this slowness, are you experiencing any specific problem(s) with the program functionality or operations?

There are many factors involved regarding the use of any application(s) over a network, however, accounting applications can be expected to be slower than other software, due to the many calculations required to return accurate figures. A good network technician should be aware of the necessary setup requirements in any case, especially when running Windows applications from the W2K Server.

The more important guidelines for running Adagio on an NT or W2K Server would be:
1. Make sure Opportunistic Locking is turned off (this is true for ACCPAC Plus as well).
2. All data and program files must be shared properly (ie NOT read-only or other attributes that may affect this).
3. When network rights are an issue, install the program to the Server as Admin (or having full rights).
4. Perform the individual workstation setups logged on as the actual User of that workstation (or the user of Adagio that will be using this workstation to access it). Even if you have to grant full rights temporarily, perform the setup, then change the User's rights back afterwards. This will avoid problems with printing reports.
5. Ensure that printer drivers are the most current for the version of Windows installed on the local stations.
6. Config.sys or equivalent should be set to Files = 250, especially if you also use ACCPAC Plus with Adagio.
7. You should suspend Plus in background, and any other DOS tasks.
8. In general you could look for any process that is taking CPU cycles by running Windows SYSMON utility.
9. Try to limit the number of open applications running on all stations. (ie do they really need Jukebox, Internet Explorer or Netscape, Email program etc etc running all the time while entering invoices and orders?) If the goal is production, then limit these things to ensure you are getting the most performance possible. Wallpaper on the desktop can be a big hog for display time if it's not configured properly for the desktop. JPEG files can be notorious for delaying screen-related tasks.

Hope this helps.

Regards!