Karen, I prefer to control such action in TRIGGERS because in my applications form are not the only method of inserting and updating records. With my address tables I need to keep track of who and when actions were performed. I was able to partially solve my problem by a major redesign of the structure by placing audit information in the master table instead of the subordinate address table. I had to resort to this because RBase implements BEFORE/AFTER INSERT and UPDATE TRIGGERS as read only cursors. When I tried to change audit fields in the subject record during the TRIGGER is created an endless loop that turminate when I exceeded some internal limit. I know of several competitive databases that implement TRIGGERS with an updateable cursor. I have had such an enhancement request in for several years to make the BEFORE INSERT and the BEFORE UPDATE triggers have an updateable cursor.
Maybe some day. Jim Bentley American Celiac Society [email protected] tel: 1-504-737-3293 --- On Fri, 1/30/09, [email protected] <[email protected]> wrote: > From: [email protected] <[email protected]> > Subject: [RBASE-L] - Re: ERROR- Specified default value is not valid for > column Re... > To: "RBASE-L Mailing List" <[email protected]> > Date: Friday, January 30, 2009, 7:50 AM > Jim: You're right, we couldn't use a computed > column either. I think in > our case the updating of this date column would have been > done only in 2 places > within a form, so we made a form variable instead for > Colname = .#DATE so > that the date would update if we entered a row or saved a > change. Could also > handle this with a trigger if you want to keep track of > r> prompt changes or > other programs that might do an Update. > > Karen > > > > Using a computed column doesn't work for me as a > reload resets the value > > whereas I am using such a field to track changes for > audit purposes. > > > > Perhaps in v9.0. > > > > Jim Bentley
