Thanks Andrew for your reply. It's greatly appreciated.

I know that I did ask, in the past few days, about some of the error
messages that I mentioned in my latest post. I didn't have my client's
actual log at the time and was feeding the error messages out of mine. The
message that I posted yesterday contains the log entries from my client.

There is at least one error that I'm curious about, and that's the first
one in my latest post, which is:
NTSERVER (Server) Tue May 21 23:26:09 2002
Database: C:\PROGRA~1\FILOPTO4\DATA\FILOPTO.FDB
internal gds software consistency check (wrong record length (183))

Also, keep in mind that the system was working fine for over 2 months,
before it occurred. But, this might be related to system errors generated
in the Windows event log(my colleague didn't tell me what he found). I
just want to understand how this error could've happened.

And, the reason why I posted my client's log entries was the chronological
order of the occurrence of the errors. Sometimes, the order that the
errors occur might tell a story of what happened. I do know some of the
messages and what they mean. And, you clarified those I didn't know.

Also, I found out from my colleague that actually does the tech support
with the clients(I do the dirty work as you can see), that this client's
Windows event log is full of red error flags. So, now I know that there's
something wrong with the system itself, because I did rectify the errors
before, but at a cost of losing data. And, it happened again not even 24
hours later(this tells me that the system itself is not trust worthy).


Daniel Rail
Senior System Engineer
ACCRA Group Inc. (www.accra.ca)
ACCRA Med Software Inc. (www.accramed.ca)