|
R Bruce, >first, it can only be an *after read >third, allow repeated change yes is permitted Isn't this a contradiction in terms? As I recall, the real problem with *READ triggers is that you can't use ALWREPCHG, since you can't use *BEFORE, and thus you can't blank out selected fields. Or even issue the escape message until *after* it is already read. I've never understood the logic in that limitation. Doug
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.