Hi

> You claim that it cannot be a bug in your code, since you communicate via

fbclient.dll. But wouldn't it be possible that your code passes some invalid
data into fbclient calls, which in turn might cause the FB process to run
havoc?

While I suspect other sources for the actual problems (see other post), I
must say the following:
Even if there was some invalid (and even selectedly malicious) data passed
to fbclient calls, this should NEVER EVER result in any kind of corruption,
not "even" index corruptions.
It is the servers duty to validate input and drop invalid connections. The
server must never trust the client.

> Or possibly there's some faulty hardware in your system? Or some other

process running on your system that e.g. locks the databse file from time to
time, disrupting FB:s updates? Just to mention a few possible alternatives
to FB being buggy in this case.

That's more what I suspect as source of the problems, but see other mail.

Regards,
Steffen



[Non-text portions of this message have been removed]