Not Allowing Exit from Subscreen
Tim Cummings
tim.cummings@frequencymarketing.com
Thu, 30 Jan 2003 08:17:54 -0500
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C2C861.FFB43BE0
Content-Type: text/plain;
charset="iso-8859-1"
Dianne,
I have been writing Quick since Quick came out in it's original beta
release. I have run across this same problem at many of my clients over the
years and I can tell you with confidence that the only way to accomplish
what you are trying to do is using the technique that Allen described.
Unfortunately the many requests from the user community have not swayed
Cognos to allow an error in the exit procedure to take the user back to the
action line (or anywhere else for that matter). I would go with the ghost
screen and save your self a lot of time and aggravation.
Tim Cummings
Cummings Consulting
Cincinnati, OH
513-576-1182
-----Original Message-----
From: Landers, Dianne [mailto:DLanders@pcc-structurals.com]
Sent: Wednesday, January 29, 2003 6: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.
------_=_NextPart_001_01C2C861.FFB43BE0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: Not Allowing Exit from Subscreen</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>Dianne,</FONT>
</P>
<P><FONT SIZE=3D2>I have been writing Quick since Quick came out in =
it's original beta release. I have run across this same problem =
at many of my clients over the years and I can tell you with confidence =
that the only way to accomplish what you are trying to do is using the =
technique that Allen described. Unfortunately the many requests =
from the user community have not swayed Cognos to allow an error in the =
exit procedure to take the user back to the action line (or anywhere =
else for that matter). I would go with the ghost screen and save =
your self a lot of time and aggravation.</FONT></P>
<BR>
<P><FONT SIZE=3D2>Tim Cummings</FONT>
<BR><FONT SIZE=3D2>Cummings Consulting</FONT>
<BR><FONT SIZE=3D2>Cincinnati, OH</FONT>
<BR><FONT SIZE=3D2>513-576-1182</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Landers, Dianne [<A =
HREF=3D"mailto:DLanders@pcc-structurals.com">mailto:DLanders@pcc-structu=
rals.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Wednesday, January 29, 2003 6:28 PM</FONT>
<BR><FONT SIZE=3D2>To: Powerh-L (E-mail)</FONT>
<BR><FONT SIZE=3D2>Subject: Not Allowing Exit from Subscreen</FONT>
</P>
<P><FONT SIZE=3D2>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.</FONT></P>
<P><FONT SIZE=3D2>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?</FONT></P>
<P><FONT SIZE=3D2>ph823d7, HP-UX 11.0, oracle 8.1.7</FONT>
</P>
<P><FONT SIZE=3D2>Dianne Landers</FONT>
<BR><FONT SIZE=3D2>PCC Structurals</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =
=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D</FONT>
<BR><FONT SIZE=3D2>Mailing list: powerh-l@lists.swau.edu</FONT>
<BR><FONT SIZE=3D2>Subscribe: "subscribe" in message body to =
powerh-l-request@lists.swau.edu</FONT>
<BR><FONT SIZE=3D2>Unsubscribe: "unsubscribe" in message body =
to powerh-l-request@lists.swau.edu</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://lists.swau.edu/mailman/listinfo/powerh-l" =
TARGET=3D"_blank">http://lists.swau.edu/mailman/listinfo/powerh-l</A></F=
ONT>
<BR><FONT SIZE=3D2>This list is closed, thus to post to the list you =
must be a subscriber.</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C2C861.FFB43BE0--