>>Hi again John - trust you got my previous message about updating the runtime.
>>Now, I've read the rest of the thread and I don't have a solution - but for whatever reason it sounds like VFP has decided internally (at the user machine level) not to optimise the query on those user machines. I've seen that happen from time to time on large data files. The differences in query time are too big to put it down to network performance, NT vs Novell and all that stuff.
>>
>>Ok - that's not much help, but then, it just could be the version of Foxpro, as you suggested; it is consistent with the difference between machines. Has the data size been increasing? Are there lots of deleted records building up in any of the tables. In my experience, deleted records are notorious for turning the optimiser mechanism off completely and Fox does a sequentially search/join resulting in *huge* temp files.
>>Lotsa luck
>
>
>Hi David, or I should say "Master David".
>
>I haven't created a new net setup yet but I did manually move the runtime dlls over to one of my test production machines and VIOLA!! my once 10 minute plus select statement is now less than 1 second! and that is on an old 486 running NTServer 4.0. I haven't fully tested my app, but it looks like you nailed that one down for me. This has definitely been a learning experience for me. I'll re-create the net-setup as you suggested after clearing the other files and have all of my users run setup again and I should be in business. I can't tell you how happy I am to see this problem go away.
>
>Have a great weekend, and I'm sure I'll talk to you again soon.
>
>Many Thanks,
>
>John.

Real glad that helped John. I can imaging your relief.

BTW... "VIOLA" (sic) - thought that was an Australian play on words :-)
"Voila" is too cultured and wimpy sounding so we often say "Viola" 'round here. LOL.
Regards