How easy it is depends on how your application was written. If all your data access is in local views or cursor adapter, the job becomes easier. However, if you have lots of SEEK/LOCATE or FoxPro SQL statements, the job becomes more difficult. *ALL* access to a backend server will be via ODBC. (Don't bother with OLEDB). Do you have grids that host the entire table? Get rid of that. Data queries for specific information should be used (for example, CustomerID=8783, LastName='Smith'). You'll never work with the entire table. Users don't work that way. Your application shouldn't either.
Upsizing MAY be easy too. I'd start with the upsizing wizard on VFPX. It will easily get your data into SQL Server (Express version is free). But...does each record have a unique id? How is it generated? Those are questions you need to look at.
>Hi All,
>
>I'm finally being dragged, kicking and screaming, into the SQL age, meaning I have to upsize the DB's in my app the some version of SQL, be it MS, MySQL or some other flavour. I think it was Tore Bleken that mentioned that after it's done, I'll won't look back, and I'm sure that's true. But right now it seems like a daunting task. 100+ forms, 200+ reports, 3rd party tools like Stonefield, Foxaudit, Int'l and VM Pro framework. Ugh!
>
>Anyway, how do I go about:
>
>a) choosing the right one (free is good);
>b) setting it up;
>b) converting my existing DB's, tables and views; and finally...
>c) integrating it?
>
>Is there some 'how to' available somewhere, or better still, some witch, wizard, or I'll even take an elf, that can wave their magic wand and it'll all be done for me in the morning?
>
>Thanks.
>
>Luke
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer