>There are two issues here on one of which I can offer no advice. The first is actual CPU load in VFP which is not something you can change. If VFP hogs the CPU on a single command (SELECT or REPORT) you're stuck with that behavior. No way around it really. Offloading to SQL Server should help here as VFP just sits idly waiting for a remote SQL command to process. However, fi the SQL Server is on the same box you may still have issues with CPU loading although SQL Server is configurable of how much CPU it can hog...

Cool. Thanks for the info. Between optimizing the queries and offloading to SQL Server, this should be the trick.

>The other issue is that of VFP going to 100% calling another component as you mentioned.

Actually it wasn't having VFP call another component, but have the C# component (that calls the VFP COM) do more of the work. From what I have observed, a C# class in ASP.NET that does a lot of work, doesn't try to hog the CPU like VFP does.

Thanks a ton for your time.