PREEXIT functionality?

[Richard Witkopp]

Basically the screen allows some file updates and has the option of kicking
off a batch process. Most of the time that the user has run this screen,
they SHOULD kick off the batch process. The original design was to call a
subscreen in the EXIT procedure that would give the user one last chance to
kick off the batch process, or not. The catch is that a couple files need to
be updated behind the scenes before the batch process can be kicked off.
That doesn't work in the EXIT procedure.
 
I think I can use a variation of Ken's suggestion, good idea.
 
Thanks, Powerhosers!

-----Original Message----- 
From: Deskin, Bob [mailto:Bob.Deskin at Cognos.COM] 
Sent: Wed 5/2/2007 6:55 AM 
To: Richard Witkopp; powerh-l at lists.sowder.com 
Cc: 
Subject: RE: PREEXIT functionality?



Getting back to the original question and proper spelling :-), what 
exactly can't you do in the EXIT procedure and where do you see a 
PREEXIT coming in terms of timing. What differences would you like to 
see? 

Just as a review, the EXIT procedure happens in response to the Return 
command, so QUICK is leaving the screen. Record buffers may or may not 
be available and all modes are false. If you need data in the EXIT, you 
can always use TEMP items. 

If I understand your comments, you want to be able to issue an error and 
prevent the user from leaving the screen even if they've entered the 
return command (^). If there's something else, please let me know. 

We specifically did not provide that in the EXIT procedure because the 
user might consider themselves to be in a loop and simply abort. Ken's 
suggestion is the technique to use if you really want that 
functionality. But I do recommend that you still give the user an out. 

Bob 
Bob Deskin 
Senior Product Manager 
Application Development Tools 
Cognos Incorporated 
Office: 613-738-1338 ext. 7268 
bob.deskin at cognos.com 
http://powerhouse.cognos.com <http://powerhouse.cognos.com>  


-----Original Message----- 
From: powerh-l-bounces+bob.deskin=cognos.com at lists.sowder.com 
[mailto:powerh-l-bounces+bob.deskin=cognos.com at lists.sowder.com
<mailto:powerh-l-bounces+bob.deskin=cognos.com at lists.sowder.com> ] On 
Behalf Of Richard Witkopp 
Sent: May 1, 2007 5:44 PM 
To: 'powerh-l at lists.sowder.com' 
Subject: PREEXIT functionality? 


It would be nice if there was a PREEXIT procedure available in QUICK. At 
times, you want to do a final check of things before the user exits so 
you can slap him upside the head if he forgot something. Unfortunately, 
the EXIT procedure is not a good place to do much because Powerhoose has 
shut down a lot of stuff in preparation for leaving the screen. A lot of 
things won't work or won't work consistently. 

Is there a workaround to replicate the functionality of a PREEXIT 
procedure? 

NOTICE: The information contained in this e-mail and any attachments is 
confidential and may be privileged or otherwise protected from 
disclosure. This e-mail is intended solely for the use of the named 
addressee. Any other use, printing, copying, disclosure or dissemination 
may be subject to legal restriction. If you are not the intended 
recipient, please contact the sender and delete all copies including any 
attachments. 

-- 
= = = = = = = = = = = = = = = = = = = = = = = = = = = = 
Mailing list: powerh-l at lists.sowder.com 
Subscribe: &quot;subscribe&quot; in message body to 
powerh-l-request at lists.sowder.com 
Unsubscribe: &quot;unsubscribe &lt;password&gt;&quot; in message body to 
powerh-l-request at lists.sowder.com 
http://lists.sowder.com/mailman/listinfo/powerh-l
<http://lists.sowder.com/mailman/listinfo/powerh-l>  
This list is closed, thus to post to the list you must be a subscriber. 
Add 'site:lists.sowder.com powerh-l' to your search terms to search the 
list archive at Google. 
  
     This message may contain privileged and/or confidential information.
If you have received this e-mail in error or are not the intended recipient,
you may not use, copy, disseminate or distribute it; do not open any
attachments, delete it immediately from your system and notify the sender
promptly by e-mail that you have done so.  Thank you.


NOTICE: The information contained in this e-mail and any attachments is
confidential and may be privileged or otherwise protected from disclosure.
This e-mail is intended solely for the use of the named addressee. Any other
use, printing, copying, disclosure or dissemination may be subject to legal
restriction. If you are not the intended recipient, please contact the
sender and delete all copies including any attachments.