Sounds interesting, SQL is not always needed, VFP does a great job on LAN's; but it is always good to thinking ahead in the design phase and maintain flexibility and options. Good Luck...

Bob

>Actually, I am partway into that very process. I am working on a redesigned structure for a VFP application that was a conversion from another older DOS database etc..
>
>The data model was not normalized very well in the old system. That is partly due to limitations of the language used to write the application back then. I hestitate to speculate about the other part. <g>
>
>The 1st VFP rewrite I did 2 years ago was without significant database redesign. This is due to my losing numerous internal political struggles at the time, and nothing else. <g>
>
>Now, I'm working with a failed, aborted project started in VB/SQL 7 by contractors last year that has been dropped in my lap. This contained a good database model, but not much of anything else. What I have done is to transfer this newer model back into a VFP database, so I can make a working application without worrying about SQL Server just yet. I am of the opinion that, when properly designed, this database may not need to go to SQL Server. It is not that large, in terms of the numbers of records the tables contain, and the database has maybe 70 tables.
>
>>Should optimize very well and gives you additional flexibility because you can mix and match the columns plus it will make it easier if you ever need to move to SQL7!
>>
>>Bob
>>