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
2010/5/20 Fernand Vanrie <[email protected]>
Johannes ,
I was troubled with same problems, we finaly decided NOT to uses the OO
buttons for "Editing" only for "Viewing", and keeping the Gui-users as far
as posible from or "Tables"
We avoid to open OO-DBase-DOC (infact the Gui-user do not know of the
exitens of this DbaseDoc) we only "open" forms without any OO-bars
The GUI-user has view rights on the server and its Tables.
For "editing" we have macro driven buttons with scrambled macro's and a
hidden user who opens a new connection to do the table editing.
BTW: we also prefere to uses "Dialogs" to gather the user input
Hope it helps
Fernand
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
