[AccessD] Database Needs Password Protection

Hi Rocky:

In my FE/BE setups, the FE always rebuilds the links to the BE(s) when it
loads.  The linking code provides the BE password once per table, as it
builds a tabledef and adds it to the FE tabledefs.  After that, I use
'Currentdb' as normal.

Doug

On Sun, Apr 25, 2010 at 12:27 PM, Rocky Smolin <rockysmolin at bchacc.com>wrote:

> 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
>
>