I helped write a VFP vertical market app that we sold to 700+ locations. During the 6 years that app was in production we had to run "repair" 1-2 times/year total. Not once did we lose any data. I'm not married to VFP, we've since rewritten the app in ASP.Net with SQL Server as the datastore. I just think the corruption of DBF issue is way overblown.


>How often do you have to repair them?
>
>>I wrote a POS for a "serious company" that put their "critical business data in DBFs". It's been working great for them for over two years now.
>>
>>
>>>>>Tell me it handles data as well and as easily as VFP.
>>>>
>>>>VFP handles DBFs/DBCs much better. SQL server - I definitely prefer .NET
>>>
>>>You beat me to it. And what serious company still wants to put their critical business data in DBFs?
>>>
>>>I have been using SQL Server as an application developer for years now but in my new gig we are using it far more extensively than I have before. EVERYTHING is done in stored procedures (or triggers or constraints) I will probably be ramping up for a bit with scripts -- shhh, don't tell the client ;-) -- but at the end of this project I will be much stronger in SQL Server than I am now.
>>>
>>>Here is today's local color. On the way back to the hotel after work I decided to check out some local radio stations. The rental car has Sirius and I had been listening to that. So I switch to FM and discover all six presets are on country stations, LOL. Gotta love it.
>>>
>>>Much nicer was being taken out to lunch by the account manager from the placement agency. We went to a first rate Cajun place. I love Cajun food and it is not very common around Chicago. I may be practically living on the stuff while I am down here.
>>>
>>>Back home for the weekend tomorrow night. It's been a terrific first week.