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
_______________________________________________