|
Hear, Hear! I've stayed out of this guy's threads, but he's got my blood boiling! Terry Richardson Vermont Information Processing, Inc. terry@xxxxxxxxxx "Booth Martin" <booth@xxxxxxxxxx om> To Sent by: <rpg400-l@xxxxxxxxxxxx> rpg400-l-bounces+ cc terry=vtinfo.com@ midrange.com Subject Re: Disabling one of 2 keys (DEL & Update) 03/17/2004 01:13 PM Please respond to RPG programming on the AS400 / iSeries <rpg400-l@midrang e.com> Since you are determined to do the process in your way then you do it. Don t let the experience and suggestions from the users on this list interfere in your God-given right to do your programming in redundant and confusing ways. I believe there is no way to disable an F-key in RPG. But then, I've never designed a program that was so terribly designed as to need that ability. Sorry for the flame, but gads man, don't you ever learn? --------------------------------- Booth Martin http://www.martinvt.com --------------------------------- -------Original Message------- From: RPG programming on the AS400 / iSeries Date: 03/17/04 12:00:50 To: RPG programming on the AS400 / iSeries Subject: Re: Disabling one of 2 keys (DEL & Update) Booth, The 2 keys are allowed for use in the same routine. I am looking for a way to disable one, when the other is on, in RPG. You can't move *off because the pressing of the key has a power of its own. Thanks, Rob400 > -----Original Message----- > From: Booth Martin [mailto:booth@xxxxxxxxxxxx] > Sent: Wednesday, March 17, 2004, 8:32 AM > To: rpg400-l@xxxxxxxxxxxx > Subject: Re: Disabling one of 2 keys (DEL & Update) > > > As this is the RPG list I will deal in the RPG solutions, not the DDS > solutions. > > Have your users spoken to you yet? Do NOT drink the coffee they offer you. > > When F2 is pressed and the user chooses to delete the record then the > process is done. Either start the next cycle or end the job. In any event > do not allow the F2 choice to take the user back to the screen with the > deleted screen's values. This is easy to do in your RPG program however it > concerns me that the process is not clear in your own mind yet. Instead of > creating a list of things you do NOT want to happen make the choice of what > you do want to have happen. In other words what should happen once a record > is deleted? Should the user see another record? Should the program end? > Should the user be taken to an inquiry screen where he can choose the next > set of records? > > Stop programming for what you don't want happening. Program for what you do > want happening. > > > --------------------------------- > Booth Martin > http://www.martinvt.com > --------------------------------- > -------Original Message------- > > From: RPG programming on the AS400 / iSeries > Date: 03/17/04 10:02:14 > To: RPG programming on the AS400 / iSeries > Subject: Disabling one of 2 keys (DEL & Update) > > HI I am using one screen to update and delete, by keys. When F2 is hit that > means Delete, when F5, update. After each key hit, there is a confirm screen > then rekey then done. Actually the full reconfirm is only on F2 because the > starting point is into Update mode so I don't need another confirm. The > problem is when F2 is hit. I redisplay the screen, and if you want to, you > can still hit F5. Is there a way to handle this in the DDS, or must I code a > bunch of statements only allowing F5 when there was no prior F2? > Thank you, > Rob400 > _______________________________________________ _______________________________________________ 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.