IGNORE SECURITY!

[Dave180]

Chris O'C wrote (a while back)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Access user level security is *always* on. Whatever workgroup (mdw file)
you're joined to when you open *any* Jet db file, if the admin user has a
password assigned, you'll be prompted for your user name and password.

Join an unsecured workgroup on your pc. The default system.mdw file
shouldn't have an admin password assigned, so you won't be prompted.

Chris
++++++++++++++++++++++++++++++++++++++++++++++++++++++++
I joined a new worgroup file on my NEW (MSA 2003) MDB.
It starts with MSA hidden and only one form (Window) open. Chris's solution
works great with this App - since it now hides the MSA User Signon panel,
which was not required.
However, as expected, all my other DBs on the same machine (or at least
every one I open as the session user) have joined the new workgroup. I need
security on all DBs except the new one.
When I distribute the new Db I wont know what security the end user will
have on their systems.
How best to overcome this please? Can the workgroup be assigned
programatically through a shortcut lnk? If so how please?

Regards,
Dave.

 

[Chris O'C via AccessMonster.com]

They can join your secure workgroup for the duration of the session if you
use a shortcut with a target like this (all one line):

"path to msaccess.exe" "path to mdb" /wrkgrp "path to secure.mdw"

Chris

 

[Dave180]

Thanks for the reply Chris,

Can either be done programatically?
I should know the SECURE DB users (and their environments etc)
But I won't know whats on the NEW Db systems.

I'll assume that MSA can't cope with this - since it uses Session Names for
Security.
This data will have been predetermnined before MSA is run (no matter what
the DB)

Can you suggest a tool that will create the LNK code requirements as your
suggestion?

My NEW DB CANNOT have security implemented (I won't know if MSA is even
installed on those machines)
My other distributables (using 2003) require ULS to present the correct
start-up options etc.

Is this a brick wall that won't be resolved without recourse to another
development tool?

Dave

 

[Chris O'C via AccessMonster.com]

Not sure I understand your first question. "Either" what? I was talking
about using a shortcut to open the secure db. What's the other alternative
you have in mind?

"But I won't know whats on the NEW Db systems."

Doesn't matter, as long as they have the right version of Access installed.
The shortcut will join the user to your secure workgroup before opening your
secure db. Whatever workgroup they're permanently joined to is ignored
during the session.

"I'll assume that MSA can't cope with this"

Access can cope with it. Problems are caused by user errors or corruption.
Both are solvable.

"since it uses Session Names for Security"

Don't know what you're talking about here. Access and Jet don't have session
names.

"Can you suggest a tool that will create the LNK code requirements as your
suggestion?"

The 10 finger tool. Type it in the shortcut's target and a send copy to each
user.

"(I won't know if MSA is even installed on those machines)"

Without MS Access, only the data in the tables can be used by other apps. No
other objects. Your forms, reports, code, etc won't work without Access
installed.

"Is this a brick wall that won't be resolved without recourse to another
development tool?"

User level security is complex but not impossible to deal with.

Chris