> As I said. Newbie.... Generators are something I have not come across. (Ex
> MS-SQL Trying to see if what you saud about IB is true ;-)) Look cool
> though..... HOWEVER....

Worth looking at - they are all transaction safe AFAIK, and they work so
well (put it in a before-trigger and you get auto-inc field :) )

> SHOW TRIGGER SOMETABLEAFTERUPDATE
>
> Triggers on Table SOMETABLE:
> SOMETABLEAFTERUPDATE, Sequence: 0, Type: AFTER UPDATE, Active
> AS
> BEGIN
> EXECUTE PROCEDURE WRITETRANLOG;
> END

drop trigger sometableafterupdate;

doesn't work???? It _should_.

> Now the above trigger has an incorrect param list for WRITETRANLOG. So I
> figure I would drop the trigger and re-create it. But all I keep getting
> is....
>
> Statement failed, SQLCODE = -104
> invalid request BLR at offset 19
> -parameter mismatch for procedure WRITETRANLOG

It shouldn't have allowed it to be saved in the first place - there is
referntial integ. all over the place to stop you altering a proc without
doing the trigger etc....

> I KNOW THIS. That is why I am attempting to drop the trigger. Even
> attempting to set the trigger INACTIVE produces the same error. Is there
> another sequence that I should be doing this in??

Try disconnecting from the DB, fire up WISQL and drop it manually (drop
trigger sometableafterupdate;). If that doesn't work, sorry, I dont know -
the only thing I can suggest is to re-create the DB (also, try dropping the
procedure BEFORE the trigger if doing the trigger first doesn't work)

If its small (<1meg zipped), backup the DB (gbak -b -USER SYSDBA -PASS
masterkey server:path/to/db.gdb somelocalfile.gbk or with the UI) and fire
the gbk file over to me (zip it, and send it to [EMAIL PROTECTED]) - I'll
see what I can do here.

Nic.

---------------------------------------------------------------------------
    New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
                  Website: http://www.delphi.org.nz

Reply via email to