>>I'm beginning a migration of our application from using VFP tables to using SQL Server. Rewriting the biz objects isn't too difficult since I've got some basic table insert/delete/update code. I've got a lot of report code though that for speed reasons, accesses the VFP tables directly to pull data. How can I minimze the changes to the report code when migrating to SQL Server 2005? Can I create a FoxPro remote view on the fly at the start of each report, that references the SQL tables, then from then on the code thinks it is accessing VFP tables?
>
>Yes you could but wouldn't SPT or ADO (CA) be better?

Is a remote view to SQL Server data on the same box, about as fast as SPT?

My fear with SPT is that the SQL synatx is different and more restrictive.

>VFP reports don't care about actual source as long as they can evaluate expressions (hope you don't mean you used tables in report DE and/or aliased field expressions).

I have a report object that has all of report code, then when all data retrieved into a single cursor, calls the report. Pretty typical I think.