If I understand the new functionality correctly the audit stamp will get updated any time the record is updated regardless of the update source. The tables in question are validation tables which shouldn't be maintained very often but do control what values are allowed into other tables. If a problem arises with a validation record I would like to know who made the last update and when. I can force the fields to change using a maintenance program but I don't have that kind of control if SQL or DBU is used for the update.
At 5.4 it looks like my only option is a trigger.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, May 11, 2009 3:18 PM
To: Midrange Systems Technical Discussion
Subject: RE: Update timestamp automatically when row changes
Why wouldn't the new stuff need additional coding? Let's face it, most developers still use RLA versus SQL to update their data, especially in a maintenance program like you're talking about. When they do so, very few build a LF that only uses the fields they maintain versus the PF or a LF that selects all fields. And few developers will use the %fields in their update operation code. And, %fields is not even supported on the WRITE statement only on the UPDATE statement. So how would you not change your existing code to not write out default values in there without switching over to a LF that only selects certain fields or go to SQL instead of RLA?
In my opinion the trigger is the better bet.
And submit a DCR to get %fields in the WRITE statement.
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
Privileged and Confidential. This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain privileged or confidential information. If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail. You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited.
midrange.com
