Dmitry:

I have thousands of VFP applications running out there, and I haven't seen data corruption in a long, long time. Big part of the reason is that I use a few preventative programs (Abri Recover, Stonefield data tools, and a few programs I wrote myself) that take care of table header inconsistencies, index corruption etc. automatically.

Still, I have to agree that SQL express is probably the way to go in the long run, so that you don't need to fall back on these various utilities to keep things going.


Pertti

>>I agree with you 100%. If I were to start a new project today I would not use VFP tables. SQL express is the way to go.
>>
>>We haven't started new projects with dbfs since 1995. All SQL Server, Cache or Oracle. But that's not an argument against dbfs: it's a reality dictated by large amounts of data needed by multiple people with decent security and reliability.
>>
>>Not everybody has those needs.
>>
>>As for SQL Express: both of us can recite the advantages that might cause people to move that way. Both of us can also recite the maintenance, implementation and hardware issues that go along with that decision. Customers can and will weigh these things up.
>
>Your company made a smart decision in 1995. Actually I wasn't even using VFP at that time, I only started with VFP in 1998.
>
>I have over 100 customers and the databases are not very large. But I spend tons of time troubleshooting data corruption. It is such a drag on my time, I can't wait to convert to SQL or MYSQL or some other more stable database. But I would love to stay with VFP for windows apps. I have already done a couple of ASP.NET apps and for that I really like .NET.