Quote:
>You've been given plenty of good advice on fixing the error when it occurs,
>but I haven't seen what the root of the problem is yet. In my experience, it
>usually boils down to a single user who likes to turn of their computer
>without properly shutting down. I would check this first.
>My permanent solution has been to use FoxFix in the nightly maintenance
>routine (since I couldn't break the bad habits of the users). It just opens
>the files with FF and if there's an error, it fixes it automatically and then
>dumps a repair log out to a file with the details.
>With this setup, I haven't had a call related to a file error in over 2
>years.
Its a real shame that knuckle headed users cant learn a few simple lessons,
like how to shut down Windows 95.. I recommend a 2 x 4 as a teaching tool.. but
beyond that, there are a couple other ways to help prevent this problem.
First, if feasible put a FLUSH command at appropriate places in the program.
This will force the network to dump the data to the hard media. Secondly, you
can turn down the cache level on the network client if they use Client32 from
novell. This may slow performance slightly, but it should cut down the chance
of having a corrupted database.
Mike Occhipinti