<< I don't think you can get any form properties until after it is rendered, making the ON AFTER START the earliest to begin querying or setting properties. >>
Well, it works fine in the non-compiled version of the code -- if the compiled code executed the same way the non-compiled code worked, I wouldn't have a problem. RBTI_FORM_MODE (the variable, not a PROPERTY command) is certainly available in the before start EEP, and correctly reported in the full version of the product. Since this particular setting is determined by the actual command used to start the form, it's not clear to me why one would have to wait until instantiation of the form to get the information. In the short term I've moved the logic from before to the after start EEP so that the form will run in both the compiled and regular versions. The difference is aesthetic only -- the user will see the form while they're prompted for some information that determines whether the form will actually be available to them or not. -- Larry
