That's not the problem. I can assign either procedure as a trigger just fine.
This is a newly created database from an unload file. Dennis McGrath -- MikeB <[EMAIL PROTECTED]> wrote: > Dennis, > Do List proc and see if the procedure has an ID. I was getting > this error and it was because > there was a snafu in the autonumbering of the procedures. Bill D. > and I discussed this a couple > weeks back including the workaround (well actually the fix if this is > the trouble.) > > The text from Bill and I follows: > > Your Workaround works, but you also have to do the same to > Sys_Proc_Cols and Sys_Proc_Mods? > > > ----- Original Message ----- > From: "Bill Downall" <[EMAIL PROTECTED]> > To: "RBG7-L Mailing List" <[EMAIL PROTECTED]> > Sent: Wednesday, June 11, 2003 12:08 PM > Subject: [RBG7-L] - Re: Stored Procedure > > > > Mike, > > > > I reported that same problem as a bug in an early version, and it > was fixed > > in a later version. Hmmm. I won't ask why the boo-boo came back, > for fear > > of Razzak's "big boys." > > > > I think my workaround at that time was to do a new AUTONUM command > > against the sys_procedures table, but you'ld better show your > example to > > RBTI. > > > > Bill > > Actually, the test db was a converted 65 db that may have had the > sniffles from Bills comments. > After Autonumbering the 3 affected Sys tables, the put command is > working OK. > > Thanks. > > ----- Original Message ----- > From: "Emmitt Dove" <[EMAIL PROTECTED]> > To: "RBG7-L Mailing List" <[EMAIL PROTECTED]> > Sent: Wednesday, June 11, 2003 1:19 PM > Subject: [RBG7-L] - Re: Stored Procedure > > > > Mike, > > > > I've been doing many PUTs, even today, as I am working on a stored > > procedure here. No problems with the ID. > > > > >Build 50A > > > > > >Trying to build a solution for John Spyrou that will work with the > > >standard database navigation > > >controls. > > >I am just using a Stored procedure to simulate the functionality > of the > > >row level eeps from 65 and > > >can't get RBase to add a Stored procedure properly. > > >When I issue the Put it adds the row for the procedure, but the ID > for the > > >procedure is null, so the > > >Call ProcedureName says the Proc doesn't exist. > > > > > > Anyone else confirm this? > > > > Emmitt Dove > > Manager, DairyPak Business Systems > > Blue Ridge Paper Products, Inc. > > 40 Lindeman Drive > > Trumbull, CT 06611 > > (203) 673-2231 > > [EMAIL PROTECTED] > > [EMAIL PROTECTED] > > > > > > ----- Original Message ----- > From: "Dennis McGrath" <[EMAIL PROTECTED]> > To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> > Sent: Wednesday, June 25, 2003 8:55 PM > Subject: [RBASE-L] - After triggers > > > > Can someone tell me the secret for getting an after update trigger > on a > > table? > > > > I have two procedures define with no parameters: > > beforepro and afterpro > > They list ok > > > > I used the syntax acording to RSyntax.com : > > ALTER TABLE Student ADD TRIGGER + > > UPDATE BEFORE beforepro, + > > UPDATE AFTER afterpro > > > > I get the error message "Procedure does not exist" whenever I > include > > the keywords BEFORE or AFTER in this syntax. > > > > If I leave those keywords out, the first trigger only is created > and I > > get no error message > > > > Am using the latest and greatest RBDOS patch. > > > > Dennis McGrath > > > > >
