rogle
asked on
Access Requires Password to Open- need to disable that feature
Whenever I try to create a new access database on a particular user's workstation, it prompts for a username and password. I also get prompted when I attempt to open any existing access database as well. I need to disable this password feature altogether.
I have ran a couple of the password unlock apps on some existing databases. They all say that the database is not password protected.
From back in the day, I vaguely remember something about a "system.md?" file that controls overall permissions to access. I found a system.mdw and renamed it, but that didn't get me anywhere.
I am the new I.T. person for our company. Until I came along support was outsourced. The user who is on the workstation has apparently had this issue for almost a year, but the contracted support never would help her.
I figure this is something straight forward, but I can't seem to figure it out.
I have ran a couple of the password unlock apps on some existing databases. They all say that the database is not password protected.
From back in the day, I vaguely remember something about a "system.md?" file that controls overall permissions to access. I found a system.mdw and renamed it, but that didn't get me anywhere.
I am the new I.T. person for our company. Until I came along support was outsourced. The user who is on the workstation has apparently had this issue for almost a year, but the contracted support never would help her.
I figure this is something straight forward, but I can't seem to figure it out.
Last Comment
ASKER
When attempting to create a new database, I dropped to a command line and started access by changing to c:\csisql\ then running access.exe with no switches.
I also used windows search to search for any file named 'system*'. I only found one system.mdw and NO system.mde nor a system.mda.
I also used windows search to search for any file named 'system*'. I only found one system.mdw and NO system.mde nor a system.mda.
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
ok...mystery solved.
Apparently the user had components of access 97 on the machine for an industry specific software. THEN when the user used Word 2003 to creat a mailing list it created it in an access database.
So...the industry specific software put the password on...AND...access 97 couldn't open the new db format.
Ultimately I was able to get from the user that all she wanted was an address list. So, I showed her how to get that via the Word wizard.
Apparently the user had components of access 97 on the machine for an industry specific software. THEN when the user used Word 2003 to creat a mailing list it created it in an access database.
So...the industry specific software put the password on...AND...access 97 couldn't open the new db format.
Ultimately I was able to get from the user that all she wanted was an address list. So, I showed her how to get that via the Word wizard.
What do you mean by "put the password on"? The only way this could have happened - assuming we're talking about the standard Access login prompt - was if (a) the workstation was joined to a non-standard workgroup file or (b) the Admin user in the default workgroup file (system.mdw) had a non-blank password. I don't see how showing that user how to build a list in Word would remove the prompts.
ASKER
Sorry for the confusion. Let me retry...
1) The user built some address lists using Word 2003. When word does this, it stores those addresses in an mdb file. Since she was using Word 2003, the mdb files were in a format newer than access 97. The default location for those files was a subdirectory off of her My Documents folder. When she tried to open them, she wsa prompted for a password.
2) After doing a search the only access executable I could find was an access 97 exe.
3) Within the same directory as the access exe was a file named something like "wrkadm.exe" in the same directory. When I ran this exe, I was able to join a different workgroup file (system.mdw)
4) After joining the new workgroup, access no longer prompted for a password when attempting to open the mdb' containing the addresses- it said it was in an invalid format. Again, my assumption at this point was that Word 2003 had created them in a format which access 97 did not recognize.
5) I ran the workgroup admin util and rejoined the user to the other .mdw file where they were joined before I started.
6) As I explained to the user about how we'd need to get her a newer version of access to put on the macine, she huffed and "But all I need are the addresses from my files!"
7) I searched Word Help for creating an address list from a saved list already created in word. As luck would have it, there was a wizard the user could run that allowed her to pull the information out and print them for her boss.
...make more sense?
1) The user built some address lists using Word 2003. When word does this, it stores those addresses in an mdb file. Since she was using Word 2003, the mdb files were in a format newer than access 97. The default location for those files was a subdirectory off of her My Documents folder. When she tried to open them, she wsa prompted for a password.
2) After doing a search the only access executable I could find was an access 97 exe.
3) Within the same directory as the access exe was a file named something like "wrkadm.exe" in the same directory. When I ran this exe, I was able to join a different workgroup file (system.mdw)
4) After joining the new workgroup, access no longer prompted for a password when attempting to open the mdb' containing the addresses- it said it was in an invalid format. Again, my assumption at this point was that Word 2003 had created them in a format which access 97 did not recognize.
5) I ran the workgroup admin util and rejoined the user to the other .mdw file where they were joined before I started.
6) As I explained to the user about how we'd need to get her a newer version of access to put on the macine, she huffed and "But all I need are the addresses from my files!"
7) I searched Word Help for creating an address list from a saved list already created in word. As luck would have it, there was a wizard the user could run that allowed her to pull the information out and print them for her boss.
...make more sense?
<When I ran this exe, I was able to join a different workgroup file (system.mdw) After joining the new workgroup, access no longer prompted for a password when attempting to open the mdb' containing the addresses>
Right ... which is what I suggested you do in my comment:
On that workstation, you need to locate the "system.mdw" file (there may be more than one, if so then use the one you find in Windows/System or Common Files). You then need to join that workgroup file.
THIS is what causes the username/password prompt. The secondary issue of whether the user was able to create a Word List was not relevant to the post (it's relevant to you, of course, but doesn't change the fact that you were given instructions as to how to eliminate the username/password prompt.
Quite simply, it's impossible for us to know the entire structure/environment of your enduser machines. We give specific advice on solving a specific issue.
Right ... which is what I suggested you do in my comment:
On that workstation, you need to locate the "system.mdw" file (there may be more than one, if so then use the one you find in Windows/System or Common Files). You then need to join that workgroup file.
THIS is what causes the username/password prompt. The secondary issue of whether the user was able to create a Word List was not relevant to the post (it's relevant to you, of course, but doesn't change the fact that you were given instructions as to how to eliminate the username/password prompt.
Quite simply, it's impossible for us to know the entire structure/environment of your enduser machines. We give specific advice on solving a specific issue.
ASKER
LSConsulting,
As it is difficult to get "tone of voice" from posts, please let me say that I appreciate the suggestions that both you and the others gave. My intent was _not_ to degrade anyone's suggestions.
I hope you have a wonderful day.
As it is difficult to get "tone of voice" from posts, please let me say that I appreciate the suggestions that both you and the others gave. My intent was _not_ to degrade anyone's suggestions.
I hope you have a wonderful day.
ASKER
Vee_Mod,
Thank you for your direction.
I do not have an option to "Object", could it be because I'm the poster?
I apologize for the misunderstanding. At the time I started the closing process, there were no objections.
LSMConsulting,
Have I responded to your comments adequately enough so that I may start the closing process?
Thank you for your direction.
I do not have an option to "Object", could it be because I'm the poster?
I apologize for the misunderstanding. At the time I started the closing process, there were no objections.
LSMConsulting,
Have I responded to your comments adequately enough so that I may start the closing process?
I object to the PAQ-Refund, as my and Scott's comments directly answer the question (especially Scott's at 22080111), which the asker confirmed in great detail at 22110450.
I second what Jim said - the poster's original question was answered correctly. The poster's question made no mention of Word or address lists until such time as they posted their "mystery solved" post.
Microsoft Access
Microsoft Access is a rapid application development (RAD) relational database tool. Access can be used for both desktop and web-based applications, and uses VBA (Visual Basic for Applications) as its coding language.
226K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
System.mdw
Create a shortcut to open your Access app, the do a right-click:Properties, and copy-paste the contents of the Target textbox into this question.
Since a previous app that was run on that pc was secured, you'll need to point this new app back to the unsecured system.mdw by adding a /wrkgrp {path-file of your system.mdw file} to the end.
Access command-line switches
http://www.vb123.com/workbench/help/commandline.htm