At 30/05/2002 10:28 AM, you wrote:

>At 06:48 AM 30-05-02 -0300, you wrote:
>
>
> >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).
>
>Erk! a dying hard-drive? Gosh, I can remember when this happened at one
>of my clients (not when IB was the database) and it was horrible to behold
>- slow, tortured death. At least IB/FB gives reasonably good warnings. I
>hope they have some good backups.

Hi Helen,

I got confirmation of what happened to my client's system. It was a kind
of Trojan Horse virus, we thought that his anti-virus program was up to
date, but apparently it wasn't. There was a lot of Windows events that
pointed the diagnostic to a bad disk. Also, the database didn't go corrupt
within 24 hours as I stated above. After checking it thoroughly, the data
was ok this time, even though my client was getting error messages from IB,
probably because of the virus.

I just thought to let you know, so you can add this experience to the
errors documentation.


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