Wow, if that's what it takes, it seems easier to write the app in C++ or something...
How can I disable the navigator buttons but still call their functionality from macros? I see you can set "Visible button" by rightclicking on the navigator, but then the user can reenable them (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
