|
Hi Booth, This is a client request. This is the first time I have ever seen a request like this. It has a (limited) feel for Windows event-driven screen processing. The screen in question is a subfile. With cursor in first field in any given subfile record, user scans a bar code, which is an order#. If order# is a bulk item, enable (shut off ND & PR attributes) second entry field, Quantity, and place cursor there. If order# is not a bulk item, place cursor at next subfile record's order# entry. Also, for order# just scanned, place customer name in subfile record's third field, an output-only field. If it were my decision, I would have probably just opened a window strictly used to scan/enter the order#, then return to the subfile with proper cursor positioning. Knowing all that, and keeping in mind that I have a working prototype now, do you have any suggestions? (VA-RPG???) Dan Bale SAMSA, Inc. 989-790-0507 DBale@SAMSA.com <mailto:DBale@SAMSA.com> Stanley Cup Finals lower bowl tickets at Joe Louis Arena: $500 Official Red Wings jersey: $150 Octopii to drop splat in front of Irbe: $22 each TEN Lord Stanleys: PRICELESS! -----Original Message----- From: rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com]On Behalf Of Booth Martin Sent: Thursday, June 20, 2002 2:39 PM To: rpg400-l@midrange.com Subject: Re: differentiate between Enter vs. CHECK(ER)? Dan, what is the problem you are trying to solve? Is there an entirely different way of solving it? Perhaps finding some way to eliminate the CHECK(ER) keyword altogether? I ve found very few instances where the use of CHECK(ER) does anything useful for the program or the user. --------------------------------------------------------- Booth Martin http://www.MartinVT.com Booth@MartinVT.com
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.