I just tested this and Commit Changes does not actually save to the database.  
All it does is pass the "On Close" field mappings originally specified in the 
"open window" action back to the parent form.

If it always saved to the DB the action wouldn't be available in Display only 
forms, etc.

However, you DID help me track down another embedded run process 
PERFORM-ACTION-APPLY that was buried in the code - and THAT was causing the 
problem. :)  It turns out my bypass before did bypass this one extra step, 
making it appear tied to the EVENT send.

William Rentfrow
Principal Consultant, 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 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 McKenzie 
  

-----Original Message----- 
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] 
On Behalf Of William Rentfrow 
Sent: Wednesday, July 12, 2006 1:35 PM 
To: arslist@ARSLIST.ORG 
Subject: Re: Send event woes... 

Possibly ....? I'll have to look. 

Shouldn't that just send values to the parent form though?  And not the DB? 

William Rentfrow 
Principal Consultant, StrataCom 
[EMAIL PROTECTED] 
O 952-432-0227 
C 701-306-6157 



-----Original Message----- 
From: Action Request System discussion list(ARSList) 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) [mailto:[EMAIL PROTECTED] 
On Behalf Of William Rentfrow 
Sent: Wednesday, July 12, 2006 3:07 PM 
To: arslist@ARSLIST.ORG 
Subject: Send event woes... 

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 direct sql calls 
and a few set fields on the parent window.  There are NO push fields at all. 

For some reason when the event is received by the parent window it saves the 
current record in the parent window.  I can see all of the workflow, etc, 
firing in logs - but there is NO triggering event logged that shows WHY it 
saved the record.  And I REALLY do not want it to save the record in the parent 
window.

I have double checked all workflow to insure there is no embedded RUN PROCESS 
PERFORM-ACTION-APPLY and that sort of thing.  There is literally no workflow 
that initiates the record save.  No push fields, no run process, no other 
events, nothing.

I confirmed this by turning off the event send from the child window.  The 
parent record does not save. 

I also added a button on the parent window that calls the same active link 
guide as the event.  In that instance all of the same steps are being taken 
EXCEPT an event is not sent.

It only saves the record when it receives this event.  I'm baffled.  It makes 
absolutely no sense to me. 

William Rentfrow 
Principal Consultant, StrataCom 
[EMAIL PROTECTED] 
O 952-432-0227 
C 701-306-6157 

_______________________________________________________________________________ 
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org 

__20060125_______________________This posting was submitted with HTML in it___ 

_______________________________________________________________________________ 
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org 

__20060125_______________________This posting was submitted with HTML in it___

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org

Reply via email to