Then if you assess the currentuser() in code or macro you can check for a
selected user name before
allowing a macro or code to continue.
The 'hardway' involves implementing security. Basically Security was always
ON, but the default use (Admin) and all permissions are accessible. It is
somewhat complex but allows for lots of control over specifics such as who
can delete or edit specific objects.
Still, it is more easy as Scott is hinting at to 'mask' those specifics in a
form. To put it into effect for a specific user, will require some kind of
log-on, or at least a password when accessing a particlular feature.
"Scott McDaniel" <junk (AT) junk (DOT) com> wrote
Quote:
The easiest way is to (a) disable the database window on startup (along
with
the hotkeys that allow users to bring up the db window and (b) disable the
shift-key bypass so that users cannot hold down the shift key to bypass
the
startup options. The theory here is that if users cannot GET to the
tables,
they cannot delete data from them!! |