That could work. For most tables in my databases, I have a column for the userID of the last person to update the record. In that case, the user value would be available in the stored procedure as "current of sys_new."
You could also use a stored procedure that was not a trigger, although then you would need to invoke it with a separate direct-dbms action (SELECT (CALL ProcName(parameterlist)) FROM dummy) Bill On Fri, 12 Jul 2002 14:37:40 -0600, Troy Sosamon wrote: >This might work for a VB app, but it would not work for a Tango APP. > >Maybee I could build a perminant table to temporarily hold values w/ >everything that is needed and run the trigger off of the data put in that >table????? ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
