QUICK automatic warning message

Deskin, Bob Bob.Deskin@Cognos.COM
Tue, 3 Apr 2001 15:57:07 -0400


As far as I know, there's no "easy" way to prevent this. The message is
based on tests done just before actually changing the mode or doing whatever
action actually caused the message. There's no procedural trap at that point
in time.

The only way I know of (of course now there'll be dozens of other methods
posted :-) ) is to delay the actual record change until you're sure you want
to write. This usually means storing values in temporaries and setting a
temp flag indicating that you want to save the values. Then check the flag
in the PREUPDATE procedure and move the values in.

Bob Deskin              
PowerHouse Web Product Manager and Senior Product Advisor
Application Development Tools, Cognos Inc.
bob.deskin@cognos.com (613) 738-1338 ext 7268 FAX: (613) 727-1178
3755 Riverside Drive P.O. Box 9707 Stn. T, Ottawa ON K1G 4K9 CANADA

-----Original Message-----
From: GGrimm@pcc-structurals.com [mailto:GGrimm@pcc-structurals.com]
Sent: April 3, 2001 3:45 PM
To: powerh-l@lists.swau.edu
Subject: QUICK automatic warning message


     Has anyone an idea how to prevent the QUICK message "Data has been 
     changed but not updated. Repeat the action if this is ok." to be 
     programatically NOT show.  I've a POSTFIND process that retrieves a 
     DESIGNER file's record and when not found, does a few LETs to items in 
     it. 
     
     When the screen user decides not to do an Update and just do another 
     FIND, I want no automatic warning message to show.  Am I missing 
     something obvious?


= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l@lists.swau.edu
Subscribe: "subscribe" in message body to powerh-l-request@lists.swau.edu
Unsubscribe: "unsubscribe" in message body to
powerh-l-request@lists.swau.edu
http://lists.swau.edu/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.