>>John,
>>
>>This fits in the category of a real wild guess, but you sound like you'd take *anything* at the moment, so here goes. . .
>>
>>This sounds a lot to me like there are *NO* indexes, thus the slowww performance *and* the large TEMP file creations. Yes, I know you have indexes!
>>BUT. . . there have been reports of index files *NOT* opening (ie the PRODUCTION .CDX fails to open) when a .DBF is opened *WITHOUT* reporting any error!!! This in a NT environment, and I *don't* know if it is documented in any way by MS.
>>At least one of the reporting persons advised that he seemed to have circumvented the problem by upping the maximum number of files allowable. I (sadly) don't know what was adjusted to to this, only that it was done and the incidence of trouble seemed to disappear.
>>
>>So I would look at your User machines (or their NT settings, if such things exist) to see what the differences might be from your "test" machine as far as maximum files permissible is concerned.
>>
>>Wishing you good luck,
>>
>>Jim N
>>
>
>Thank you Jim,
>
>Your post is greatly appreciated, and yes I need lots of luck!!
>
>John.

FYI - set the user files to 180. It usually enough to handle any Fox/Sql app. Also you may want to make sure that (if your files are on a server) that all the permissions are set correctly. I have 2 vfp apps on my network at the office. One app is on a Novell 3.12 server and the other is on Nt4 Server. If your app is running off the NT server you may notice a *big* decrease in performance in speed. The app on the Novell server runs twice as fast as the same app on NT.. Also( I think this is still relevant) make sure that the total files that a user can have open doesn't exceed 255. So if they can have 100 on the server make sure that the local machine has no more that 155. I had some of my users have problems when the total was over 255.