Hi Kev,

>Will it be much of a headache to reference these (new) tables alongside the VFP database? I'm thinking of using Remote Views in place of the Dos tables.

To directly answer your questiton < g >, no, it should NOT be much of a headache to reference these (new) tables alongside the VFP database.

The data access and updating code you're using for the Fox4Dos tables is going to have to be rewritten. I'm not a huge fan of Remote Views, oh they work, but they have their weaknesses.

I'd advocate a more OOP approach to accessing and updating the SQL Server data utilizing a middle-tier business objects. That object handles the connecting, retrieving, updating, and deleting of the data by calling stored procedures on the SQL Server.

SET BLATANT MARKETING ON

You might want to checkout DataClas/VFP. It does EXACTLY what that paragraph above states. It is a data class written completely in VFP. For more info, check out www.redmatrix.com

SET BLATANT MARKETING OFF

If you go the RV route, you'll still will be rewriting quite a bit of code including code for TABLEUPDATE(), TABLEREVERT() and so on.

Hope this helps.