Tim

First time I've ever had this happen. I've restored from backup so there's not a problem and my question is for curiosity only. If you're busy don't bother replying.

The printer on my network started playing silly buggers so I had to turn it off and reboot the PC its connected to. First I closed my app on my PC and it threw a wobbly, no idea why. After sorting the printer out I couldn't log back in as the tables were corrupted. Tried repairing over the network. Didn't work. Repaired on the fileserver. Worked BUT all the index definitions for one table had been wiped.

The question is what will cause the index headers to become corrupt to the point where they are wiped?

Roy Lambert

Roy Lambert wrote:

> Tim
>
> First time I've ever had this happen. I've restored from backup so there's not a problem and my question is for curiosity only. If you're busy don't bother replying.
>
> The printer on my network started playing silly buggers so I had to turn it off and reboot the PC its connected to. First I closed my app on my PC and it threw a wobbly, no idea why. After sorting the printer out I couldn't log back in as the tables were corrupted. Tried repairing over the network. Didn't work. Repaired on the fileserver. Worked BUT all the index definitions for one table had been wiped.
>
> The question is what will cause the index headers to become corrupt to the point where they are wiped?
>
> Roy Lambert

Roy,
   Prior to printing, could you not run FlushBuffers to write the cache
to disk just in case something happens when printing? I suppose you
could run FlushBuffers every few minutes to eliminate corrupted files. I
think this might help.

Dave

Dave


I'm not too concerned. Its the first time something like this has happened and I've been using DBISAM since V2.

Roy Lambert

Roy Lambert wrote:

> Dave
>
>
> I'm not too concerned. Its the first time something like this has happened and I've been using DBISAM since V2.
>
> Roy Lambert
>
Roy,
   It happened to me just a week ago. No fault of DBISAM, but both of
my dual screens went blank and I had to reset the computer. When you're
dealing with Windoze and maybe faulty hardware, you actually have to
write code to take system failures into account. Sort of like wearing a
cup when playing baseball-you gotta protect your assets.

Dave

Roy,

<<The printer on my network started playing silly buggers so I had to turn
it off and reboot the PC its connected to. First I closed my app on my PC
and it threw a wobbly, no idea why. After sorting the printer out I couldn't
log back in as the tables were corrupted. Tried repairing over the network.
Didn't work. Repaired on the fileserver. Worked BUT all the index
definitions for one table had been wiped.

The question is what will cause the index headers to become corrupt to the
point where they are wiped? >>

Were the tables written to prior to the shutdown ?  With tables that are
local, the Windows file system will overwrite portions of the table with
junk data if a) the table was written to prior to the blowup, and b) the
table was not flushed to disk.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


Probably but quite some time before if at all.

Roy Lambert

Roy,

<< Probably but quite some time before if at all. >>

Unfortunately, it doesn't matter because the Windows file system appears to
literally cache things for several hours in some cases.

--
Tim Young
Elevate Software
www.elevatesoft.com