Hi Eric,

I suppose that the network could be the problem. hard to say given the information.

VFP has the "coverage profiler" that can help you to isolate slower aspects of your application. This sounds like a good usage for it.

Are you running as an EXE? Do the workstations load the EXE from the server or from local HD?

Do the temporary files go to the local HD or are you directing them to the server (CONFIG.FPW)?

When you say slow for enquiries do you use SEEK for these or do you mean SQL-Select?

How big are the tables involved (# of records, approx)?

Again, good luck

>>Eric,
>>
>>It depends what your application does.
>>
>>But more importantly, no VFP application should get slower and slower, especially when you are talking 10-20 users.
>No? Maybe it is not the vfp application by itself, but the newtork maybe?
>
>>
>>What is a "WinServer", and what release and SP level?
>Windows server 2003 in most of the case
>>
>>Do you use lots of memo fields with lots of memo replaces in your app?
>Yes, several memo fields with replaces. But the slow problem is mostly when we make inquiries or when we load info in a form.
>>
>>What OS do the workstations use to run the application?
>Most of them are XP workstations, some Win98.
>>
>>Am I correct in assuming that you are running on a LAN (i.e. not dialup or some other option)?
>Yes
>>
>>INDEXES are the critical factor to make FAST VFP applications. Are you confident that you have good index definitions AND that your code uses those indexes?
>It is a huge application. I believe most of our indexes are ok but we may have some fine tuning there..
>>
>>good luck
>>
>>
>Thanks Jim
>>>I have some vfp8 applications that are getting slow when adding users (uses VFP database on a WinServer).
>>>
>>>I wonder what is the best situation for a 10-20 users setup:
>>>
>>>- Run the application as is on terminal service (MS or Citrix?)
>>>- Modify the application to run as client-server (with MS-SQL or MySQL?)