>Based on that, it sounds like something in your app itself. (This is VFP 5.0, right?) Two ideas:

5.0a Sp2 on NT 4.0 WS Sp3 with SQL Server 6.5 Sp3 on NTS 4.0 Sp3.

>a) You may be opening cursors and not closing them, such that subsequent requests keep opening more and more.

I always close them with USE IN cursorname. Is it preferable to select the cursor and then USE?

>b) You may be opening connections to SQL Server and not closing them.

The SQL use in this case is all with parametrized remote views. As the view stays open and is requeried with new parameters, could this be a problem?

>>>1. If you shut down the application and re-start, does it speed back up? What about the workstation if you reboot?
>>
>>Works great if I shut the app and estart. I don't have to restart VFP.
>>
>>>2. Have you run this from a second workstation? If so and the problem doesn't appear there, it could be the network card in the first workstation.
>>
>>It''s consistent.
>>
>>>3. Was that CPU utilization on the VFP machine or the SQL Server machine?
>>The client. SQL seems fine and CPU usage is less than 1%.
>>Most of the activity is on the client.
>
>Based on that, it sounds like something in your app itself. (This is VFP 5.0, right?) Two ideas:
>
>a) You may be opening cursors and not closing them, such that subsequent requests keep opening more and more.
>
>b) You may be opening connections to SQL Server and not closing them.
>
>Maybe you could add a menu item to dump DISPLAY STATUS information (or run the app in development mode from VFP if possible).