Hi Brenda,

Basically you will be switching from directly accessing VFP tables to using remote views. 30 tables / 60 forms shouldn't be a difficult conversion.

Some general points:
1) Create a VFP DBC with a remote view for all 30 tables.

2) When converting your forms, you can minimise the amount of work by deleting the physical VFP tables (after taking appropriate backups). Now when you open a form the form designer complains that the tables can't be found and will offer you the chance to locate them. Instead of locating the original VFP tables, select the equivalent remote views from the DBC. Each view will keep the alias from the original table so the view name can be different from the original VFP table and the form should still run. This means you don't have to change form method code or the datasource property for form objects as the original table alias is still valid.

3) If you will be changing your data structures reasonably frequently you will need a quick mechanism to update your SQL Server database without losing your existing data. Although you can script this yourself you may find it useful to consider programs such as xCase (www.xcase.com) that will help you do this.

My advice would be to try the conversion for a couple of forms and tables on a backup copy of your application and see how you get on.

Good luck.

Regards,

Aaron