Johannes Öberg wrote:
Thanks!
What is the call I make to perform the same action as when pushing the Save
Record button?
Starts making a "save" macro ("record" the save action with the macro
recorder or write your own basic code) and place a button who calls this
macro
/J
2010/5/20 Fernand Vanrie <[email protected]>
Johannes Öberg wrote:
Wow, if that's what it takes, it seems easier to write the app in C++ or
something...
No :-) just basic will do the job, you can find a lot of examples on the
net
How can I disable the navigator buttons but still call their functionality
Use the Form-properties where you can define what the user can or cannot
do with the form and the OO-buttons will been adapted to these behaviour.
place then some new buttons on the form who are macro driven
navigator, but then the user can reenable them
If you load only the form without its toolbars, for most users it becomes
hard to change the properties, and do not forget the GUI-user has only
"view" rights on the Tables
(not really a problem, but
not the "right solution").
Thanks /J
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
