|
First off, what's the big deal in validating something a second time. You are talking maybe milliseconds of processing time to repeat a validation. But if this is what is required. Create save fields to hold the previous value of the screen fields. Then only when they change do you do your validation. You can use a separate indicator for each field to position to a field on the screen. Ciao! Michael Schutte rpg400-l-bounces@xxxxxxxxxxxx wrote on 11/01/2006 07:22:25 PM:
I have a display file which contains about 7 fields which the user needs to complete. We need to use CHECK(ER) in order to validate the input as the user is entering it. All of this is simple enough, however I need to not only check these fields but also know when the user has entered the last field. In addition I am hoping to find a simple way to move the cursor from each field to the next corresponding field for each iter. I know that I could set the DSPATR(PR) with an indicator on each field once it has been validated and that will move the cursor along as well, but that also prevents the user from going back and editing information that although may be valid, is not correct. This would also help avoid looping through unneeded sub-routines each iter as well as fields that have been already validated do not need to be validated a second time, etc. Suggestions on how some of you would do it? Mark. -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing
list
To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
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.