Gene, you can put the name of the event or method (must have code in it) in the debugger, and this should force the debugging into this method or event.
In the worst case, you can SET COVERAGE TO FILE to see what lines are executed. May be something is bad behaving because some kind of binary corruption, like the one that do not throw errors directly when opening the class or form, but makes it bad behave. El 13/10/2015 6:38 a. m., "Gene Wirchenko" <[email protected]> escribió: > At 16:58 2015-10-12, Ted Roche <[email protected]> wrote: > >> I'll bet your form has a private data session and SET STEP is scoped >> to the data session. >> > > You would lose that bet. I do not use private data sessions. > > Add a breakpoint in the debugger for SET("STEP") and you'll find where >> it gets turned off. >> > > I did not state that it gets turned off but that it is as if it does > get turned off. When my form is show()ed, that is when it happens. This > is a bother as I want to be able to follow through the validation of the > form. In the case that I wrote about, I could not put anything in the OK > button that starts the reporting without modifying the superclass. > > [snip] > > Sincerely, > > Gene Wirchenko > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/cagq_jumzbaq7vkxctxmbfsas6wf_dh8dlzafxeuj4yxtebd...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
