Hi Stephane,

I've done a couple of conversions from 2.6 to client/server using VFP to Oracle and MS SQL Server. I used a framework to build the VFP interface. Using a framework gave me a big headstart in rebuilding all my data entry screens.

I use parametized views of tables that are constantly changing and I download static tables to VFP local lookup tables. This makes the interface very quick. Having local lookup tables, I was able to salvage a lot of the data validation code from 2.6. I didn't have to rewrite all that business logic in SQL stored procedures.

Also I download data to VFP temporary tables to do any complex calculations. Using the downloaded tables I found that I was able to salvage a great deal of my 2.6 code that handled business calculations and specialized reports.

I found that this combination of a framework for the interface and downloaded VFP tables to salvage some 2.6 code worked very well in migrating to a client/server environment.

Good luck,

Paul



>Hi all
>
>We have an application using about 600 tables in a VFP6 database, our app for the most part is not using views of the tables to access data but tables in the DE.
>
>So by all meen, SQL upsizing wizard will not work in our case. Our application pretty large (400 forms, 100 Progs, reports, etc..) It will take a lot of work to convert all manually. We fist developped this app converting Fox 2.X App and choose this approach to avoid full rewrite of the biggest prgs (with no user interface)
>
>All the table update functions are handled by one class and we are use private data session (5).
>
>Basicly, i need some suggestions on what would be the best approach to start converting this app into an SQL Enabled app without have to rewrite everything.
>
>Thanks.