Larry, 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.
----- Original Message ----- From: "Lawrence Lustig" <[EMAIL PROTECTED]> To: "RBASE-L Mailing List" <[email protected]> Sent: Tuesday, July 08, 2008 10:27 AM Subject: [RBASE-L] - Compiler gets RBTI_FORM_MODE wrong? > I'm seeing a possible bug in the latest 7.6 compiler. > > When I place the statement > > PAUSE 2 USING .RBTI_FORM_MODE > > in both the BEFORE START and AFTER START EEPs of a form (any form, it looks > like) I get different values reported from the two EEPs. The first value > reported is incorrect, and the second is correct. > > For instance, if I do EDIT USING Test the before start EEP reports that the > form is in ENTER mode and the after start EEP reports it is in EDIT mode. If > I do ENTER USING Test, I get the opposite behavior. > > It works fine in the full 7.6 product (the same, correct, form mode is > reported in both EEPs), just the compiled version gets it wrong. > > Can someone verify this is happening on your compiled program as well. All > you have to do is create a simple form with the two eeps and then ENTER and > EDIT USING that form from inside compiled code. I want to eliminate the > possibility of DLL mismatches. > > Also, is there a separate reporting mechanism for possible issues with the > compiler? I don't see it as an option at http://rbase.com/rbg7rdcc/. > -- > Larry >
