----- Original Message ----- From: "Lawrence Lustig" <[EMAIL PROTECTED]> To: "RBASE-L Mailing List" <[email protected]> Sent: Tuesday, July 08, 2008 10:51 AM Subject: [RBASE-L] - Re: Compiler gets RBTI_FORM_MODE wrong?
> << > 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. > I see. You have by now explored clearing the VAR prior to the ENTER/EDIT using code that sets the MODE to see if the VAR is: A: NULL B: HasAValue I ask this because if my guess of how the compiler functions, there should be no difference between the standard version and compiled, with respect to timing and such. > 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 > > >
