Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Started Security wizard and changed workgroup Noone can log on to app
- Thread starter Tomadams
- Start date
FancyPrairie
Programmer
Generally, when one sets up security, a new mdw file is created. Then a shortcut needs to be created to launch the Access database. The properties for the shortcut would look something like this "\\path\msaccess.exe" "\\path\YourDb.mdb" /wrkgrp "\\path\YourWorkgroup.mdw".
However, if that is not how you launch it, then Access uses the System.mdw file by default. I suspect when security was setup, whoever set it up, didn't create a new workgroup. To get around the problem, without fixing it, is to create a shortcut and set its properties like this: "\\path\msaccess.exe" "\\path\YourDb.mdb" /wrkgrp "\\path\System.mdw". Then launch the shortcut. If it works, then that tells me that Access overwrote the System registry so that it points to the new mdw file you created with the wizard rather than pointing to system.mdw.
If the above works and you want to fix the problem so it works like it did before, you need to mess with the System Registry. The system registry should now be pointing to the new workgroup you created. So search the System registry for the name of the new workgroup and change it to system.mdw (or whatever workgroup you were using). To search the system registry, type regedit via the Run command. But be very careful when messing with the registry, you could cause some major problems. I suggest backing up the registry prior to modifying it.
However, if that is not how you launch it, then Access uses the System.mdw file by default. I suspect when security was setup, whoever set it up, didn't create a new workgroup. To get around the problem, without fixing it, is to create a shortcut and set its properties like this: "\\path\msaccess.exe" "\\path\YourDb.mdb" /wrkgrp "\\path\System.mdw". Then launch the shortcut. If it works, then that tells me that Access overwrote the System registry so that it points to the new mdw file you created with the wizard rather than pointing to system.mdw.
If the above works and you want to fix the problem so it works like it did before, you need to mess with the System Registry. The system registry should now be pointing to the new workgroup you created. So search the System registry for the name of the new workgroup and change it to system.mdw (or whatever workgroup you were using). To search the system registry, type regedit via the Run command. But be very careful when messing with the registry, you could cause some major problems. I suggest backing up the registry prior to modifying it.
I am assuming you are not using Access 2007 as I have not read up on whatever they changed in the newest version.
Likely it works on the machine where you ran the wizard.
If so, you can find out what workgroup file you are using by going into the workgroup administrator.
In 2000 + it is Under Tools and Security.
Earlier, you had to run the file separately. wrkgrpadm.exe if memory servers. It was buried under either the office installation path or thw windows root directory.
Using the Workgroup Administrator you can rejoin the default workgoup by hitting the join buton and naviagting to it. I believe moving the target workgoup should have the same effect. However this does not fix the security problem.
Like FancyPrairie posted. you can use a shortcut to specify a workgroup.
To allow anyone to get into it, you need to give admin and preferably the Users group permission to do everything (Tools, Security, User And Group permissions). Note the option group for users and groups. Users is a group and admin is a user. These are common to every workgroup file. So giving them permission is like giving permission to anyone who uses the default workgroup.
Finally, if you want to strip the extra security out of the database, you can create a new file logged into the default workgroup and import everything into the file (admin or users needs at least Read Design and Read Data permission where appropriate).
Likely it works on the machine where you ran the wizard.
If so, you can find out what workgroup file you are using by going into the workgroup administrator.
In 2000 + it is Under Tools and Security.
Earlier, you had to run the file separately. wrkgrpadm.exe if memory servers. It was buried under either the office installation path or thw windows root directory.
Using the Workgroup Administrator you can rejoin the default workgoup by hitting the join buton and naviagting to it. I believe moving the target workgoup should have the same effect. However this does not fix the security problem.
Like FancyPrairie posted. you can use a shortcut to specify a workgroup.
To allow anyone to get into it, you need to give admin and preferably the Users group permission to do everything (Tools, Security, User And Group permissions). Note the option group for users and groups. Users is a group and admin is a user. These are common to every workgroup file. So giving them permission is like giving permission to anyone who uses the default workgroup.
Finally, if you want to strip the extra security out of the database, you can create a new file logged into the default workgroup and import everything into the file (admin or users needs at least Read Design and Read Data permission where appropriate).
- Status
Similar threads
- Locked
- Question
