We moved our 400 table (at the time: now 530+) table to SQL with not much trouble. But we had planned for it. Everything was written in views, so the DBC could be changed out at will to a "remote" DBC.

You mention using "data objects": you can use SQL server as tables by using SPT and making the cursors modifiable, etc. Naomi will pipe in with the reference. <s>

So, a lot depends on how your app is currently written.

Hank

>We have a mature vertical market application in 150+ sites, it started in dBase and has gradually moved through to VFP9.
>
>Most (but not all) is rewritten into VFP9 OOP style with data objects being accessed from data input forms and those data objects doing the read/write. The reports are all VFP reports, based on either SQL queries to the back end data or direct reading of VFP tables.
>
>We are now experiencing major issues with;
>
>a) larger clients data slowing down due to volume of data being read across the network.
>b) issues with Server 2008 R2 (documented in other threads).
>
>Our long term plan is to move over to .Net with SQL back end (currently undergoing .Net training), but clearly that is going to take a while to complete.
>
>What I want to know is what my short term options are? Can I use the upsizing wizard and simple change my table reads to be remote views to a SQL back end? is it that simple or will that take so long to write/debug etc that I am wasting my time?
>
>Any thoughts / ideas welcome!
>
>Gary.