sharing database FORMS only

  • Thread starter Thread starter mezzanine1974
  • Start date Start date
M

mezzanine1974

I designed a database to be used in the server of my company. I want
to enable my colleagues to use FORMS ONLY which has been designed as
interface for themselves. However, i can not find a way yet not to
allow my colleagues to use TABLES directly. Because, tables contains
sensitive and important data and i am worrying from being destroyed by
users.
What do you suggest to me ?
 
mezzanine1974 said:
I designed a database to be used in the server of my company. I want
to enable my colleagues to use FORMS ONLY which has been designed as
interface for themselves. However, i can not find a way yet not to
allow my colleagues to use TABLES directly. Because, tables contains
sensitive and important data and i am worrying from being destroyed by
users.
What do you suggest to me ?
Click to expand...

There are various methods of keeping users out of your design, some easier
to break than others. You could start by hiding the database window, hiding
built-in menus and setting a startup form (Tools, Startup). You could also
disable the bypass (shift) key. You could then look at applying user-level
security but that is a major learning task and you may not need it if your
users aren't the curious type.

As an aside, if your data is *very* sensitive then don't use Access to store
it, it just isn't secure enough.

HTH - Keith.
www.keithwilby.com
 
Also, convert the front end into a .mde. This will prevent users from
altering forms, reports, and modules. Of course they will be able to edit
data but they won't be able to change table structure for any table that is
linked to the backend.

Keith said:
I designed a database to be used in the server of my company. I want
to enable my colleagues to use FORMS ONLY which has been designed as
Click to expand...
[quoted text clipped - 3 lines]
users.
What do you suggest to me ?
Click to expand...

There are various methods of keeping users out of your design, some easier
to break than others. You could start by hiding the database window, hiding
built-in menus and setting a startup form (Tools, Startup). You could also
disable the bypass (shift) key. You could then look at applying user-level
security but that is a major learning task and you may not need it if your
users aren't the curious type.

As an aside, if your data is *very* sensitive then don't use Access to store
it, it just isn't secure enough.

HTH - Keith.
www.keithwilby.com
Click to expand...
 
Back
Top