>
> On the weekend I tried to backup and restore a database to reorganize
> it. The restored failed with duplicate keys in a primary key
> constraint. How is this possible? The primary key constraint should
> have prevented the creation of duplicate keys in the first place. And
> before you ask, this constraint has been in place since the database
> was created. It has never been set inactive because you can't
> inactivate a primary key constraint. There has never been any hint of

are you sure? I thought there was a problem with 1.0.3 in that you could
have inactive PK constraints.
Try to restore setting indexes to inactive and see if it restores.
Alan

> data corruption either. I'm using Firebird 1.0.3 on W2K.
>
>