PUT's not working in EXIT procedure

[Deskin, Bob]

Matt's answered the first question.
The NEED option is independent of mode and should work in FINDMODE. It
tells QUICK to treat the record as if the the status ALTEREDRECORD was
true. Keep in mind, it's not that you can't update in FINDMODE, it's
that a changed value won't set ALTEREDRECORD to true.
You can change status if no mode is true. I just tested it in 7.29.C8 on
MPE/iX.

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: 	Michael C. Lee[SMTP:mclsys@home.com]
> Sent: 	Sunday, August 16, 1998 4:02 PM
> To: 	MattO1@aol.com
> Cc: 	KPCUMMIN@GAPAC.com; powerh-l@lists.swau.edu
> Subject: 	Re: PUT's not working in EXIT procedure
> 
> Just a couple of observations:
> 1) It would seem impossible to be in FINDMODE in the EXIT procedure.
> 2) If you are in FINDMODE I doubt the NEED option would work anyway
> (Bob?).
> 3) I have found that being in no mode can also contribute to not being
> able to
> change the record status under certain circumstances (Bob??).
> 
> 
> Regards,
> 
> 
> Michael Lee
> MCL Systems Inc.
> 
> 
> MattO1@aol.com wrote:
> 
> > 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.
> 
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
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.