>>We are planning to rewrite a VFP application which uses DBFs to .NET and SQL Server. The system is extremely large and is comprised of a large number of subsystems invoked from a main PRG and menu. It is not considered feasible to convert everything at once. Instead the plan is to rewrite a piece at a time as resources and budget become available. Has anyone done something like this? To me it seems like the data is going to have to reside in both VFP and SQL Server until everything is converted. Any tips on good ways to do that?
>>
>>Thanks in advance.
>
>In the case of phase after phase convert I think so in first you should convert it to VFP+SQL. With .DBF files it doesn't possible. You can convert and use your application in VFP+.NET+SQL.

What we do is a cut-off. We created a new .NET version of the entire application with DB structure changes then implement it phase by phase. If the user needs information, the VFP app is available for inquiry but succeeding data will be made available in .NET. We do hospital systems with hundreds of simultaneous users. When .NET become stable, then the migration of VFP data will take place. Another approach is to create a migration tool which can be used to migrate data to the new DB .Net. This is a little risky because the .NET is not yet stable at best which might result to data integrity compromise.