>That is what I did. Bummer it can't be avoided. Tell me, once we finnaly get all this switched to Oracle. Will this be eliminated?

Mike;


Now, if you were in California, I would say that the PG&E just cut off your power - what they are terming a "rolling blackout". What is a "rolling blackout" you ask? That is when the power company disconnects groups of users and laughs so hard they roll on the floor.

You might consider Stonefield Database Toolkit to prevent your files from getting hosed. However, when bad data is inserted into a field that is another story. Then you start looking at your network - switchers, routers, Hubs, OS, etc. If you have any kind of a glitch on the power that can cause a problem. I have tracked down that type of problem with a power line monitor. A large spike on the AC line is what I am referring to or even an SCR controlled device can corrupt data if it feeds back on the line.

Another source of problems is switching power supplies which all PC's use. When they get at a certain point of their life cycle they have been known to contribute to data losses because of excess hash which can be random.

Going to SQL Server or Oracle will make for a more robust system however, these problems still exist. That is why there are Database Administrators to recreate the database when it does a crash and burn. In a good environment I have seen VFP run for years without a problem. In a poor environment I have seen SQL Server and Oracle corrupt data. Nothing is perfect and you will pay a pretty penny to own, develop and use Oracle.

Tom