User Workgroup in Access 2000

[Guest_imported]

<br>&nbsp;&nbsp;I have a multi-user database, which I recently upgraded from Office 97 to Office 2000. I created a new workgroup on our network, and assigned various users and groups. However, when I join that workgroup from a differant computer, it is though it is a brand new workgroup, with none of the users or groups. In other words regardless of what I do to the database users and security, it seems to not affect the main system.mdw file which is supposed to hold that information. Can anyone tell me what I am doing wrong, or not doing right? Thanks <p>John Vogel<br><a href=mailto:johnvogel@computerwiz.net>johnvogel@computerwiz.net</a><br><a href=

http://johnvogel.homepage.com>My

Home Page</a><br>Jesus is the Way, the Truth, and the Life:<br>
Without the Way there is no going;<br>
Without the Truth there is no knowing;<br>
Without the Life there is no living. —Anon.

 

[elizabeth]

1. Were you joined to the correct .mdw when you make the changes to security?<br>2. Were you entering the correct .mdb before making the changes?<br>3. Were you joined to the correct workgroup and in the correct .mdb when you use the other machines?<br>

 

[elizabeth]

4. Were you using the Access97 or Access 2000 wrkgadm.exe?<br><br>Access 2000 defaults to a different file than Access 97, although you can continue to use the Access 97 one if you convert. This has worked fine for me in upgrading multiple dbs from 97 to 2000.

 

[Guest_imported]

Elizabeth,<br><br>&nbsp;&nbsp;Well, actually, I tried using Access97 AND 2000 wrkgadm programs. <br>I am using a workgroup file on our main server. I created the workgroup file, and then I joined the workgroup. <br>I opened my Access2000 Table and I went on to create the users, and everything worked fine. <br>When I join the same workgroup from a differant machine, it shows no users or groups. It is as though it is using a new workgroup?! I checked securities and all, everything seems fine in that area. I am totally perplexed.<br> <p>John Vogel<br><a href=mailto:johnvogel@computerwiz.net>johnvogel@computerwiz.net</a><br><a href=

http://johnvogel.homepage.com>My

Home Page</a><br>Jesus is the Way, the Truth, and the Life:<br>
Without the Way there is no going;<br>
Without the Truth there is no knowing;<br>
Without the Life there is no living. —Anon.

 

[elizabeth]

Well you probably would not do this foolish thing that I occassionally do; I've applied security to a back end and then looked for them from the front end.<br><br>If that's not it either, you might try renaming the security file on the server and see if you can open the db from both places. Especially if you left your file named system.mdb as it's best to give it a custom name & password.