Do you have administrator rights on the Novell server? If so, create a new user that has the same rights as one of the manager accounts that works well and see if the results are the same speedwise. Novell is an excellent network OS and can be controlled in many ways that W2k cannot. You may have controls put in place for auditing, tracking, tracing, etc user accounts that is slowing it down. The rights and working location on the server may be different too. What is the working directory of the different user accounts? Are the temporary files location on the same server? If not, check the purge setting on the Novell volumes being used. It needs to be tested with users that have the same network rights, working locations, as well as within the app itself to separate the two issues.

Tracy

><
>When you say 'logging in as' do you mean logging into the 'app' as a specific user, logging into the 'domain' as a different user, or a specific server, workgroup, or what specifically? Is it a W2k domain, Novell, Window NT, Windows 98 workstation and Windows 98 peer server, etc?
>>
>
>- Yes, I mean logging into my application using different usernames & pwds
>- Test is on a WIN2K, Novell
>
><
>IN other words, what specific workstation, server, and network are you testing on? According to your statement below, you used the SAME workstation for testing and the data resides in the same location regardless of user (right?), so the only difference was the username and any account differences, correct?
>>
>
>- The data is in central location and not on the individual PCs
>
><
>Also, if it is filtered by mgr versus employee etc, the wouldn't manager accounts pull more records?
>>
>
>- Yes the MGR sees more records and yet it is slower for the employee than the MGR.
>
>>In production this might vary. But we were doing the tests on the same machine, logging on as different users each time.