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 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
