Timing Issue With EpiViewNotification

I’m working on the UD02 form and allowing the user to search for records using a quick search. When the user makes a selection and the data loads into the form I need it to check a couple of things and make a decision, essentially, If ClosedDate is a real date and the ClosedCheckBox is checked then make the form read only.

When I load up the record from the search I’m noticing that the EpiViewNotification I’m running everything under is firing prior to the data being loaded into the form. This means when both conditions are met above, the form isn’t being set to read only because it doesn’t believe the conditions have been met.

Is there anyway to force an EpiViewNotification to run or delay it from running until the data is loaded?

With the help of my IT Manager we were able to figure out a solution. I needed an update to occur after the EpiViewNotification, but I knew if I simply put an oTrans.Update it would create an endless loop. The update needed to be controlled. We set a condition to call the update around a boolean variable. This helps prevent the endless loop from occurring.