Another way to approach this if you are more comfortable with working with VFP is to have a VFP Report Server. This would be a standatd PC where you would have a VFP program running and waiting for a report request (I just add records to a table, but there are many ways to pass the request) The program would run the report and output it to a common printer, or a PDF, or whatever. It would then pass back a reference to the result (again I just populate a field with the PDF file name) This works well for printing as well. The user request a report, their machine is available to continue working, the report prints to the printer (PDF), and the user is notified. This is also nice since only 1 computer needs the printer drivers, pdf generator, fonts, etc. We use the same server to do background maintenance processing, emailing, and faxing through VFP.

Bob

>I am using SQL Server 2005. I am using Cursoradapter/ODBC, but could change that. I don't want to open cursors and process a complicated report on the Client system.
>What would be a good way to process a VFP report on the server and then pass only the resulting cursor back to the client?