look through VM fwk and your code if the is a central code piece and decide on remote view, cursoradapter or SQL-PT
(ask Hank here or on the VM help if you are unsure) as it is often better to go with the fwk and not against it.

Then convert your app first, still using vfp data, but disallowing/rewriting any data access not having gone through your data layer.
Then upsize - if 10GB is enough, MS SQL is a nice mesh of vfp-sql compatibility, free price and big-name vendor.

If you need larger DB, PostgeSQL for free, or DB2 if free version CPU/RAM limits are still performant or pay.
You might also look into Lianja - offers *a lot* of new possibilities like Web and Pad/Phone, but different revenue model.



>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