>Hi Erik,
>
>Just wanted to throw out a wild guess.
>
>What if you renamed all the existing tables and pre-pended them with 't_', also rename the orig. .dbc add a 't_' also. Now create a new .dbc (same name as the original, add a connection that uses ODBC to point to the original tables, and create a remote view for each table using the original table names.
>
>so MyDbc becomes t_MyDbc
>so MyTable becomes t_MyTable
>then make a new MyDbc and a remote view called MyTable.
>
>You could trick the forms into using the remote views instead of the tables. As long as the forms use tableupdate / revert it might work.
>
>I know there will be alot of places where you could have problems, just wondering if maybe it could provide a temporary solution.
>
>Stephane- This s a SWAG, I'm not saying it will work, and don't even know if it is completely plausible. As both Erik and Ed have said, there is probably no magical cure. I'm just throwing it out to get some input.
>
>You may want to look at http://msdn.microsoft.com/isapi/msdnlib.idc?theURL=/library/periodic/period99/html/ft99d1.htm for some ideas of how to architect a C/S solution that uses both VFP and SQL back-ends..


Thanks, that is exactly what i was planning to do at first, create a remote view of all my tables, then run upsizing wizard. But i guess i have a *bit* of reading to do before i even start...

Yes all the forms use TableUpdate() ..Revert() etc.. And of course, i will have to modify my data access classes to fetch records the C/S way. But i want to do this the right way so if anyone has recommendations before we start, i will be happy to consider all of them.

Tanks a lot.