Warren,

The details you provide don't give us much insight as to where the specific problem might be. I know that you have been in regular contact with Tech Support  as you worked on your project, and that they are currently looking at your most recent set of support requests. Raymond and/or Alec should be getting in touch with you again shortly.

Warren,

The problem causing your crash has been found and fixed. In one of your field exit events you have a deferred macro call *@DeferredMacro", later in the same event you have an @AskUser call. The event loop that allows the user to answer the question in the @AskUser call was also allowing the deferred macro to run before programming was complete. Because the macro it invokes closes the form (I assume, you did not send the macro), and programming on that form is still actively running (because it is waiting on the user to answer the question in the @AskUser call), Sesame goes down - defeating the point of the deferred macro in the first place.

I fixed Sesame so that the event loop in @AskUser does not allow deferred macros to run. It will be available in the next release. In the meantime, to work around the problem you can either move the @DeferredMacro call so that it does not get called until after the @AskUser funtion has been called. Move the @DeferredMacro call so that it does not fall in the same logical section as the @AskUser function, or eliminate either function from the event. Any of these work-arounds will suffice.

In general, until the next release, remember that an @AskUser call may prematurely allow a deferred macro to run. To prevent this, always make sure that a @DeferredMacro call appears logically after any @AskUser calls within any programming that is likely to be invoked on the same initial event. There will be a note about this on the Workarounds page shortly.