Scott Ballinger wrote: > The trigger is normally called twice: the first time you get the > original @RECORD, the second time the new @RECORD. If an item > is new or > being deleted, then the trigger is called only once. I use > named common > to track of where I am and to save old @RECORD, so that I can test: if > this is not a new item, and old @RECORD is null, then this must be a > delete.
Scott said in an earlier post that he was talking about a pseudo-trigger implemented by creating a secondary index on a SUBR I-type. It may well be that such index routines are called twice, but real TRIGGERs aren't. Certainly on UniData they're not. Cheers, Ken ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
