>>I was wondering if anybody ever created a project with database split between VFP and SQL Server? How practical it was? Any problems?
>>
>>I want to start converting a very large application from VFP 6 VFP DB to VFP 9 and SQL Server. But I realize the magnitude of the project will be too big to accomplish in reasonable time. So I am thinking about an approach of moving only one table to SQL Server. This is a very big table (of about 300,000 records) that often gives me problems (corruptions). Then, I could move other tables of the application to SQL Server, one step at a time.
>>
>>Any suggestions or warning will be greatly appreciated.
>>
>
>That is possible. Even when we use SQL Server, we continue to use DBFs for local metadata. Of course, you'll have to make the necessary changes for a client/server environment, but that's the subject of an entire book (
http://www.hentzenwerke.com/catalog/csvfp.htm). As a side note, VFP 9 offers better detection of corruption than VFP 6, but you will still need a tool (Stonefield, FoxFix, Recover, etc.) to repair it.
I do use SDT and Foxfix but it is good to know that VFP 9 has even more built-in stuff.
Thank you for your input.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
