Not Allowing Exit from Subscreen
Peter Bateman
shediac92@hotmail.com
Fri, 31 Jan 2003 10:37:21 -0400
This is a multi-part message in MIME format.
------=_NextPart_000_006B_01C2C914.BC0888C0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
RE: Not Allowing Exit from SubscreenDianne:
A procedure PREEXIT would be nice to have.
A error in PREEXIT would keep the users focus on the
current screen.
Here is a technique that could help.
If your users are hitting a function key to exit change the
action on the function key to run as designer procedure.
If no errors detected in the designer PUSH RETURN in
the designer.
Regards,
Peter Bateman
----- Original Message -----=20
From: Landers, Dianne=20
To: Tim Cummings ; Powerh-L (E-mail)=20
Sent: Thursday, January 30, 2003 1:29 PM
Subject: RE: Not Allowing Exit from Subscreen
ok, thats what i'll try. thanks for all the ideas and help.
Dianne Landers=20
PCC Structurals=20
-----Original Message-----
From: Tim Cummings [mailto:tim.cummings@frequencymarketing.com]
Sent: Thursday, January 30, 2003 5:18 AM
To: Landers, Dianne; Powerh-L (E-mail)
Subject: RE: Not Allowing Exit from Subscreen
Dianne,=20
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=20
Cummings Consulting=20
Cincinnati, OH=20
513-576-1182=20
-----Original Message-----=20
From: Landers, Dianne [mailto:DLanders@pcc-structurals.com]=20
Sent: Wednesday, January 29, 2003 6:28 PM=20
To: Powerh-L (E-mail)=20
Subject: Not Allowing Exit from Subscreen=20
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=20
Dianne Landers=20
PCC Structurals=20
=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=20
Mailing list: powerh-l@lists.swau.edu=20
Subscribe: "subscribe" in message body to =
powerh-l-request@lists.swau.edu=20
Unsubscribe: "unsubscribe" in message body to =
powerh-l-request@lists.swau.edu=20
http://lists.swau.edu/mailman/listinfo/powerh-l=20
This list is closed, thus to post to the list you must be a =
subscriber.=20
------=_NextPart_000_006B_01C2C914.BC0888C0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>RE: Not Allowing Exit from Subscreen</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Dianne:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2> A procedure PREEXIT would be =
nice to=20
have.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> A error in PREEXIT would keep =
the users=20
focus on the</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> current screen.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2> Here is a technique that =
could=20
help.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2> If your =
users are hitting=20
a function key to exit change the</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> action on the function key to run =
as designer=20
procedure.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2> If no errors detected in the =
designer PUSH=20
RETURN in</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> the designer.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Regards,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Peter Bateman</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A title=3DDLanders@pcc-structurals.com=20
href=3D"mailto:DLanders@pcc-structurals.com">Landers, Dianne</A> =
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A=20
title=3Dtim.cummings@frequencymarketing.com=20
href=3D"mailto:tim.cummings@frequencymarketing.com">Tim Cummings</A> ; =
<A=20
title=3Dpowerh-l@lists.swau.edu =
href=3D"mailto:powerh-l@lists.swau.edu">Powerh-L=20
(E-mail)</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Thursday, January 30, =
2003 1:29=20
PM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> RE: Not Allowing Exit =
from=20
Subscreen</DIV>
<DIV><BR></DIV>
<DIV><SPAN class=3D450113217-30012003><FONT face=3DArial =
color=3D#0000ff size=3D2>ok,=20
thats what i'll try. thanks for all the ideas and=20
help.</FONT></SPAN></DIV>
<DIV> </DIV>
<P><FONT face=3DArial size=3D2>Dianne Landers</FONT> <BR><FONT =
face=3DArial=20
size=3D2>PCC Structurals</FONT> </P>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
size=3D2>-----Original Message-----<BR><B>From:</B> Tim Cummings=20
[mailto:tim.cummings@frequencymarketing.com]<BR><B>Sent:</B> =
Thursday,=20
January 30, 2003 5:18 AM<BR><B>To:</B> Landers, Dianne; Powerh-L=20
(E-mail)<BR><B>Subject:</B> RE: Not Allowing Exit from=20
Subscreen<BR><BR></FONT></DIV>
<P><FONT size=3D2>Dianne,</FONT> </P>
<P><FONT size=3D2>I have been writing Quick since Quick came out in =
it's=20
original beta release. I have run across this same problem at =
many of=20
my clients over the years and I can tell you with confidence that =
the only=20
way to accomplish what you are trying to do is using the technique =
that=20
Allen described. Unfortunately the many requests from the user =
community have not swayed Cognos to allow an error in the exit =
procedure to=20
take the user back to the action line (or anywhere else for that=20
matter). I would go with the ghost screen and save your self a =
lot of=20
time and aggravation.</FONT></P><BR>
<P><FONT size=3D2>Tim Cummings</FONT> <BR><FONT size=3D2>Cummings=20
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:=20
Landers, Dianne [<A=20
=
href=3D"mailto:DLanders@pcc-structurals.com">mailto:DLanders@pcc-structur=
als.com</A>]</FONT>=20
<BR><FONT size=3D2>Sent: Wednesday, January 29, 2003 6:28 PM</FONT> =
<BR><FONT=20
size=3D2>To: Powerh-L (E-mail)</FONT> <BR><FONT size=3D2>Subject: =
Not Allowing=20
Exit from Subscreen</FONT> </P>
<P><FONT size=3D2>Does anyone know of a way to force the user to =
enter values=20
in a field before they are allowed to go back to the invoking =
screen? =20
I have a quick screen where we allow the user to copy partial =
information=20
from one record to another, and we want to force them to enter the =
missing=20
information before they can exit. I have an error that I raise =
in the=20
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=20
of the EXIT procedure, QUICK backs up to the last ACCEPT or PROMPT=20
verb. It doesn't seem to be behaving that way to me. Any =
ideas=20
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=20
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=20
=3D</FONT> <BR><FONT size=3D2>Mailing list: =
powerh-l@lists.swau.edu</FONT>=20
<BR><FONT size=3D2>Subscribe: "subscribe" in message body to=20
powerh-l-request@lists.swau.edu</FONT> <BR><FONT =
size=3D2>Unsubscribe:=20
"unsubscribe" in message body to =
powerh-l-request@lists.swau.edu</FONT>=20
<BR><FONT size=3D2><A =
href=3D"http://lists.swau.edu/mailman/listinfo/powerh-l"=20
=
target=3D_blank>http://lists.swau.edu/mailman/listinfo/powerh-l</A></FONT=
>=20
<BR><FONT size=3D2>This list is closed, thus to post to the list you =
must be a=20
subscriber.</FONT> </P></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_006B_01C2C914.BC0888C0--