As others have mentioned, this is easier at 6.1.

If you're not at 6.1, then your options are
1) trigger
2) access through LF/Views that don't contain the timestamp field.

As an added bonus, you can implement option #2 without recompiling!
Simply move the data to a new table, and create a LF/View over the new
table using the name of the original table.


On Thu, Sep 17, 2009 at 4:43 PM, Alan Shore <AlanShore@xxxxxxxx> wrote:
Afternoon everyone

I KNOW that I've seen this (well, I think I have)
Is there a way to define a timestamp on a file that will automatically
change each and every time the record is written/updated WITHOUT any coding
changes to any programs.
Obviously re-compiles would be needed, but that's all

As always
any responses:- MUCH appreciated

Alan Shore
Programmer/Analyst, Distribution
P:(631) 200-5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].