>>Hi all. I am using VFP 3.0 for Windows.
>>
>>I am starting a project in VFP that will likely move to client/server within a year or two. I would like to develop the app so that I will have to do little or no work when it comes time to move from simple VFP tables (and databases) to tables in either Oracle or SQL Server.
>>
>>Can anyone give any pointers on this subject? Is it.. (choose all that apply)
>>
>>a) Simple, just use the upsizing wizard
>>b) Minor code changes
>>c) A really big change, but doable
>>d) requires the use of ODBC which will slow down the app
>>e) a really stupid idea
>>f) boy you are naive, I can still see the turnip truck your fell off of
>>g) there is an excellent book on the subject it is ______________
>>h) all of the above
>>i) none of the above
>>j) both e and f
>
>I feel like I'm still a novice at this, but...when I create an application that I know will eventually be using SQL Server I do the following:
>
>1. I create a DBC that contains all my tables and data
>2. I create an ODBC connection to the visual foxpro data
>3. I create my application using a connection to this ODBC and remote views
>4. When I upsize, I use the upsize wizard only on the DBC with the tables and data, and do not create views, etc; I only upsize the tables and data.
>5. The only change I need to make to my application is to the connection.
>
>For my first application I created the entire application using local tables. The upsize wizard didn't help much, I had to redo a lot of code.
>

Jeff,

Thanks. That was the answer I was looking for. Concise and field-proven.

A couple of questions, if you have time.

1) Is there a speed penalty when using ODBC is this way?
2) Do you know if your solution is applicable to other backend dbs like Oracle?
3) What do I gain by using SQL server over VFP tables? Am I reducing the network traffic? It seems that SQL Server will allow much larger table sizes. If there is a whitepaper on the subject, could you let me know?

Thanks Jeff.