|
security
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Access 2003 on wondows XP de-secure problemI have Ms Access 2003 runs on windows XP. I have secured one access database at user level. This one is supposed to be used by multiple users from their computers. The database is located on a network. First time when I tested this worked as expected from my computer, but didn’t work from my boss computer. I thought this is some thing to do with the shortcut for the secured database, since he was trying to open from a different location. The physical location or path name from my computer is different from his (“M:/xyz/anothefolder/ABC.mdb†and “H:/ABC.mdbâ€). Then as stupid as it sounds I have run the user level security again, by selecting the option: I want to make this my default work group applicationâ€. But this didn’t solve the problem; even then my boss couldn’t open the database. I have thought it is complicated to secure an access database which runs on a network. Then I de-secured it by running another user level security with out using a password for admin account. Now I can not open the database. It gives an error message saying “you do not have necessary permissions to open the “C/…… ..mdb†database.†I am able to open the other access databases. It brings the logon window, I click ok; with out giving password, then it opens. But the database which I set up the user level security doesn’t open. If I try to install the access database program again does it fix all the mess I made by securing and de-securing? If not how can I open the database? Thank you very much in advance for any help. Sheela. sheela wrote:
> You'd need to put the secure mdw on the network as well. Then the shortcut > I have Ms Access 2003 runs on windows XP. > > First time when I tested this worked as expected from my computer, but > didn't work from my boss computer. I thought this is some thing to do > with the shortcut for the secured database, since he was trying to > open from a different location. The physical location or path name > from my computer is different from his ("M:/xyz/anothefolder/ABC.mdb" > and "H:/ABC.mdb"). can be changed to reflect the location of the mdw. You can also use UNC pathnames rather than relying on users having the shares mapped to the same letter. eg. "c:\Program Files\Microsoft Office\Office11\msaccess.exe" "\\servername\somefolder\ABC.mdb" "\\servername\somefolder\secure.mdw" That's all on one line in the shortcut target. > Then as stupid as it sounds I have run the user level security again, Did you run the wizard on the original unsecured mdb, or just run it again?> by selecting the option: I want to make this my default work group > application". > But this didn't solve the problem; even then my boss couldn't open the You shouldn't be running the wizard over and over. Check in the folder > database. I have thought it is complicated to secure an access > database which runs on a network. > Then I de-secured it by running another user level security with out > using a password for admin account. Now I can not open the database. > It gives an error message saying "you do not have necessary > permissions to open the "C/.. .mdb" database." where your mdb is located, and see if there is a backup of the unsecure mdb somewhere (it'll have the same name, but a bak extension). Open Access and go to Tools, security, workgroup administrator and click on Join and rejoin the standard system.mdw that ships with Access - perhaps do a search on your computer to find its location. Rename the bak file you found to have a mdb extension and double-click it and see if you can get in. If you can, then this renamed mdb file is your unsecured mdb. You can close Access and delete all the secure mdw files and secure mdb files you created. Don't delete the unsecured mdb file! You're now back to square one. > I am able to open the other access databases. It brings the logon That's because you are joined by default to the wrong mdw file - use the > window, I click ok; with out giving password, then it opens. But the > database which I set up the user level security doesn't open. workgroup administrator to rejoin system.mdw. -- Joan Wild Microsoft Access MVP Joan,
Thanks for your reply. I did the search on my computer and there is no system.mdw file on my computer. The only *.mdw files found were security.mdw files which were created in the same folder where the secured database located. When I ran the security wizard I have saved the work group information files in the same folder. I do not remember deleting any files. Sheela. Show quoteHide quote "Joan Wild" wrote: > sheela wrote: > > > > I have Ms Access 2003 runs on windows XP. > > > > First time when I tested this worked as expected from my computer, but > > didn't work from my boss computer. I thought this is some thing to do > > with the shortcut for the secured database, since he was trying to > > open from a different location. The physical location or path name > > from my computer is different from his ("M:/xyz/anothefolder/ABC.mdb" > > and "H:/ABC.mdb"). > > You'd need to put the secure mdw on the network as well. Then the shortcut > can be changed to reflect the location of the mdw. You can also use UNC > pathnames rather than relying on users having the shares mapped to the same > letter. eg. > "c:\Program Files\Microsoft Office\Office11\msaccess.exe" > "\\servername\somefolder\ABC.mdb" > "\\servername\somefolder\secure.mdw" > That's all on one line in the shortcut target. > > > Then as stupid as it sounds I have run the user level security again, > > by selecting the option: I want to make this my default work group > > application". > > Did you run the wizard on the original unsecured mdb, or just run it again? > > > But this didn't solve the problem; even then my boss couldn't open the > > database. I have thought it is complicated to secure an access > > database which runs on a network. > > Then I de-secured it by running another user level security with out > > using a password for admin account. Now I can not open the database. > > It gives an error message saying "you do not have necessary > > permissions to open the "C/.. .mdb" database." > > You shouldn't be running the wizard over and over. Check in the folder > where your mdb is located, and see if there is a backup of the unsecure mdb > somewhere (it'll have the same name, but a bak extension). Open Access and > go to Tools, security, workgroup administrator and click on Join and rejoin > the standard system.mdw that ships with Access - perhaps do a search on your > computer to find its location. Rename the bak file you found to have a mdb > extension and double-click it and see if you can get in. If you can, then > this renamed mdb file is your unsecured mdb. You can close Access and > delete all the secure mdw files and secure mdb files you created. Don't > delete the unsecured mdb file! You're now back to square one. > > > I am able to open the other access databases. It brings the logon > > window, I click ok; with out giving password, then it opens. But the > > database which I set up the user level security doesn't open. > > That's because you are joined by default to the wrong mdw file - use the > workgroup administrator to rejoin system.mdw. > > > -- > Joan Wild > Microsoft Access MVP > > > "sheela" wrote: There has to be. Access can't run without it. Ensure you also search in > Thanks for your reply. I did the search on my computer and there is no > system.mdw file on my computer. hidden and system folders. > The only *.mdw files found were security.mdw files which were created in the OK, so you need to change your shortcut so that Access uses the security.mdw > same folder where the secured database located. > When I ran the security wizard I have saved the work group information files > in the same folder. I do not remember deleting any files. workgroup file. The target would look like "path to msaccess.exe" "Path to secure mdb" /wrkgrp "path to security.mdw" Change the shortcut on your boss's computer to reflect the correct paths. -- Joan Wild Microsoft Access MVP Joan,
It is working. thank you very much for your help. I had successfully de-secured the DB. and secured it. Before I wasn't saving the MDW files on the network. This time I saved all the files on the network. Didn't have to change any paths in the shortcut propoerties. It worked. Hopefully will work for other users also. I have another question about the *.bak file, will it be updated each time the secured database is changed? thanks again for your help. Sheela Show quoteHide quote "Joan Wild" wrote: > "sheela" wrote: > > > Thanks for your reply. I did the search on my computer and there is no > > system.mdw file on my computer. > > There has to be. Access can't run without it. Ensure you also search in > hidden and system folders. > > > The only *.mdw files found were security.mdw files which were created in the > > same folder where the secured database located. > > When I ran the security wizard I have saved the work group information files > > in the same folder. I do not remember deleting any files. > > OK, so you need to change your shortcut so that Access uses the security.mdw > workgroup file. The target would look like > "path to msaccess.exe" "Path to secure mdb" /wrkgrp "path to security.mdw" > > Change the shortcut on your boss's computer to reflect the correct paths. > > > -- > Joan Wild > Microsoft Access MVP > You're welcome. The bak file will not get updated (nor would you want it
to). It is an unsecured copy of your mdb before you secured it. I suggest you copy it somewhere safe. Note that if you run the security wizard again (not adviseable), it *will* overwrite your existing bak file. But the new bak will not be an unsecured one, in this case. -- Show quoteHide quoteJoan Wild Microsoft Access MVP sheela wrote: > Joan, > > It is working. thank you very much for your help. > I had successfully de-secured the DB. and secured it. Before I wasn't > saving the MDW files on the network. This time I saved all the files > on the network. Didn't have to change any paths in the shortcut > propoerties. It worked. Hopefully will work for other users also. > > I have another question about the *.bak file, will it be updated each > time the secured database is changed? > > thanks again for your help. > Sheela > > > > > "Joan Wild" wrote: > >> "sheela" wrote: >> >>> Thanks for your reply. I did the search on my computer and there is >>> no system.mdw file on my computer. >> >> There has to be. Access can't run without it. Ensure you also >> search in hidden and system folders. >> >>> The only *.mdw files found were security.mdw files which were >>> created in the same folder where the secured database located. >>> When I ran the security wizard I have saved the work group >>> information files in the same folder. I do not remember deleting >>> any files. >> >> OK, so you need to change your shortcut so that Access uses the >> security.mdw workgroup file. The target would look like >> "path to msaccess.exe" "Path to secure mdb" /wrkgrp "path to >> security.mdw" >> >> Change the shortcut on your boss's computer to reflect the correct >> paths. >> >> >> -- >> Joan Wild >> Microsoft Access MVP
More security questions
Getting started with security Frontend Downloads Read only report Encode/Decode Data Base Error 7399 When trying to link an Access database to SqlServer 2K Error 0x80040E4D when tryng to open an password protected Access database programmatically Problem accessing Access from ShortCut. Desperate housewife needs help with user profiles.... seting a predefined workgroup in office 2007??? |
|||||||||||||||||||||||