I'm using a simple event to send a message from a child window to a parent
window.
The event is done after a Save button is pushed on the child window. When
the event is received by the parent window all that happens is a guide is
called. In this guide there are 8 active links that do ONLY 3
Title: RE: Send event woes...
**
You wouldn't happen to have a stray COMMIT CHANGES in the mix somewhere, would you?
-Original Message-
From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of William Rentfrow
Sent: Wednesday, July 12, 2006 3:07
) on behalf of Kaiser Norm E
CIV USAF 96 CG/SCWOE
Sent: Wed 7/12/2006 3:24 PM
To: arslist@ARSLIST.ORG
Subject: Re: Send event woes...
**
You wouldn't happen to have a stray COMMIT CHANGES in the mix somewhere, would
you?
-Original Message-
From: Action Request System discussion list(ARSList
Title: RE: Send event woes...
**
William:
A commit changes action will ALWAYS save to the database unless there is an error (pattern mis-match, value not within specified allowed values, etc.) I suspect there is a Commit Changes action somewhere that is fired off on the parent form.
James
, StrataCom
[EMAIL PROTECTED]
O 952-432-0227
C 701-306-6157
-Original Message-
From: Action Request System discussion list(ARSList) on behalf of McKenzie,
James J C-E LCMC HQISEC/L3
Sent: Wed 7/12/2006 3:43 PM
To: arslist@ARSLIST.ORG
Subject: Re: Send event woes...
**
William:
A commit
Title: RE: Send event woes...
**
William:
And that PERFORM-ACTION-APPLY was calling to save data to the database.
Yes, a COMMIT CHANGES from the Child to the Parent will just do a 'push' of data back onto the parent form. However, this is NOT true with the parent form, as this will cause
6 matches
Mail list logo
