|
Alan Shore wrote:
In my example the user goes back to the same field and INSERTS extra text into that field, pushing some pre-existing text to the right. Eventually the right most character cannot go any further, but the cursor is NOT at the right most character. Hence CHECK(ER) will NOT work (or at least it doesn't on mine test sample) Alan midrange-l-bounces@xxxxxxxxxxxx wrote on 09/01/2006 03:03:33 PM:Ok, then what do you want to do under what circumstances? The CHECK(ER) would return to the program and you can check anything out that you want about the last character, or ANY character.... ??? "is there a way for the program to realize that the last character is NOT blank. " -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Shore Sent: Friday, September 01, 2006 2:03 PM To: Midrange Systems Technical Discussion Subject: RE: Field filled in Thanks for your reply Dave. I think what you are talking about is CHECK(ER). I do use this, however if you re-read my example, the cursor is NOT at the end of the field. That's my predicament. Alan midrange-l-bounces@xxxxxxxxxxxx wrote on 09/01/2006 02:27:16 PM:Actually, there is a possibility of making the block oriented data stream work something like what you want. It's been a long time, but there is something you can put into DDS that tells the system to do an auto-Enter type of action. If you were to put that on each field, as the user went from field to field, the display would return to theprogram.You would then determine what field was entered, if it was correct or not, and re-write the screen with the cursor placed where you wanted it to be. Don't know if it's practical, but I have used it in the past. Primarily on the last record of a subfile used in heads down entry. When the user hit the last field, the screen would automatically refresh and the user would be able to continue entry with no hesitation - OR - keying over information already entered... Spoz that could stir up a bee's nest maybe... :-) Dave-- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailinglistTo post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-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.