PUT's not working in EXIT procedure

[MattO1@aol.com]

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.