PUT's not working in EXIT procedure

[Deskin, Bob]

Well done Matt. It's easy enough to check what mode you're in. Set a
define based on the different modes (don't forget no mode) and do an
INFO NOW RESPONSE. I was wondering about the comment that Cognos
specifically stated that the PUT verb doesn't work in the EXIT procedure
because I couldn't find any such reference nor do I recall that change
(and I would have been involved in making it). I do recall discussions
around not changing record status in FINDMODE and working through the
logic of why we originally did that. In case anyone cares it has to do
with things like automatically changing things the user didn't intend
and SUM INTOs and such.

Bob Deskin              
Senior Product Advisor  bob.deskin@cognos.com
Cognos Inc.             (613) 738-1338 ext 4205 FAX: (613) 228-3149
3755 Riverside Drive P.O. Box 9707 Stn. T, Ottawa ON K1G 4K9 CANADA


> ----------
> From: 	MattO1@aol.com[SMTP:MattO1@aol.com]
> Sent: 	August 15, 1998 5:27 PM
> To: 	KPCUMMIN@GAPAC.com; powerh-l@lists.swau.edu
> Subject: 	Re: PUT's not working in EXIT procedure
> 
> In a message dated 8/13/98 11:52:17 AM Central Daylight Time,
> KPCUMMIN@GAPAC.com writes:
> 
> << 
>  I have a clustered screen which contains no database fields, only
> TEMP's.
>  Duing the EXIT procedure, I am attempting to update a field in a
> DESIGNER
>  procedure using an explicit PUT command.  I have found, however, that
> the
>  PUT verb does absolutely nothing if I use it in the EXIT procedure,
> contrary
>  to the PowerHouse documentation.
>  
>  I have experimented with other PUT's in the EXIT procedure (on an
> indexed
>  data file).) and found that they have no effect either.
>   >>
> Hi Ken,
> I've read the other replies so I realize you have a work-around, but
> just as
> an extra bit of information, I suspect I may know the root of your
> problem.
> The Put verb, as you probably know, will not perform any actual update
> activity if the record status is NOTALTERED.  
> 
> What many people don't know it that you cannot set a record's status
> to
> ALTERED while the screen is in FINDMODE.  You can change the record
> buffer all
> you want, but the ALTEREDRECORD flag will not change from NEW,
> NOTALTERED,
> NOTDELETED.
> 
> I know this has caught me before when I was trying to perform a PUT in
> the
> EXIT procedure. You might try putting the NEED option on your output
> FILE.
> That tells Quick to treat the file as ALTERED even if it isn't at the
> time of
> the PUT.
> 
> Good luck,
> Matt Ohmes 8-)
> Cognos Corp
> = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> = = =
> Subscribe: "subscribe powerh-l" in message body to
> majordomo@lists.swau.edu
> Unsubscribe: "unsubscribe powerh-l" in message to
> majordomo@lists.swau.edu
> powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
> This list is closed, thus to post to the list, you must be a
> subscriber.
> 
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.