--- In firebird-support@yahoogroups.com, "Alan McDonald" <alan@m...>
wrote:

> > I checked the server, it has force writes on, howerver they are

still

> > loosing records.
> >
>
> I just wonder by "not seeing them" you mean that your application is

failing

> to update a foreign key which went committed, means the the records

are

> orphaned? They could be there but not retrievable unless you update

that

> key.
> There's one thing IB/FB has never done and that's los records.

Alan, in fact patiently torturing IB/FB we can achieve this :)
1. Records can be on place but not visible with indexed selects in
case of broken indices. Reason, as usual, improper termination of FB
or operating system - power failure, three-fingers-salute etc. Forced
writes decreases probability of such a corruptions but not to 0. In
this case backup and restore (into another file!) can heal database
but can show another problem on restore - duplicates in unique
indices.
2. I recall reports on lost records if it was performed file-copy of
database when users were connected. Copy is broken anyway but
sometimes original database too. Automatic volume backup can help to
get broken this way database.
3. In old versions connections with different connection strings could
lead to lost records - server did'nt understand it is the same
database and corrupted it. It was said it is fixed long ago, but
personally I had not nor chance not will to check it :)

Best regards,
Alexander.