Workgroup (access 97)

[Bob]

I am having difficulty using a shortcut to an access
database using a workgroup file. The shortcut is:

"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE"
"\\NT-LEN-FS01\683 Public\Pharmacy WorkOrder
db\SecureWorkOrderRX.mdb" /wrkgrp "\\NT-LEN-FS01\683
Public\Pharmacy WorkOrder db\Workorderworkgroup.mdw"

It will not 'accept' the workgroup and require my logon.
However, when I use the Workgroup Admin tool and join
that .MDW it prompts me as expected. However, after using
the tool to 'join' that .MDW, I then am prompted for an
ID/pswd for any database I use from there-on.

Please advise.

Thank you
Bob

 

[TC]

The shortcut looks ok to me.

When you say: "It will not 'accept' the workgroup and require my logon", do
you mean that it automatically logs you on >successfully< to the secured
database >without< asking for a username/password? If so, then one of two
things must be true:

(1) It >is< using that workgroup file, and that file does not have a
password on the Admin user; or,

(2) It is >not< using that workgroup file - in which case, you have not
secured the database correctly - because a properly secured database will
only work in conjunction with the proper workgroup file.

You should not have used workgroup admin to join the special workgroup file
(except for testing purposes). Use it again, to re-join the >default<
workgroup file (system.mdw, or whatever). Then get the shortcut working
properly.

HTH,
TC

 

[Bob]

Thanks for the reply.

It does not accept the workgroup option because when I
click on a form from the switchboard, I get a pop-up with
the Debug or Exit option. Debug shows that the following:
username = DBEngine.Workspaces(0).username
usergrp = DLookup
("[workgroup]", "Resources", "[usernm] = '" + username
+ "'")

The application is supposed to prompt me for logon as
well, but it does not.

I have re-installed Access on my PC, but that hasn't
changed anything. I belong to my local/defaul workgroup
now.

Any assistance would be appreciated.

Thanks,
Bob
(e-mail address removed)

 

[TC]

Bob, nothing that can happen in the switchboard form, can possibly have any
impact on what workgroup file Access is using, or whether Access will ask
you to log on or not. The sequence of events is as follows.

1. Access selects a workgroup file using the one specified on the startup
shortcut, or the default one that was last selected by the workgroup
administrator program.

2. If the Admin user of that workgroup file has a password, Access prompts
you to enter a valid username and password. Otherwise, Access automatically
logs you in as Admin.

3. Access opens the database and starts the switchboard form.

So, workgroup file selection, & logging-on (if any), are well & truly done &
finished, before you even get to the switchboard form.

If you are getting a popup with the Debug & Exit options, you are probably
getting a runtime error. There will be a number and message describing that
error. What is the number & message? Are you sure that you have shown the
line of code on which it actually happens?

HTH,
TC

Thanks for the reply.

It does not accept the workgroup option because when I
click on a form from the switchboard, I get a pop-up with
the Debug or Exit option. Debug shows that the following:
username = DBEngine.Workspaces(0).username
usergrp = DLookup
("[workgroup]", "Resources", "[usernm] = '" + username
+ "'")

The application is supposed to prompt me for logon as
well, but it does not.

I have re-installed Access on my PC, but that hasn't
changed anything. I belong to my local/defaul workgroup
now.

Any assistance would be appreciated.

Thanks,
Bob
(e-mail address removed)

-----Original Message-----
The shortcut looks ok to me.

When you say: "It will not 'accept' the workgroup and require my logon", do
you mean that it automatically logs you on >successfully< to the secured
database >without< asking for a username/password? If so, then one of two
things must be true:

(1) It >is< using that workgroup file, and that file does not have a
password on the Admin user; or,

(2) It is >not< using that workgroup file - in which case, you have not
secured the database correctly - because a properly secured database will
only work in conjunction with the proper workgroup file.

You should not have used workgroup admin to join the special workgroup file
(except for testing purposes). Use it again, to re-join the >default<
workgroup file (system.mdw, or whatever). Then get the shortcut working
properly.

HTH,
TC





.