Marc
The screen that you are customizing is a compiled .exe.
Customization Manager does not show you the source code of that screen, or allow you to modify it.
It does, however, allow you to write VBA code in the various Events.
In some cases the customization event will run before the host screen's event.
In other cases the customization event will run after the host screen's event.
In some Events (usually with a parameter called retval) your code can abandon that event.
For example in the Update control's OnUpdate event, which runs when the user clicks on SAVE, your code can cause the Save operation to be aborted and abandoned.
For a button, about all you have is the Click event, and, to my knowledge, there is no ability to "abandon the click".
However there is a workaround, which doesn't always work :)
Change a couple of properties on the button.
Set TabStop to false.
set Left to, say, -1000.
That effectively makes the button totally inaccesable to the user.
Now use the Insert Wizard to add your own button to "replace it".
Now when the user clicks "the button", it will be "your button", not the "real one".
If your code determines that you don't want to call PANOT00, then simply exit, and it won't get called.
If you decide that calling it is OK, then you must programmatically click the "real button".
And it is this bit that may not work.
Or if it works now, it may cease working in a future version.
Here's a couple of ways of possibly pushing a button.
If neither works, post the SL Version that you are using, and I might be able to do a little experimenting.
Call ApplSetFocus("TheButtonsName")
Call SendKeys(" ",true)
or
sivmyapp.controls("TheButtonsName").value = true
Hope that helps a bit.
Barry
Share
Report
40
All responses (
Answers (
