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 -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Richard Baird Sent: Friday, July 20, 2007 10:46 AM To: [email protected] Subject: Strange commit changes action behavior when using parent window and dialog Hi Folks, I'm seeing what seems like strange behavior when using commit changes to save a parent record after a child dialog closes....Here is the scenario..... 1. I have an Active Link that opens a dialog window when a user selects a record on the parent form and a particular field is null 2. The user selects a value on the dialog and then clicks a button to indicate the selection 3. I then have an Active Link that has the following actions: - Commit Changes to write the value back to the parent form - Send Event to parent indicating the value has been selected and sent back - Close Window 4. I then have an Active Link on the parent window that executes on the event sent above and performs a commit changes action to write the record back to the DB with the new field value. When I log this, it looks like things are working correctly, however the parent record is never written (nothing in SQL log either) and the save button is lit. The value is returned to the parent window, but the DB write isn't done. It is almost like the second commit changes is running in the context of the dialog window (which is now closed) instead of the parent window, but the log clearly shows it running on the parent after the event is received. Any Ideas...? Windows Server environment ARS 6.3 patch 20 SQL Server 2000 Thanks, Richard ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
