Not Allowing Exit from Subscreen

[Jones Allen]

In general, I don't think you can force users to do anything but in this
case your best bet may be to have a ghost screen between the invoking screen
and your data entry screen. The ghost screen can check that all the info has
been entered, and if not, re-run the data entry screen. That way, it doesn't
matter how users leave the data-entry screen, the ghost screen is there to
catch the omissions. Make the ghost screen a "stopscreen" so entries of
multiple ^'s won't bypass it.

-----Original Message-----
From: Landers, Dianne [mailto:DLanders@pcc-structurals.com]
Sent: Wednesday, January 29, 2003 3:28 PM
To: Powerh-L (E-mail)
Subject: Not Allowing Exit from Subscreen


Does anyone know of a way to force the user to enter values in a field
before they are allowed to go back to the invoking screen?  I have a quick
screen where we allow the user to copy partial information from one record
to another, and we want to force them to enter the missing information
before they can exit.  I have an error that I raise in the EXIT procedure,
but it still goes back to the invoking screen.

The manual says that if an error occurs during the execution of the EXIT
procedure, QUICK backs up to the last ACCEPT or PROMPT verb.  It doesn't
seem to be behaving that way to me.  Any ideas out there?

ph823d7, HP-UX 11.0, oracle  8.1.7

Dianne Landers
PCC Structurals


= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l@lists.swau.edu
Subscribe: "subscribe" in message body to powerh-l-request@lists.swau.edu
Unsubscribe: "unsubscribe" in message body to
powerh-l-request@lists.swau.edu
http://lists.swau.edu/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.