Kevin,

Make your application set SYS(3050) to something sensible. We do this at the top of Main.PRG, in the first 5 lines of code.

If you don't do this, then any VFP session can potentially take as much server resources as it can...

**--** Steve

>Hi, all...
>
>We have a VFP 6 reporting application running on a server, where approximately 7-8 remote users access the application through Terminal Server (under Windows 2000, SP2). If I go into Terminal Services Manager, the license is for MetaFrame 1.8 for Win2000 for Workgroups.
>
>The Server is a screamer, with a ton of disk space and about 1 GB of memory.
>
>The users are complaining of extremely sluggish performance anytime one user is running a report. They are stating that CPU usage on the server is close to 100% when one user is running a lengthy report, and that others see the application slow to a crawl until the first user's report has completed.
>
>Not that I would think this would be related, but we have tried the SYS(3050) trick, with no noticed affect.
>
>I know that VFP is greedy with system resources, but I've never seen anything like this. Is there any way (either through Terminal Server or VFP) to keep a VFP app from taking (or at least 'appearing to take') over total control of the CPU?
>
>Any clues?
>
>TIA,
>Kevin