472,108 Members | 1,463 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 472,108 software developers and data experts.

Restrict user access to tables in MDE file

Does anyone know if it is possible to prevent a user from accessing
the tables in an MDE file? I can go to my start-up menu and limit
access to various functions, etc. I could even disable the 'close'
button on the forms. However, all a user has to do is hold the
SHIFT key down while launching the MDE application to bypass the
start-up menu.

I would like to limit any kind of data access (add/delete/modify)
through the forms that I have created. The purpose of the MDE is to
block access to my VB code.

The MDE file has linked tables to a centralized mdb file. So, I still
need the user to have the flexibility to access the "Linked Table
Manager" and to "compact" database (MDE grows every time you use it
even though no data is stored in the MDE).

Is it possible to 'hide' that tables. Unfortunately, if someone had
'View - Hidden Objects' selected in their Options, they would see the
hidden tables.

Thank you in advance for any ideas.
Nov 12 '05 #1
5 10226
You'll have to use the Access user-based security. Read the Access
Security FAQ available on MS Knowledge Base site:

http://support.microsoft.com/default...09&Product=acc

And the Security white paper (Acc 95 - but, can be used for all versions
[except 2.0]):

http://support.microsoft.com/default...55&Product=acc

HTH,

MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)
Jay McGrath wrote:
Does anyone know if it is possible to prevent a user from accessing
the tables in an MDE file? I can go to my start-up menu and limit
access to various functions, etc. I could even disable the 'close'
button on the forms. However, all a user has to do is hold the
SHIFT key down while launching the MDE application to bypass the
start-up menu.

I would like to limit any kind of data access (add/delete/modify)
through the forms that I have created. The purpose of the MDE is to
block access to my VB code.

The MDE file has linked tables to a centralized mdb file. So, I still
need the user to have the flexibility to access the "Linked Table
Manager" and to "compact" database (MDE grows every time you use it
even though no data is stored in the MDE).

Is it possible to 'hide' that tables. Unfortunately, if someone had
'View - Hidden Objects' selected in their Options, they would see the
hidden tables.

Thank you in advance for any ideas.


Nov 12 '05 #2
NB
User should never have access to the database window.
You can disable the Shift key, check out the Access Web for the sample code
http://www.mvps.org/access/modules/mdl0011.htm

NB
Nov 12 '05 #3
Try looking in Tools, Startup.
Uncheck all those boxes. Make a backup first because you won't be
able to get in either. :)
Pachyderm

ja*********@hotmail.com (Jay McGrath) wrote in message news:<e5**************************@posting.google. com>...
Does anyone know if it is possible to prevent a user from accessing
the tables in an MDE file? I can go to my start-up menu and limit
access to various functions, etc. I could even disable the 'close'
button on the forms. However, all a user has to do is hold the
SHIFT key down while launching the MDE application to bypass the
start-up menu.

I would like to limit any kind of data access (add/delete/modify)
through the forms that I have created. The purpose of the MDE is to
block access to my VB code.

The MDE file has linked tables to a centralized mdb file. So, I still
need the user to have the flexibility to access the "Linked Table
Manager" and to "compact" database (MDE grows every time you use it
even though no data is stored in the MDE).

Is it possible to 'hide' that tables. Unfortunately, if someone had
'View - Hidden Objects' selected in their Options, they would see the
hidden tables.

Thank you in advance for any ideas.

Nov 12 '05 #4
TC

"Pachydermitis" <de******@hotmail.com> wrote in message
news:4f**************************@posting.google.c om...
Try looking in Tools, Startup.
Uncheck all those boxes. Make a backup first because you won't be
able to get in either. :)


Sure he could! Just open the db using dbengine.opendatabase() and reset the
relevant properties.

TC
Nov 12 '05 #5
"TC" <a@b.c.d> wrote in message news:1074662335.830060@teuthos...

"Pachydermitis" <de******@hotmail.com> wrote in message
news:4f**************************@posting.google.c om...
Try looking in Tools, Startup.
Uncheck all those boxes. Make a backup first because you won't be
able to get in either. :)
Sure he could! Just open the db using dbengine.opendatabase() and reset

the relevant properties.


In addition to that, if the users need to be able to use the Linked Table
Manager to change or refresh the links, then they will easily see the path
to the back end file and could link or import those tables into a separate
MDB.

It's important to make the distinction that you are obfuscating, not
securing. While this can be very effective against many (perhaps most) of
your users, it is not much of a barrier against users who have any
familiarity with Access.
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Nov 12 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

3 posts views Thread by Paul | last post: by
4 posts views Thread by Neil Coleclough | last post: by
5 posts views Thread by toddles666 | last post: by
2 posts views Thread by phpnoob | last post: by
3 posts views Thread by =?Utf-8?B?R1ROMTcwNzc3?= | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.