Kevin,

Check the report itself. It will consume the cpu largely. Well, that's the only thing I can think of. Run the report on a normal PC, and check the cpu useage there.
And I wonder, what lengthy reports do you have ? several thousands of pages ? I mean, each report of 100 pages or so, should be finished within a sec or 2, of course depending on the "calculations" the report does. So when your 100 page report takes minutes, something is doing too much in there, or ... it is just necessary. Well, all resource consuming stuff obviously should not be on a WTS-like. And don't blaim VFP for being greedy with system resources, because to my experience it is not. But know what you do, and you may be greedy ... ;)

HTH

Peter





>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