MDE file

[Glynn]

I am trying to secure an application against Users being able to access
Tables, Queries etc>
MDE is not working for me on two counts:

1. after carefully 'converting' my database to 2002 format, and then
following the
screen instructions to Make and Save, I always get the error message
'MS Access
was unable to create an MDE database'.
Even though I did many months ago experiment with 'replication', the
database I
am trying to make an MDE was not part of that experiment, so I don't
think
that replication is the prblem.

2. even if I could make an MDE database it appears that Access 97 and Access
2000
users would be excluded from using this MDE application.

I have resorted to HIDDING the database files which would otherwise be
displayed,
if the user depressed the 'Shift' key while opening the database.

This is not a very satisfactory way to protect the database.

I there any other way (other than the cumbersome user-level security
processes).?

I will appreciate any guidance.

 

[Rick Brandt]

I am trying to secure an application against Users being able to
access Tables, Queries etc>
MDE is not working for me on two counts:

MDEs don't protect tables or queries. What you need is User Level Security.
While that is hackable it does at least require that the hacker obtain utility
programs to do so.

 

[tina]

it's impossible to *completely* secure an Access database, even using the
built-in User-Level security option. but there are various things you can do
to make your database "more" secure. suggest you take a look at Garry
Robinson's Real World Microsoft Access Database Protection and Security.

hth

 

[George Nicholson]

It is possible to simply disable the Shift key:
http://www.mvps.org/access/general/gen0040.htm
(This and a simple database-password is the most security any client has
ever asked me to implement.)

(Note: you might consider including a "backdoor" so you can turn Shift
functionality back on for yourself when necessary.)

HTH,

 

[Glynn]

George/Rick and Tina
Thanks for your inputs - I have however stumbled on a possible solution. I
find that by Right-clicking a Table/Qry etc, and selecting Properties I can
then tick the 'Hidden' Attributes - and the selected Table/Qry no longer
appears in the Database View.

My concern is that while it locks the Users out - it also locks me out
(apparently forever). I have not been able to find a way to restore the
Tables/Qrys etc, once I've 'hidden' them.

Do you know of any way to restore?

 

['69 Camaro]

Hi, Glynn.

If I may barge in . . . .

My concern is that while it locks the Users out - it also locks me out
(apparently forever).

Not at all. To view these hidden tables, select the Tools -> Options...
menu to open the Options dialog window. Select the "View" tab and mark the
Hidden objects check box. Close the Options dialog window and return to the
Database Window. All the objects that you've designated with the "hidden"
attribute appear in the list again, but show a greyed out icon next to the
name.

Be aware that anyone else who wants to see any hidden objects can use this
technique, too, so it isn't that safe. Another method is to name the tables
with a "USys" prefix, making them user-defined system objects. For example,
if a table were named tblEmployees, then it could be renamed
USysTblEmployees" and the user would have to have the "View System Objects"
option turned on -- which most folks don't -- to see them. When you rename
these objects as user-defined system objects, they will disappear from the
Database Window, unless you have the "View System Objects" option turned on
yourself. If that's the case, then use the same method to view them again by
repeating the steps above to unhide an object, but mark the "System objects"
check box in the Options dialog window, instead.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address so that a message will
be forwarded to me.)
- - -
If my answer has helped you, please sign in and answer yes to the question
"Did this post answer your question?" at the bottom of the message, which
adds your question and the answers to the database of answers. Remember that
questions answered the quickest are often from those who have a history of
rewarding the contributors who have taken the time to answer questions
correctly.

 

[Mohamed Hassan]

I am trying to secure an application against Users being able to access
Tables, Queries etc>
MDE is not working for me on two counts:

1. after carefully 'converting' my database to 2002 format, and then
following the
screen instructions to Make and Save, I always get the error message
'MS Access
was unable to create an MDE database'.
Even though I did many months ago experiment with 'replication', the
database I
am trying to make an MDE was not part of that experiment, so I don't
think
that replication is the prblem.

2. even if I could make an MDE database it appears that Access 97 and Access
2000
users would be excluded from using this MDE application.

I have resorted to HIDDING the database files which would otherwise be
displayed,
if the user depressed the 'Shift' key while opening the database.

This is not a very satisfactory way to protect the database.

I there any other way (other than the cumbersome user-level security
processes).?

I will appreciate any guidance.