Re: NT/W2K users as Access Users
From: TC (no_at_email.here)
Date: 03/19/04
- Next message: Br1an_g: "Kicking User Out"
- Previous message: Kevin Yu [MSFT]: "Re: Problem changing password using ADOX.Catalog.Users(User).ChangePassword"
- In reply to: Bruce Hensley: "NT/W2K users as Access Users"
- Next in thread: Bruce Hensley: "Re: NT/W2K users as Access Users"
- Reply: Bruce Hensley: "Re: NT/W2K users as Access Users"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 19 Mar 2004 14:09:00 +1030
Seems fair to me - unless I'm missing something really obvious!
Just a few points.
- Make sure the users can not bypass your startup code by holding the shift
key down when they open the database. There is a property that you can set
to prevent that occurring, but be careful to set the DDL parameter to True
in the CreateProperty statement, when you create that property. Otherwise, a
non-administrative user can run VBA code from any suitable client, to delete
that property from your database. Then they can start it with the shift key
down, bypassing all your startup code.
- Er, this is a multi-user database with a single copy of the MDB file on
the server? That is a sure recipe for (a) database corruption, and (b)
difficulty distributing code updates. The application should be split into a
so-called front-end/back-end structure. The BE database has all of the
tables, but nothing else. The FE database has all of the queries, forms,
reports, macros & modules, and links to the actual tables in the BE. Each
user should have their own copy of the FE - on their own PC, or on the
server.
HTH,
TC
"Bruce Hensley" <bhensley@bechtel.com> wrote in message
news:ulfbB$TDEHA.3348@TK2MSFTNGP11.phx.gbl...
> The following model seems to work for us, but I would appreciate any
advice
> as to the risks, or a simpler/safer way to accomplish the same goals.
>
> The goals are:
>
> - utilize Access user-level security within the application
> - not require users to learn a new password for the application
> - allow authenticated network users to run the app without Access login
>
> We are working on a local intranet, with the MDB and MDW on a fileserver.
>
> We create user accounts in Access with the same user ID as their network
> username, but without passwords.
>
> In Access, there is an AUTOEXEC, or procedure attached to the startup
form,
> that gets the network user ID and compares it to the Access user ID. If
> they don't match, then the application exits. Since the user must first
log
> on to the network with network user ID and password, we know the user is
> valid. If another network user tries to start the app with someone else's
> Access user ID, the app will then exit.
>
> To further simplify the startup, we launch the application using a
VBScript
> file. The VBS file gets the network username and launches the Access app,
> passing it the user ID and a blank password. This way, the user need not
> even be prompted for user ID and password.
>
> Thanks,
> Bruce Hensley
>
>
- Next message: Br1an_g: "Kicking User Out"
- Previous message: Kevin Yu [MSFT]: "Re: Problem changing password using ADOX.Catalog.Users(User).ChangePassword"
- In reply to: Bruce Hensley: "NT/W2K users as Access Users"
- Next in thread: Bruce Hensley: "Re: NT/W2K users as Access Users"
- Reply: Bruce Hensley: "Re: NT/W2K users as Access Users"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
