>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.
>

Do **ALOT** of reading and testing if you choose to do it this way. I can forsee bunches of problems (and I'm not that experienced at c/s apps). Like I said, this was a wild guess on my part, and I don't want to lead you down a road with no end.

As Erik mentioned in another post. In a c/s app you don't 'use' a table and work on it. You would create paramaterised views that only bring down a subset of records or a single record. Or you build an n-tier solution that works even differently than that.

By just converting your tables to views you may end up with a incredibly slow and unusable application. So read and test before you make a decision.

As far as the upsizing wizard, AFAIK it just converts your vfp tables to SQL tables and converts local views to remote views.

Again, and I can't stress this enough, I am not an expert in C/S. I was just putting the idea out for discussion. Erik and Ed (and many other people here) are by far more experienced and knowledgeable than I.