>What would cause a query to take less than 3 seconds on the developemnt computer and yet greater than 3 minutes on the user's computer? I'm running VFP 5.0---Windows NT on the server and Windows95 on the client.

The other guys are right about there being not enough info to answer... but.

Assuming that you're network connection is fast (10baseT or faster) and you're query is optimized then you might be having the same problems I've been having. I'm running Win95 OSR2 (P2 400 w/64M RAM), VFP5 and a Netware 4.11 server (Intranetware client).

You should use the GlobalMemoryStatus API function to see how much memory Win95 says is available. My machine, when completely idle, will report that I only have 2-3M of memory free. VFP will default to 40M.

What I've found is that Win95 will not free memory to VFP until VFP has tried to use more then the 2-3M. Large queries will hit the machine hard and free the memory, but not until after VFP has been slowed. If you set VFP to the available 2-3M first (using sys(3050)) then you're query will be faster.

I only noticed this behavior when I received my new machine. My old machine was a PPro 200 running NT Workstation 4. My client, on a new Win95 box, noticed it also. As have all the Win95 users in the building. NT handles memory completely different.

paul