The trigger is probably not going to be fired.
Let me know if it works, but I do not expect it to.
When you created the trigger it bound that file to the database so
that the database engine knows to fire triggers, check RI constraints
(foreign table constraints), etc.
If you just recreate the file (Btrieve API?) it would not be bound to
the database so I would not expect the trigger to fire.
The status 73 meant that the file as already populated violated one of
the SQL foreign key constraints. For more information you can run the
Check Database Wizard on the database and it can check and report the
constraint violations.
Leonard
On Mon, 12 Jul 2004 22:19:53 +0200, "Roland Wolfs"
<r.wolfs (AT) rw-software (DOT) com> wrote:
Quote:
After creating a trigger on file "FILENAME", I get the following error when
I try to re-access that file.
ODBC Error: SQLSTATE = S1000, Native error code = 0
Unable to open table: "FILENAME".
The RI definition is out of sync(Btrieve Error 73)
--
After physically removing the file from the disk, I can recreate it again,
and access it again - trigger remains in the system.
Roland |