Re: NT/W2K users as Access Users

From: Bruce Hensley (bhensley_at_bechtel.com)
Date: 03/19/04 

Date: Fri, 19 Mar 2004 07:35:06 -0800

TC,

Thanks for the review.

I should have mentioned, we are using Access 97.

We set AllowBypassKey. But, I can't find anything in help about a DDL
parameter.

We use a frontend/backend arrangement, with linked tables and all forms
driven from queries. Sometimes the backend is Access, sometimes Oracle,
sometimes a combination of both. But, we keep the frontend on the server
with the backend. We have no more than 20 users, probably 3, or less,
concurrent. We keep a separate isolated copy of the frontend for
development, and back up the server 3 times a day.

I'm not clear on how I should set up security on the backend when it is
Access.

Thanks again.

Bruce

"TC" <no@email.here> wrote in message
news:405a6ad5$1_4@news.chariot.net.au...
> 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
> >
> >
>
>

Relevant Pages

  • Re: NT/W2K users as Access Users
    ... key down when they open the database. ... bypassing all your startup code. ... > that gets the network user ID and compares it to the Access user ID. ... If another network user tries to start the app with someone else's ...
    (microsoft.public.access.security)
  • Re: Problem running .NET CF 1.0 apps on CE 4.2 Core
    ... I have tried it with an app that prints to stdout when no command line args ... I have also tried with a simple windows form that does nothing. ... that looks to me like something in the startup code for the managed code ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Different focus.
    ... I would (and did behind my original response) suspect there's something in the startup code for the app that is timing/system dependent so that there is a specific reason on the offending system. ...
    (microsoft.public.vb.general.discussion)
  • Re: Compact and repair problems
    ... got an error that states "Microsoft Access has encountered a problem and ... key down while opening the copy so the startup code doesn't execute. ... module and compile the code if it's not compiled. ... import all objects from this copy into the new database. ...
    (microsoft.public.access.gettingstarted)
  • Re: Selecting records for print
    ... > problem on a datasheet refresh, or a resize of a form. ... I don't recall hearing of this as a problem before. ... You could create this database (in the current user's Temp ... >> folder), and create the table in the database, in your startup code, ...
    (microsoft.public.access.modulesdaovba)