If you have to mix, then design with views. The views can be in the dbc, and you can mix and match vfp tables with free tables. I have to do a lot of that, and I never even mention the fpw tables in my projects (expect, of course in creating the views, but they are not in my 'free tables' list at all). When the view is instantiated, the required tables will be opened - some vfp, some fpw. Ultimately, you can begin to replace the tables behind the scenes when it becomes possible.

I've had no problems at all doing this. Believe me, views are the way to go.

Alan

>>>Surely, one-time conversion is easier, but it entirely depends on client's needs/requirements.<<
>
>Unfortunately, I want to gradually introduce the new, converted programs. Otherwise it might be the year 2000 before users can start using VFP.<g> I'm devoting only an hour a day to this conversion since I'm also the chief of my company and do programming on the side when I have time.
>
>Perhaps in my case it's better to design with free tables now, then convert to database containers later.
>
>Wouldn't having duplicate tables slow down the programs considerably when updating?