Tim,

After droping a field before deleting the attached trigger the db cannot be opened for
altering in EDBManager any more.
Once the field is gone, droping the trigger does not solve the problem etiher . Even after
they are both gone from EDBManager, keep getting Error #401. It appears that a foreign key
is missing fom the metadata db.

Tried reverse engineering -  fails with the same error.
Backup and restore works, but but the problem remains.

(I understand how risky it is to allow direct access to metadata tables, but in this case
it would probably make it possible to repair it in a blink.)

Regards,
Leslie

Correction:

After droping a field without deleting the attached trigger first ...

Leslie,

<< After droping a field before deleting the attached trigger the db cannot
be opened for altering in EDBManager any more.  Once the field is gone,
droping the trigger does not solve the problem etiher . Even after they are
both gone from EDBManager, keep getting Error #401. It appears that a
foreign key is missing fom the metadata db. >>

What version of ElevateDB are you using ?  And what is the column name and
what does the trigger look like ?

<< (I understand how risky it is to allow direct access to metadata tables,
but in this case it would probably make it possible to repair it in a
blink.) >>

It's not actually a database, but rather just looks like one to the end
developer/user.  And, it should never need repaired because we never allow
direct access to it.

--
Tim Young
Elevate Software
www.elevatesoft.com

Leslie,

Also, if you want to just send me a copy of your backup file (.edbbkp), that
will work also.

--
Tim Young
Elevate Software
www.elevatesoft.com

Leslie,

I tried to reproduce this using a NEWROW reference in the trigger to the
column being dropped, and I got a #401 column not found error message during
the ALTER TABLE execution, and the catalog was still fine afterwards.

However, the message is a little less than helpful, so I've added the proper
dependency checks in 2.02 B4 for such a column drop so that the error
message reflects a dependency error along with the name and type of the
trigger that has the dependency.

--
Tim Young
Elevate Software
www.elevatesoft.com