|
List, I have mapped field names such as "Part#Invld" to *In23, "LengInvld" to *In24, etc., so that the corresponding indicator can be used to reverse imaging/cursor position screen fields on errors. As such, if I want to do something when a condition IS VALID, I end having to use a double-negative, such as "Not Prt#Invld". For readability I would much rather use "Prt#Valid", but my output screen indicators would then have to be a series of 'N##'s. I know that I could have a series of statements, such as 'Prt#Valid = Not Prt#Invld', or change both fields whenever I changed one. Both of these methods would require that I always remember to execute the chosen process to change the second variable. I was wondering if there is a method that I am overlooking that would AUTOMATICALLY cause one field to be the 'Not' of another immediately upon its changing of value. TIA for any suggestions, Tim Kredlo Exterior Wood, Inc
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.