[AccessD] Database Needs Password Protection

Dan Waters dwaters at usinternet.com
Mon Apr 26 08:57:33 CDT 2010


Whatever ability people have now in the FE won't change by joining the BE
file to a workgroup, even if the two user names and passwords are the same.
I would suggest setting up a user name/password for opening the BE to
something not in the FE - just so your customer is clear that there is a
difference.  You might set up a test that your customer can duplicate so
they are confident.

By the way, I've used the technique that Lambert suggested at one of my
customers.  I got this out of a book named, "Real World Microsoft Access
Database Protection and Security."  It's currently available on Amazon.  It
works just fine, but you'll need to practice it and then explain it to the
IT folks at your customer.

Dan

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
Sent: Monday, April 26, 2010 8:42 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Database Needs Password Protection

Dan:

Will people in the workgroup who can link to the back end through the front
end also be able to open the back end directly and change the data there?

Rocky
 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters
Sent: Monday, April 26, 2010 6:28 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Database Needs Password Protection

Hi Rocky,

I think that you could:

1) Create a new blank workgroup file (a copy of System.mdw).  Give it a
unique name (BTWBE.mdw).

2) Join each BE file to BTWBE.mdw.

3) Create a new user name and password for your client.  

4) If you want a little more security, create a procedure that shuts down
the BE if CurrentUser = "Admin".  Run that procedure from an AutoExec in the
BE file.

HTH!
Dan

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
Sent: Sunday, April 25, 2010 2:28 PM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Database Needs Password Protection

Dear List:

In my manufacturing software users log in with a password that gives them 1)
read only, 2) read write, 3) administrator access.  But the back end is wide
open. So far this has not been a problem.  Everywhere the system is
installed people 'play by the rules'.  

Now comes a client who wants access to the back end restricted.  So I'm
trying to think of way to do that with the least disruption to the system
which BTW supports multiple back ends - the user can open a different back
end through an 'Open a Database' utility.

In the code, of course, I'd have to change all occurrence of 

set db = CurrentDb to 

Set db = DBEngine.OpenDatabase(gstrDB, False, False, ";pwd=" & gstrPWD)


where the password would be in gstrPWD.

Then I would have to add a utility accessible only by someone with admin
rights, to 1) set, 2) remove, and 3) change the password on the currently
linked back end.  Don't know what that code looks like but I suppose I can
figure it out.

Question is - is this the shortest distance between the two points?  Or is
there another approach which would be faster/better/easier?

 

MTIA

Rocky Smolin

Beach Access Software

858-259-4334

www.e-z-mrp.com <http://www.e-z-mrp.com/> 

www.bchacc.com <http://www.bchacc.com/> 

 

 

 


--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com




More information about the AccessD mailing list