P
Piotr Ryszkiewicz
Guest
Hi Mike, Thanks for answers. But, as always, anwers generate more questions
1. Honesty, I don’t like this idea, it would force me to create some wrapper around the form with part of the logic there. It can be done, but it’s not nice I think. Isn’t there something better ? BTW, I did not observe the effect you described, but it reminds me one question I forgot to ask previously (see point 5 below) 2. It does work, but has unwanted side effect – it fires also when pressing Cancel button. How to avoid that ? 3. I am afraid I don’t understand L . I know there is VALIDATE method which is called when „OK“ button is pressed. But how can I influence what is it doing ? I see it can’t be overridden. I thought that I could use Validating or Validated methods on form level, but these does not seem to fire when I call this-object:validate(). Moreover, the ‚e‘ argument to these is of different type, which does not provide Cancel property. 4. This gives me he name of the form. But I wanted the name of the screen object on which the current running trigger was fired. 5. If STOP event happens inside the form I can’t start this form again without restarting the session. The only workaround I found is to create ON STOP block around the piece of code inside the form which may cause STOP event. Can it be done in better way ? ON STOP around the code which calls the form does not work. Piotr
Continue reading...
Continue reading...