suedo ULS

[Guest]

I am using Access 2002, but can't get the User Level Security features to
work with Multiple Users using a front end MDE file.

Unfortunately, I have some Access users who like me know just enough to mess
it all up. My goal is to limit other user's ability to modify the back end
tables directly in the backend database. I have code to record user's
actions in the front end datbase.

I have tried to password protect the backend database, but then the front
end database doesn't work.

Is there a way to password protect the backend database and send that
password in my forms? I can password protect the VBA Code of the front end
database.

Any suggestions or magic words of wisdom on ULS with multiple users using a
MDE file on a shared corporate server?

 

[Rob Oldfield]

What doesn't work with ULS? You're using the wizard to set it up the basic
starting point?

 

[Guest]

Rob,
Thank you for your reply. I will have up to 70 Users using 3 different
databases. The MDE files are in the same folder, 2 levels deep in the folder
structure, the mdb files are in the same folder, 3 levels deep. To conserve
I/O time, the user's copy the mde file to their desktop.

Can I use one security file for all databases/users? Would the user have to
copy the security file to their desktop as well. How can I link all MDE's to
the same security folder.

Simple questions, evidently it is the concept. I can create a ULS system on
my own desktop with a test database, but don't know how to implement in a
corporate environment with multiple users using a split database on a shared
server.

In all of my databases, I have a LOGIN screen, which upon successful login,
opens a temp form in ACHIDDEN mode and stores the user's ID and profile like
AUTHOR or USER. My forms check the user's profile on open or on current to
limit or allow modifications to the records.

Is there a simple way to block users from accessing the backend
tables/database without ULS?

 

[Rob Oldfield]

Rob,
Thank you for your reply. I will have up to 70 Users using 3 different
databases. The MDE files are in the same folder, 2 levels deep in the folder
structure, the mdb files are in the same folder, 3 levels deep. To conserve
I/O time, the user's copy the mde file to their desktop.

Slightly pointless. I/O is about getting data from the backend db - which
presumably is on a central network share somewhere.

Can I use one security file for all databases/users? Would the user have to
copy the security file to their desktop as well. How can I link all MDE's to
the same security folder.

Which mdw file is used is, by default, set up on a per machine basis. There
are various ways of setting it...

Run C:\Program Files\Microsoft Office\Office\1033\WRKGADM.EXE (or wherever
you've installed) on each machine.
(That's obviously labour intensive and I wouldn't use it in your situation.)
Update the registry setting
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\9.0\Access\Jet\4.0\Engines\Syst
emDB ... could do this in a login script.
Use shortcuts that look something like <path>\msaccess.exe <path>\FE.mde
/wrkgrp <path>\YourSecurityFile.mdw

The third option is my favourite as it allows you to specify a mdw *only*
for those mdbs that need it. The first two both mean that users will be
asked for a password *every* time.

Simple questions, evidently it is the concept. I can create a ULS system on
my own desktop with a test database, but don't know how to implement in a
corporate environment with multiple users using a split database on a shared
server.

Just a case of creating your mdw... copying it to a central share and then
pointing users at it by one of the methods above.

In all of my databases, I have a LOGIN screen, which upon successful login,
opens a temp form in ACHIDDEN mode and stores the user's ID and profile like
AUTHOR or USER. My forms check the user's profile on open or on current to
limit or allow modifications to the records.

Is there a simple way to block users from accessing the backend
tables/database without ULS?

No. There might be a way by playing with mdes and setting network security
options, but certainly not simple or reliable. ULS takes a bit of getting
used to... but if you need that kind of thing then it's worth the effort.