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
I'm making an Invoice database more user friendly / screwup resistant.
Sent invoices are locked and not editable from the interface so people won't
change them by mistake (they are still editable in the table view, but
that's no problem). You can however view locked invoices and print copies
and make non-printing notes.
However, I'd like to disable the navigator save button for locked fields,
and would prefer not to have to disable the entire navigator.
I think the best way would be to somehow intercept the Save Button event,
but I don't know how.
The other approach I could think of is BeforeRecordChange, however, I don't
know how to find out what button was clicked.
Thanks
/Janoch
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
