Location of Workgroup administrator in Office 2002

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi

I having a really strange problem with my access 2002 databse. I have put it
on the network as it needs to be used by many users. I have a workgroup and a
shortcut which is coded to open the database and the workgroup.

When i click on the shortcut i get an error message saying it can't find the
database i have checked all spelling etc.

The strange thing is if i browse to the network folder and double click on
the database itself it opens fine but without the security.

I can't find the workgroup administrator tool to join the workgroup
therefore taking the need for the shortcut away.

I thought the workgroup administrator file would have been in
c\programs\microsoft office\office10\1033 but it doesn't appear to be there.

Can anyone help

Thanks
 
Starting with 2002, the workgroup administrator is no longer a separate
program; it's part of Access - Tools, Security menu.

Your best bet is to get the shortcut working. Post the target and someone
may see the flaw (remember that if there are spaces in the path, you must
enclose it in double-quotes).

You say that you are able to browse to the network folder and open it, with
no login prompt. That means that it isn't secured properly. If done
properly, you shouldn't be able to even open it while using the system.mdw
workgroup file.

You missed a step in securing it.
 
1 Is your network drive mapped to M:?
2 As Joan said, you should not be able to open the file with system.mdw.
 
Hi

Thanks for your reply i have posted the shortcut string below but i am more
inclined to think it is a network problem. I have the same shortcut to test
the databse on my C drive the only difference being the "M" in the shortcut
string are "C".

This shortcut works perfectly and open the database with the security.

"C:\Program Files\Microsoft Office\Office10\MSACCESS.EXE" "M:\OSC Purchase
Orders\Purchase_Orders.mdb" /wrkgrp "M:\OSC Purchase
Orders\Purchase_Orders.mdw

Thanks for your help
 
A couple of comments:

1. You may have problems with both the mdb and mdw having the same name and
in the same folder. They each need to create a ldb file...and with the same
name, that'll be difficult.

2. You shouldn't have multiple users sharing the same mdb. You should split
the mdb and put the backend on the server, and give each user a copy of the
frontend on their computer. When you split it, don't use the splitter
wizard - do it manually see www.jmwild.com/SplitSecure.htm

3. You don't have to use mapped drives. You can use the UNC pathnames
and then not worry if users have the same mapping.

\\server\share\... rather than M:\...

4. Again, you shouldn't be able to open the mdb while using system.mdw

5. All users need read, write, create and delete permissions on the network
folder.
 
Back
Top