>>>Very good point, Jim. And a very good reason to do all current VFP development with upsizing in mind. View based applications, designed n-tier upsize very well. At this point, I think a strong case can be made that all new VFP development should be against a SQL (Express) backend. Definitely leaves more options for the future of both the app and the developer. A strong VFP app withe SQL data can be supplemented for web or tricky interface with .net modules or whatever. Best of both worlds.
>>
>>Charles,
>>
>>You are right on point. The biggest problem with upsizing, as I see it, is the mistaken idea that many developers have that it involves moving the tables from VFP to SQL Server or whatever when in fact everything from the way data is presented to the user to how the menu system works is up for review in an upsizing project.
>
>I'm not sure I understand. Why is that?

See my other reply to Denis for further discussion. Mike, my point is that moving the data and dealing with the syntactical differences is ONLY part of the task in "upsizing" an application.