>Having done this a bunch of times in the past - what I've found works best is to use VFP remote views for everything. You can use remote views to access a VFP table, PostgreSQL table, Oracle, SQL Server, etc.. Now IF you design your tables properly - then you can use the same remote view to connect to any of these (and other) back-ends. Using VFP and want to switch to SQL Server? All you have to do is change 1 connection string ..and taadaa! Now using other back-end. I've had great success doing this - and even have a couple of applications that can run on VFP, SQL Server, Oracle, PostgreSQL, and mySQL -- all work with changing one connection string. :)

Good idea.
I was faced with the reverse issue - the potential of moving off VFP/SQL Server to another platform but staying with SQL Server.
SQL Server views and stored procedures are portable to just about any language, so I used them for all my VFP queries and updates.
Later I used them unchanged in .NET applications.