By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,863 Members | 879 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,863 IT Pros & Developers. It's quick & easy.

Workgroup specification dilemma

P: n/a
Thank you for reading...

I have developed two separate dbases using Access 2002. Each has
their own workgroup specifications. On each users desktop I created a
shortcut to the front end dbase and with the appropriate workgroup:

Path of shortcut is:
"locationofMSACCESS.EXE" "locationoffrontend.mdb" /wrkgrp
"locationofworkgroup.mdw"

The problem is that my databases are sharing the same workgroup on my
machine. When I look up the workgroup identification through Tools >
Security > Workgroup Admin it shows that the workgroup file is that of
the other. If I click "Join" and select the appropriate workgroup
file it will automatically set that workgroup for the other database.
This is causing a lot of problems...

Thank you in advance for your time.

Regards
Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
On 20 Oct 2003 08:10:19 -0700, aw***@umich.edu (Daniel) wrote:
Thank you for reading...

I have developed two separate dbases using Access 2002. Each has
their own workgroup specifications. On each users desktop I created a
shortcut to the front end dbase and with the appropriate workgroup:

Path of shortcut is:
"locationofMSACCESS.EXE" "locationoffrontend.mdb" /wrkgrp
"locationofworkgroup.mdw"

The problem is that my databases are sharing the same workgroup on my
machine. When I look up the workgroup identification through Tools >
Security > Workgroup Admin it shows that the workgroup file is that of
the other. If I click "Join" and select the appropriate workgroup
file it will automatically set that workgroup for the other database.
This is causing a lot of problems...

Thank you in advance for your time.

Create the same shortcuts on your desktop that you made for your users, and
use those shorotcuts to open the respective databases when you work on
them.
Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.