Just a thought, but maybe you have an outer parent transaction that
is being rolled back (because of an error or crash) which
can "uncommit" the previously committed child transaction:

TRANSACTION PARENT BEGIN:

TRANSACTION CHILD BEGIN:
UPDATE 1...
UPDATE 2...
UPDATE 3...
TRANSACTION CHILD COMMIT

UPDATE 4...
UPDATE 5...

TRANSACTION PARENT ROLLBACK
--> Rolls back previously committed updates 1, 2, 3 and updates 4, 5

Regards,
Walter

--- In firebird-support@yahoogroups.com, "Zakir Mahomedy"
<zmahomedy@d...> wrote:

> I have been using Firebird for about 1 year now without much

problems, however lately there have been reports from my client that
after he enters a few records and confirms that it has been saved
into the db, the next day or a few days laters the record no longer
exists. He has confirmed that no one has interfered with the database.

>
> I have been using ODBC driver as my interface. I cant seem to

figure how this would be possible as I checked my application coding
and cant find what could be causing this to happen.

>
> I am using RC6.
>
> Any ideas on what could course records to disappear after a

confirmed commit to the db.

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