At 02:13 PM 19/06/2003 +0200, you wrote:

>Must be - this isn't allowed:
>
>alter index rdb$foreign80 inactive

Not in 1.5 - I just checked. And found that the exception has a bug. I
*hope* that it is just a little mistake in the message enhancements that
Dmitry did recently, and not a sign that a request to deactivate a foreign
key causes an attempt to deactivate one or more primary keys...

Oh, btw, in 1.0.2 you *could* deactivate both primary and foreign key
indexes...
I've seen similar to the reported problem before (where a pk index was set
inactive and the developer forgot to reactivate it) with a db that was
running under 1.0.2.

Hmm -- I think it would be worth running that alter index request through
the SQL monitor. Will report back on anything interesting.

h.