>What's wrong with VFP? Three words: NO FAULT TOLERANCE.
>
>I just spent the last four hours (and counting) putting out fires for our in-house project tracking system (written by me in VFP, of course) resulting from our network server going down and corrupting several VFP files.
>
>1) CDX files got corrupted
>2) Bad data got commited to critical tables (primary key counters, etc.)
>3) Data was lost forever (barring any backup tapes)
>4) Error messages were misleading.
>
>Does anyone have a good cure for the old network going down while users are writing to VFP tables problem? Until Microsoft comes up with a better solution for fault tolerance VFP will never get the respect it deserves.

Our vfp server data is actually quite resilient, I'm continually surprised to find it in good shape after network problems. We've had at least as much trouble with other server files, notably Excel, Access, & Word. CDXes are usually the first thing to go for us here, but those are easily enough replaced. But we make nightly tape backups, that's the bottom line even with SQL Server here, you've got to maintain a thorough backup system...