Thanks, Emmitt. I’ll go that direction. Dennis
________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Emmitt Dove Sent: Wednesday, January 13, 2010 3:03 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: date tracking question Dennis, I've previously posted a sample using a variable set in the trigger itself. I'm away from my computer, but the gist is this: at the top of the trigger, declare and type a variable but do not assing a value. Next, test the variable to see if it is not NULL. If not NULL, clear the variable and RETURN, else assign a value and continue the trigger code. Emmitt -- Sent from my Palm Prē ________________________________ Dennis McGrath wrote: I guess my next question is, what is the best way to avoid an endless loop when updating a row that has been updated. Obviously some kind of variable flag could be used, but is there a better way? ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Wednesday, January 13, 2010 1:05 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: date tracking question Dennis: That would be my guess. A simple update trigger to push the value in (you would have to be careful about an endless loop), and also an insert trigger for the first time. Karen I need to add a datetime column to a table that will indicate the last time each row was inserted or updated. It has to be updated regardless of how it is updated, namely with RBASE or Ottero. I want this value to survive a reload or an unload/load. It believe this rules out a computed column Is a trigger the only way to accomplish this? Thanks in advance, Dennis McGrath
