Hi Joe,
I understand what you are saying. I wasn't too clear, in the scenario I
detailed below there are two Commit Changes actions. The 2nd Commit Change
could easily be replaced with Run Process: Perform-Action-Apply and get the
same results.
AL 1 (on parent form)
On: btnOpenDlg
Ex Order: 1
Action 1: Open window
AL 2 (on child from)
On: btnSaveDlgValue
Ex Order: Doesn't Matter
Action 1: Commit Change (sends value back to parent form)
AL 1 (on parent form)
Action 2: Commit Change (saves parent record)
OR
AL 1 (on parent form)
On: btnOpenDlg
Ex Order: 1
Action 1: Open window
AL 2 (on child from)
Ex Order: Doesn't Matter
Action 1: Commit Change (sends value back to parent form)
AL 3 (on parent form)
On: btnOpenDlg
Ex Order: 2
If: 'zTmpValueFromChild' != $ NULL$ OR 'zTmpValueFromChild' != "Other Value
You Do Not Want to Trigger a Commit"
Action 1: Commit Change (saves parent record)
Jason
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza
Sent: Friday, July 20, 2007 2:43 PM
To: [email protected]
Subject: Re: Strange commit changes action behavior when using parent window
and dialog
**
Commit Changes on opening of a dialog box is designed only to pass the
values from the dialog box to the parent form.
No saves happen as a result. If you want it to save changes as soon as
control is returned to the parent window you need to do a
Perform-Action-Apply on the Parent form on return of control to that parent
form..
Joe
-----Original Message-----
From: Action Request System discussion list(ARSList) [
<mailto:[email protected]> mailto:[EMAIL PROTECTED] Behalf Of Jason
Miller
Sent: Friday, July 20, 2007 2:38 PM
To: [email protected]
Subject: Re: Strange commit changes action behavior when using parent window
and dialog
Just wondering if wondering if sending events is more complicated than
needed?
You could have a commit change action on the same AL that opens the dialog
after the window open action? Or you could do in a separate AL that fires
later on the same action as the AL that opens the dialog but has a different
"Run If" to validate the data from the dialog window before committing.
I have done this a number of times without having to sending events between
parent and child. This may not directly address the issue with nothing being
committed to the DB but maybe taking out the sending of events between
parent and child may help?
Jason
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
