We use Workgroup files for on centralized DB within our department. Is it
possible to not require a user to login when opening files? The login screen
appears to be causing some of his macros to malfunction.

If not are there options in contruction the macro to bypass the login when
opening a mdb?

The login is based on the mdw file the user is joined to.

Your users should all be joined to the default SYSTEM.MDW which does not
require a login.

For any secured files, you should create a shortcut that includes the
database file and the workgroup to use.

If you will do a search, you will find many previous posts on this topic.

--
Rick B



"Homestar95" <(E-Mail Removed)> wrote in message
news:ED3E717E-6FCA-4B73-86A4-(E-Mail Removed)...
> We use Workgroup files for on centralized DB within our department. Is it
> possible to not require a user to login when opening files? The login
screen
> appears to be causing some of his macros to malfunction.
>
> If not are there options in contruction the macro to bypass the login when
> opening a mdb?

Homestar95 wrote:
> We use Workgroup files for on centralized DB within our department.
> Is it possible to not require a user to login when opening files? The
> login screen appears to be causing some of his macros to malfunction.
>
> If not are there options in contruction the macro to bypass the login
> when opening a mdb?

Your users should have a custom shortcut that specifies the "secured"
workgroup so it is only used for the specific files that require it and then
their default workgroup can be set back to the default "System.mdw" which
will not prompt them. The secured file's shortcut Target will be
constructed roughly like...

"Full path toMSAccess.exe" /wrkgrp "Full path the MDW" "Full Path to MDB"

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

How are the macros "malfunctioning", and what makes you think that this
is something to do with the login screen?

TC