Access 2002 security on a local PC

[Guest]

Situation is access on a local pc - not a network.

I used in access 2002 the security option using the wizard security option
on user level on my access database (covers several objects - including
password). It works on my lokal pc perfectly.
So i want to distribute this secure database - including all objects -
without loosing the security to prevent copy etc.
Testing this on another local pc (not a network), access 2002 doesn't
establish the security. It look likes that access on the other local pc uses
the basis secure file.
PS Visual Basic or SQL are not use, but regular access functionality for
making tables, forms, report and macros.

The help function from access 2002 gives me no satisfied answer/solution.

Can you help me?

(e-mail address removed)

 

[Alex White MCDBA MCSE]

Hi,

The trick here is the security database is by default the system.mdw file,
store this file on a network share and then use the wrkadmin.exe tool on
each computer to point to that file on the network.

Hope it helps.

Regards

Alex White MCDBA MCSE
http://www.intralan.co.uk

 

[Keith]

Situation is access on a local pc - not a network.

I used in access 2002 the security option using the wizard security option
on user level on my access database (covers several objects - including
password). It works on my lokal pc perfectly.
So i want to distribute this secure database - including all objects -
without loosing the security to prevent copy etc.
Testing this on another local pc (not a network), access 2002 doesn't
establish the security. It look likes that access on the other local pc
uses
the basis secure file.

If users on other PCs can open your application without joining your
workgroup then user-level security has not been applied correctly. If you
haven't yet done so then read the MS FAQ on security, there's a link to it
on my web site. There's also a step-by-step example there too but please be
sure to work on copies of your files since it's so easy to lock yourself
out.

Regards,
Keith.
www.keithwilby.com

 

[TC]

The trick here is the security database is by default the system.mdw file,
store this file on a network share and then use the wrkadmin.exe tool on
each computer to point to that file on the network.

Sorry, that is bad advice. Amongst other things, it will impact /every/
database on each PC.

Instead, the poster should:

(1) Create a /new/ workgroup file for the secured database. (Do not use
the default file - unless you want to leave a big security hole that
lets people break in to your database.)

(2) Distribute that new workgroup file - being careful /not/ to
overwrite the default file on the user PCs, then

(3) Give each user a shortcut which uses the /wrkgrp switch to select
that workgroup file, when starting that particular database.

However, the OP is clearly missing several other important steps.
He/she should get a written list of detailed instructions. No-one has
any hope of learning user-level security just by fooling around, or
using the wizard.

HTH,
TC