Auto Signon and Joining MDW Group

[Jay]

Haven't used Access in a while, so I've I need to provide more information to
get a definitive answer, please let me know and I can post whatever is needed.

I did not write the code for this database, but I do have access to it to
make changes. In short, the original developer created a pseudo
Client-Server architecture where the data exists on a network share
(Data.mdb) and the code exists on the end-user's desktop (code.mdb) - tables
linked to data on server. In this scheme, Access security is turned on
requiring the user to join the workgroup (MDW) file which exists on the same
network share as the data.mdb. Although the application uses access security
to secure the file, the developer used the user's Windows login as the
username (stored in Users Table) to grant specific access to objects via
code.

This causes two usability issues:

1) When a new user first launches the client db, they must first manually
local the MDW file on the network share and Join. End users are not always
savvy with this sort of thing.
2) Because the user's access to forms, etc. is controlled via code in the
User's table, each time the user logs into the database, they are prompted to
enter an Admin password to login. (I believe the default Admin account
doesn't have rights, then he assigns\removes specific rights via code). All
users enter the same default admin password combo.

So, my questions are:

A) Is there any way I can have my InstallShield program add an entry to the
user's Registry so that they are automatically joined when they install the
application - eliminating the need to do this manually? I haven't worked
with Access in some years - so I don't know if adding their Windows login to
the MDW file before hand would help either.
B) Is there a way to supply the username\password to Access from the Start
Menu shortcut so that the user isn't prompted for this, sort of like web
based databases from URLs?


More Setup details
==============
Access 2000 database
Using Access 2003
Access Security turned one with MDW file in same directory as network share

Thanks in advance for your assistance.

 

[Jay]

One other thing regarding the Username\Password shortcut:

I tried something like this:

"C:\CODE.MDB" /USER UserName /PWD Password

but didn't work - I started db but login screen appeared. Teh only way I
was able to get it to work was this:

"C:\Program Files\Microsoft Office\OFFICE11\MSACCess.exe" "C:\CODE.MDB"
/USER Admin /PWD password

The problem with this is not every user has Access instaled in the same
location. Does XP use something similar to PATH in Win98/NT?

 

[TC]

One comment: using workgroup administrator to join the relevant
workgroup file, is not the way to go. As you already know, this
adversely affects all other db's on the user's PC.

Instead, leave each PC joined to the normal, default workgroup file
(system.mdw). Then, start the db via a shortcut of the following form:

"full path to msaccess.exe"
"full path to user's code.mdb"
/wrkgrp "full path to workgroup file"

Your installer could doubtless create suitable shortcuts.

HTH,
TC

 

[david epsom dot com dot au]

We use a small VB program to find MSACCESS.EXE and
start it with the correct command line parameters.

You could do the same in a small mdb if you wanted
to.

If you are good with your install scripts, you can
locate Office Root and use that when you create
your application shortcuts.

The normal registry association for .MDB files is
something like this:
....\msaccess.exe "%1"

%1 is the first command line parameter. since there
is no %2, %3 etc, no other values from your command
line are used: they are just ignored. You can change
this registry entry: better, you can name your files
something other than .MDB, and create your own file
association that takes as many parameters as you want -
or has hardcoded parameters if you want:
....\msaccess.exe "%1% /user fred /pwd fred

To do that, you need to be able to create the appropriate
registry entries.

Another approach is to use the /profile command line
option: this has some other advantages, but in your
situation it would just be a replacement for the /wrkgrp
command line option.

Yes, XP uses PATH like Win98/NT. However, to add the
Office folder to the PATH, you still need to know the
Office folder: it is not in the default PATH: so you
still have the same problem.


More generally, you may wish to reconsider your general
security model. This book explains some alternatives:

Apress: Garry Robinson: Real World Microsoft Access
Database Protection and Security

(david)