N,
> doesn't work???? It _should_.
Uh oh.....
> the only thing I can suggest is to re-create the DB
You're making me nervous. Here I am playing with 2 tables and you are
suggesting things like the above (Linux v Windoze springs to mind). Does not
bode well for a production system. (This is 5.5, perhaps 5.6 is better??)
- also, try dropping the procedure BEFORE the trigger
Tried that..... Doesn't like it.... Naturally the procedure has
dependencies.......
As I am still playing I just killed off the whole table and then recreated
it..... I think that some of the issues here are arising from the fact that
I am using SQL explorer and WISQL. I would like some GUI tool as a fallback
at some point for our people out in the field. If SQL Explorer does not
measure up (and the one you mentioned when I first raised the issue of
interbase was also rather flaky) are there any others???
Also did you read my post earlier about TIBEvents?? Any ideas on that???
> see what I can do here.
Thanks for the offer, but I fixed it as above.....
------------------------------------------------------------------------
--Donovan
Donovan J. Edye [www.edye.wattle.id.au]
Namadgi Systems, Delphi Developer
Web: www.namsys.com.au E-Mail: [EMAIL PROTECTED]
Voice: +61 2 6285-3460 Fax: +61 2 6285-3459
TVisualBasic = Class(None);
------------------------------------------------------------------------
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Nic Wise
> Sent: Wednesday, 2 February 2000 14:03
> To: Multiple recipients of list delphi
> Subject: Re: [DUG]: Interbase Error : What am I missing here???
> (Interbase Newbie)
>
>
> > 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
>
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
