Coded security question

  • Thread starter Thread starter John Vinson
  • Start date Start date
J

John Vinson

We prefer not to password the BE or create a workgroup file.
Click to expand...

Well, since those are the two methods (the latter being preferable,
passwording is about as secure as a three-wheel bicycle lock) that one
can secure a database, I guess the answer is No.
 
Thanks. I was thinking that maybe there might be hidden properties (like
AllowBypassKey) that could be appended to the database's properties
collection.
Click to expand...

Well, without security it's pretty easy to crack, but you can conceal
the database window and use your own custom toolbars so that the
"Tools" menu option isn't available. A determined user can get around
this though.
 
There are no properties that would prevent someone from importing or linking
to tables in another MDB. You could, as John suggests elsewhere in this
thread, add your own custom UI to the back-end to prevent a user getting
access (no pun intended) to the default, built-in Access UI, and importing
or linking tables that way. But without security, there would be nothing to
prevent anyone importing or linking tables programmatically, and that is not
at all difficult to do.

If you're just trying to prevent well-intentioned users from doing something
accidentally, this might be enough for your purposes. But it will not
prevent someone with a working knowledge of VBA and DAO from doing it
deliberately.
 
I think I wasn't very clear...sorry. I want to prevent linking to tables or
importing from from the BE via another mdb.

As an alternative... Is it possible to password the BE (database password)
and pass the proper password to the BE from the front end via VBA?

Thanks again,
Joe
 
Is there a way to code security in an unsecured Access 2000 back end to
prevent users from importing or linking to tables from another mdb? I have
already coded it to prevent the shift-key bypass. The BE has a user table
with their network usernames and database roles that are used with the front
end. We prefer not to password the BE or create a workgroup file.

Thanks for any tips or references.
 
Thanks. I was thinking that maybe there might be hidden properties (like
AllowBypassKey) that could be appended to the database's properties
collection.
 
Try this:
1) Remove the toolbars from all the clients. This makes
it difficult to just click on File/Get External Data and
View/Toolbars. What version of Access are you using?

I have a question for you... What did you do to
inactivate the [Shift] key bypass. I used to know one way
of doing it, years ago, but I've forgotten and several
people on this forum have asked this question.

Dank
(e-mail address removed)
 
I use Access 2000 and 2002, but I wound up porting the back end to SQL
Server.

The code is online in the MS Knowledgebase. Search the Access section for
"AllowBypassKey" or "SetBypassProperty".

Joe
 
Back
Top