How can I block user access to dbs through Explorer 1

[paradiso]

I have a split database and I would like to allow two levels of security to the users as they access a single set of tables on a network drive (the front-end db is resident on each individual's local PC).

Through the user interface I can disallow the one set of users from changing information where they shouldn't, but how can I prevent them from using Windows Explorer and simply opening the back-end data file and getting direct access to the data?

When I apply security to the back-end database, my queries bounce when I log in as the less-secure user. I am currently trying to dynamically re-link the tables by deleting the previous links and re-creating the table defs. This is suggested in an article from the Smart Access newsletter as a way to circumvent security through code. But I'm getting an invalid parameter error when I run the ' db.tabledefs.append TD1 ' line of code. (I've copied several code snippets verbatim -- bang head here).

Assigning a database password has failed me as well. Is there a simpler solution out there, or even some insight.

most grateful,
paradiso

 

[KyleS]

Sorry, this is a little off subject, but how did assinging a dB password fail you? (I'm not saying it didn't just seeing if there are any pit-falls I may not have been aware of)

How do you have this dB Secured? Even if you keep them out of the Backend what's to stop them from making an entirely new dB and getting to the tables through that?

You could set up some "home-made" security with a login form and what not and make that launch at startup (you'll need to disable the SHIFT key *shudder*) That way when your front end accesses the Backend, Access sees no security so everything works just fine, but when opened it won't let unauthorized people in. this has it's flaws too... It depends on what security you've got going and what level you're looking to attain... Kyle

 

[jebry]

Hi!

You can put the following code in a public function:

If CurrentUser <> &quot;YourLANName&quot; Then
DoCmd.Quit
End If

Then create a macro called autoexec which uses the RunCode action to call this function. Now you will be the only person able to open this database and it will not affect your links at all. If CurrentUser is not available to you, there are functions people have posted on this site to get the LAN name for you, or I can supply one if you need it.

hth
Jeff Bridgham
bridgham@purdue.edu

 

[Junior1544]

here's another thought, and this is what i did....

i use user level security built right into access... and i set the back end to use the same mdw as the front end... now if a user tries to get into the back end, they will be able to open it, and view and not edit if their account doesn't allow any edit's, or they can edit if they are alowed to edit... (i know, not to smart to allow users direct access to the tables, but my users don't know any thing about databases in general...)

and in the back end i made a little form that is in all red, that said that the person is not allowed in the database. and to get out. it has an OK button that is set to exit the database.... i didn't disable the shift key, but i did disable the f11 key... i kept the shift key so i can get in, and my users don't know about it... also, if you want to, you can hide the tables... then it makes it very hard to import or link the table into another db without knowing what the names are... just a few things that i have done...

--Junior JHauge@jmjpc.net
Life is change. To deny change is to deny life.

 

[paradiso]

Hi Kyle, jebry, and junior...,

Thank you so much for your quick replies. If I apply a database password to the back end, any time the user updates it they will get prompted for the password. Actually they get 'invalid password', which worse.

I understand Kyle's second point and will sure that my clients understand that if they want true security, they will need to upsize to a client-server system. MS Access isn't designed for high-security applications.

In this instance I am looking for a medium-security solution, and that is supplied by all of your excellent suggestions.

You are most kind.

gratefully,
paradiso

 

[Junior1544]

me and Jebry must have been typing at the same time i like that idea... i think i'm going to be using that in the futchure I never thought of that...

--Junior JHauge@jmjpc.net
Life is change. To deny change is to deny life.