Thanks Jim. I'll try EXE.
FWIW the asserts are turned off.
>Mark,
>
>Presuming this to be the same app as the previous discussion. . .
>
>Have you tried running it as an EXE?
>
>Are you running with *ANY* debug stuff running (like Coverage or Asserts)?? If so, try turning that stuff OFF.
>
>While of course things like you describe should not happen in *any* mode of running, running as an EXE should certainly change the internal environment such that CASE statements cannot be tampered with and the like. I would trust "high volume" production much more in a EXE than in a .APP or the like.
>
>Good luck,
>Jim N
>
>>>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.
>>
>>>>Has anyone had experience with a VFP-SQL 6.5 getting slower
>>>>as a process carries on? I have a process that was taking
>>>>24 hours and is now taking 40+. CPU usage has gone from 40-50%
>>>>to 85-100% yet memory remains at 80-100k.
>>>
>>>1. If you shut down the application and re-start, does it speed back up? What about the workstation if you reboot?
>>>
>>>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.
>>>
>>>3. Was that CPU utilization on the VFP machine or the SQL Server machine?
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only