Hi,

I have a problem in getting Access 2002 to read my workgroup file.
I've created different groups and users and when the db is opened the
user is prompted to enter a username and password which seems to be
working perfectly on my PC.

However, when someone else on a different computer opens this db on
the shared network the user is no longer asked to enter their username
and password and they are logged on as the default admin user.

I've looked at the workgroup adminstrator and the db is joined with
the correct workgroup. I've also looked at the whitepaper Microsoft
Access Security FAQ and tried the solution in point 40, but still no
success.

Can anyone out there help me please?

Many thanks,
Dom

"Dom" <dominic.marmion@which.co.uk> wrote in message
news:dae8cd33.0405280828.383c9c04@posting.google.c om...[color=blue]
> Hi,
>
> I have a problem in getting Access 2002 to read my workgroup file.
> I've created different groups and users and when the db is opened the
> user is prompted to enter a username and password which seems to be
> working perfectly on my PC.
>
> However, when someone else on a different computer opens this db on
> the shared network the user is no longer asked to enter their username
> and password and they are logged on as the default admin user.
>
> I've looked at the workgroup adminstrator and the db is joined with
> the correct workgroup. I've also looked at the whitepaper Microsoft
> Access Security FAQ and tried the solution in point 40, but still no
> success.
>
> Can anyone out there help me please?[/color]

You have a fundamental misunderstanding of how Access security works.

*Files* are not joined to workgroups *Users* are.

When Access is launched it will use the workgroup file specified as a
command line argument and if no such argument is supplied it will use the
default workgroup file for the current user as defined on his local PC.
This all happens before your file is even opened which is why your file
cannot possibly specify which workgroup to use.

You either have to have users "join" your workgroup file to make it their
default (not recommended) or supply them with a shortcut to your app that
specifies your workgroup file as a command line argument (recommended).
The shortcut would look something like...

"Full path to MSAccess.exe" /wrkgrp "Full path to MDW file" "Full path to
MDB file"

Here's the important bit. Having failed to do one of the above, your users
should not have been able to open the file at all. When properly secured,
a file can only be opened with the appropriate workgroup file. This
indicates that you missed a step in setting up security. You have to
correct that problem BEFORE you give users a proper shortcut or your
security efforts will have been a complete waste of time.


--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com