Jeff,

What kind of "network server"?

What are you doing that makes it go down so often?

Do you have some reasonable things in place, like UPS for Server, Server in restricted area, rules regarding hitting reset or pulling plug on workstations, etc?

I certainly agree that fault tolerance is extremely light for VFP, but with some simple steps (and, apparently, *NOT* WIN95 networking as "server") you should be able to have a nice stable system.

Good luck,

Jim N

>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.
>
>I am told that transaction processing would alleviate the seriousness of the situation. Let's hope so. I don't know how many more of these situations my reputation can withstand.
>
>Maybe SQL Server/Oracle isn't such a bad idea....
>
>-JT