|
security
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
More security questions(Access 2003). I finally decided to use Joan Wild's step-by-step instructions to implement security, then I read Jack MacDonald's paper to learn more about what I had just done. I may be ready to look through the MS FAQ again. It seems to have worked in my limited test, but I have a few questions. 1) From what I can tell, when I go to User and Group permissions and view group permissions, one of the items that can be checked is "Administer". I expect this is to administer user accounts, assign ownership if needed, clear passwords, and all that sort of thing. Is that correct? 2) I have created a number of test users, all of whom have the same password and the default PID (that 20-character string of letters and numbers). The idea is that I will create shortcuts for individual users so that clicking on the shortcut fills in that person's user ID. To do that I am using this as the target in the shortcut: "path to msaccess.exe" "path to the mdb file" /user UserName /wrkgrp "path to secure mdw file" I realize that a separate shortcut for each user is an administrative hassle on the one hand, but there are some advantages such as the username always being correct on that user's computer. The number of users is small enough that it should work OK. I can change the strategy if need be. Anyhow, my question is about a strategy for deploying the shortcuts, and specifically about forcing the users to choose a password. 3) In a related question, I know that I can clear a user password if it is forgotten, but then the shortcut above opens the database without any security at all. Again, how can I force the user to select a password? 4) In a split database, I'm still trying to sort out when I assign permissions. Do I assign permissions to objects, then split the database, or do I assign permissions for tables in the back end and other objects in the front end, or what? I'm still having trouble getting a conceptual handle on this aspect of security. 5) I would like to have the username appear in records at times. Are spaces in the user name OK, or is it like spaces in field names, which can create extra work down the road? 6) If I assign permissions to groups, but there is one user with a unique set of permissions, can I assign permissions to that user independent of the group? Even if it is possible, is it advisable, or should I create a custom group for that one user? 7) Why would I as the developer want to change ownership of database objects? It is possible, I know, but I can't quite imagine why unless maybe on a large project with several developers. BruceM wrote:
> Modify permissions on that object. A person needs to be a member of the > 1) From what I can tell, when I go to User and Group permissions and > view group permissions, one of the items that can be checked is > "Administer". I expect this is to administer user accounts, assign > ownership if needed, clear passwords, and all that sort of thing. Is > that correct? Admins Gruop in order to administer user accounts, clear passwords. Also it's the owner who can change ownership (as well as the owner of the database object) > 2) I have created a number of test users, all of whom have the same There is no 'default' PID; also I don't understand why you'd give everyone > password and the default PID (that 20-character string of letters and > numbers). the same password. > The idea is that I will create shortcuts for individual OK, you can do that. However without the /user switch, Access will > users so that clicking on the shortcut fills in that person's user > ID. To do that I am using this as the target in the shortcut: > "path to msaccess.exe" "path to the mdb file" /user UserName /wrkgrp > "path to secure mdw file" automatically fill in the last Access username that opened a secure mdb on that computer. It's only the first time that it'll use the user's Windows login name. So I'm not sure there is any advantage to doing this. > Anyhow, my question is about a strategy for I would deploy without a password set. You can check that the password > deploying the shortcuts, and specifically about forcing the users to > choose a password. isn't blank; if it is, then give them a form to set their password. Also you can then send everyone the same shortcut (assuming they have installed Access to the same folder, and installed the frontend to the same location). > One can do it either way.> 4) In a split database, I'm still trying to sort out when I assign > permissions. Do I assign permissions to objects, then split the > database, or do I assign permissions for tables in the back end and > other objects in the front end, or what? I'm still having trouble > getting a conceptual handle on this aspect of security. 1. - split first - just be sure you use the same secure mdw to secure both the FE and BE 2. - secure first - be sure you don't use the splitter wizard as that will result in an unsecure BE. There's a page on my site explaining how to split manually (which is very easy to do). I generally give only Open Permission on the BE database object. All data interaction is done via RWOP queries; users then don't need any permission on the backend tables. > 5) I would like to have the username appear in records at times. Are In this case you can use CurrentUser() function to retrieve the Access > spaces in the user name OK, or is it like spaces in field names, > which can create extra work down the road? username. Since this is data (as opposed to a field name), spaces are just fine > 6) If I assign permissions to groups, but there is one user with a You can. I always use groups; as soon as you think there is only one user > unique set of permissions, can I assign permissions to that user > independent of the group? Even if it is possible, is it advisable, > or should I create a custom group for that one user? in a group, you'll find another user that needs to be a member. > 7) Why would I as the developer want to change ownership of database The main thing is that neither the Users Group, nor the Admin User own > objects? It is possible, I know, but I can't quite imagine why > unless maybe on a large project with several developers. anything. These two entities are common to every mdw. So if either owns something, then anyone with Access (i.e. they'd be using system.mdw) could, as owner, do anything with the object. -- Joan Wild Microsoft Access MVP
Show quote
Hide quote
"Joan Wild" <jwild@nospamtyenet.com> wrote in message When I create a user the PID is filled in with a 20-character string. I news:OHLy45zEHHA.4464@TK2MSFTNGP06.phx.gbl... > BruceM wrote: >> >> 1) From what I can tell, when I go to User and Group permissions and >> view group permissions, one of the items that can be checked is >> "Administer". I expect this is to administer user accounts, assign >> ownership if needed, clear passwords, and all that sort of thing. Is >> that correct? > > Modify permissions on that object. A person needs to be a member of the > Admins Gruop in order to administer user accounts, clear passwords. Also > it's the owner who can change ownership (as well as the owner of the > database object) > >> 2) I have created a number of test users, all of whom have the same >> password and the default PID (that 20-character string of letters and >> numbers). > > There is no 'default' PID; also I don't understand why you'd give everyone > the same password. called it the default PID, but "automatically generated" would probably have been more accurate. Regarding the password, I was testing security by "pretending" to be different users with different permissions. To do that I used the same password just so it would be easy to remember for the testing. I'm ot sure why I bothered to add the detail about the password, as it could only have muddied the waters. Is there any value to using something other than the automatically generated PID? > I once attempted to deploy a front end by e-mail, but could neither send the >> The idea is that I will create shortcuts for individual >> users so that clicking on the shortcut fills in that person's user >> ID. To do that I am using this as the target in the shortcut: >> "path to msaccess.exe" "path to the mdb file" /user UserName /wrkgrp >> "path to secure mdw file" > > OK, you can do that. However without the /user switch, Access will > automatically fill in the last Access username that opened a secure mdb on > that computer. It's only the first time that it'll use the user's Windows > login name. So I'm not sure there is any advantage to doing this. front end or link to it because of security settings in Microsoft Exchange. I renamed it as a text file, and send it in an e-mail that started with (in all caps) "Do not try to open the file from the e-mail", followed by instructions for saving and renaming the file. Sure enough, I got calls saying "When I tried to open the file I just got a lot of gibberish." There are a number of people here who are very good at their jobs, but struggle with things like this. The trouble is that a number of computers are shared. On those computers there may need to be a user-specific shortcut. Without it people would double click the shortcut, add their passwords (regardless of the user name), and then complain that the database doesn't work. It will not occur to them to check the user name. > Perhaps I can start with the same shortcut for everybody, then modify it as >> Anyhow, my question is about a strategy for >> deploying the shortcuts, and specifically about forcing the users to >> choose a password. > > I would deploy without a password set. You can check that the password > isn't blank; if it is, then give them a form to set their password. Also > you can then send everyone the same shortcut (assuming they have installed > Access to the same folder, and installed the frontend to the same > location). > the circumstances demand. For a single-user computer there shouldn't be a problem. My main question regarding user passwords is how to get a user to enter a password. The only way I can find is to log on as the user, then navigate to User and Group Accounts by way of the menu (or I suppose I could have an icon). Also, I would need either to rely on the user to navigate to the appropriate dialog box, or I would need to go to each workstation, navigate to the password dialog, and leave the user to enter a password. You say that I can check that the password isn't blank, but the only way I can figure out how to do that is to log on as that user. Is there another way of doing that? Regarding giving the user a form, I'm not sure what you mean by that. Are you talking about having them tell me the password so that I can enter it for them, or are you talking about an Access form, or something else? I'm sorry if I'm being dense about this, but I just don't get how to do this. A person's signature on a document is unique unless somebody is skilled at forgery. I am looking for a way to simulate that assurance of uniqueness in Access. As the Administrator I can clear a user's password and log in as that user. Since I will also be using the database, it may be necessary to set up an administrator who can only administer accounts, but not work directly with data. When my e-mail account and network logon were implemented there was a dialog box asking for the password. Without completing the information I could never have logged in. I get a similar sort of thing from time to time when I need to change the password. Is there a way of producing the "You can't go any further without a password" dialog in Access, or must it be a manual, station-by-station process? Show quoteHide quote >> I will try again to comprehend the MS FAQ. I must say it is really too bad >> 4) In a split database, I'm still trying to sort out when I assign >> permissions. Do I assign permissions to objects, then split the >> database, or do I assign permissions for tables in the back end and >> other objects in the front end, or what? I'm still having trouble >> getting a conceptual handle on this aspect of security. > > One can do it either way. > 1. - split first - just be sure you use the same secure mdw to secure both > the FE and BE > 2. - secure first - be sure you don't use the splitter wizard as that will > result in an unsecure BE. There's a page on my site explaining how to > split manually (which is very easy to do). > > I generally give only Open Permission on the BE database object. All data > interaction is done via RWOP queries; users then don't need any permission > on the backend tables. that such important information has not been updated in over six years. I'm not sure how much to believe (for instance, it is among the very few documents I have read that mention without any caveats using a database password), but in any case there is a discussion of RWOP queries which should be of value now that I know a little more about how the security works. Show quoteHide quote > I have already banished the Admin user to the Users group, and removed all >> 5) I would like to have the username appear in records at times. Are >> spaces in the user name OK, or is it like spaces in field names, >> which can create extra work down the road? > > In this case you can use CurrentUser() function to retrieve the Access > username. Since this is data (as opposed to a field name), spaces are > just fine > >> 6) If I assign permissions to groups, but there is one user with a >> unique set of permissions, can I assign permissions to that user >> independent of the group? Even if it is possible, is it advisable, >> or should I create a custom group for that one user? > > You can. I always use groups; as soon as you think there is only one user > in a group, you'll find another user that needs to be a member. > >> 7) Why would I as the developer want to change ownership of database >> objects? It is possible, I know, but I can't quite imagine why >> unless maybe on a large project with several developers. > > The main thing is that neither the Users Group, nor the Admin User own > anything. These two entities are common to every mdw. So if either owns > something, then anyone with Access (i.e. they'd be using system.mdw) > could, as owner, do anything with the object. permissions from the Users group, thanks in large part to your instructions and reinforced by other things I have read (Jack MacDonald's paper in particular). I really appreciate all of your help with this. I could not have done it using only Microsoft's documentation. Show quoteHide quote > > -- > Joan Wild > Microsoft Access MVP > BruceM wrote:
> "Joan Wild" <jwild@nospamtyenet.com> wrote in message No that's fine. I didn't realize you were using the wizard. If you want to > news:OHLy45zEHHA.4464@TK2MSFTNGP06.phx.gbl... >> >> There is no 'default' PID; also I don't understand why you'd give >> everyone the same password. > > Is there any value to using something other than the automatically > generated PID? add users later, you'd do so via Tools, security, accounts, and there you have to come up with your own PID. > The trouble is that a number of computers are shared. On those I would use /user "" in the shortcut instead - that'll pop up the login with > computers there may need to be a user-specific shortcut. Without it > people would double click the shortcut, add their passwords > (regardless of the user name), and then complain that the database > doesn't work. It will not occur to them to check the user name. no username filled in and force them to enter one - then you only need a single shortcut for all. > You say that I can check that the password isn't blank, but the only I'm talking about using an Access form to change passwords, and using code > way I can figure out how to do that is to log on as that user. Is > there another way of doing that? Regarding giving the user a form, > I'm not sure what you mean by that. Are you talking about having > them tell me the password so that I can enter it for them, or are you > talking about an Access form, or something else? to determine if their password is blank. You'd create an unbound form with three textboxes and a command button. The three textboxes are for the user to enter their username (or have it default to CurrentUser()), their old password, and their new password (maybe even another textbox to confirm the new password). There is sample code in the security FAQ for how to change a password. As for checking if it's blank, you can do this in on startup (in your main form, or have a hidden form that opens at startup and checks this. You could attempt to open a DAO workspace in code using the CurrentUser() for the username, and a blank password. If the password is wrong (i.e. they have a password set), you can trap the error. If you get no error then you'll know it is blank, and can throw up a nice message, and then open your change password form. Dim ws as Workspace Set ws = DBEngine.CreateWorkspace("tempws", CurrentUser(),"") If Err=0 then 'they have a blank password 'open a change password form DoCmd.OpenForm "frmChangePassword" Else 'they don't have a blank password 'do nothing End If > Since I will also be That is also covered in the security FAQ. You'd need to create a second mdw > using the database, it may be necessary to set up an administrator > who can only administer accounts, but not work directly with data. for production, while keeping your first secure mdw for development. Look in the FAQ. > I've also got some info at www.jmwild.com/RWOP.htm> I will try again to comprehend the MS FAQ. I must say it is really > too bad that such important information has not been updated in over > six years. I'm not sure how much to believe (for instance, it is > among the very few documents I have read that mention without any > caveats using a database password), but in any case there is a > discussion of RWOP queries which should be of value now that I know a > little more about how the security works. >> The main thing is that neither the Users Group, nor the Admin User That may not be sufficient. If you used the wizard in 2002 or 2003, then >> own anything. These two entities are common to every mdw. So if >> either owns something, then anyone with Access (i.e. they'd be using >> system.mdw) could, as owner, do anything with the object. > > I have already banished the Admin user to the Users group, and > removed all permissions from the Users group, thanks in large part to > your instructions and reinforced by other things I have read (Jack > MacDonald's paper in particular). you're likely OK. However just double-check that Admin is not the owner of the Database Object (or any other object either). Even without any permissions, the 'owner' trumps all. The owner can always take over. -- Joan Wild Microsoft Access MVP
Show quote
Hide quote
"Joan Wild" <jwild@nospamtyenet.com> wrote in message Cool!news:u87aXd8EHHA.3616@TK2MSFTNGP06.phx.gbl... > BruceM wrote: >> "Joan Wild" <jwild@nospamtyenet.com> wrote in message >> news:OHLy45zEHHA.4464@TK2MSFTNGP06.phx.gbl... >>> >>> There is no 'default' PID; also I don't understand why you'd give >>> everyone the same password. >> >> Is there any value to using something other than the automatically >> generated PID? > > No that's fine. I didn't realize you were using the wizard. If you want > to add users later, you'd do so via Tools, security, accounts, and there > you have to come up with your own PID. > >> The trouble is that a number of computers are shared. On those >> computers there may need to be a user-specific shortcut. Without it >> people would double click the shortcut, add their passwords >> (regardless of the user name), and then complain that the database >> doesn't work. It will not occur to them to check the user name. > > I would use /user "" in the shortcut instead - that'll pop up the login > with no username filled in and force them to enter one - then you only > need a single shortcut for all. Show quoteHide quote > Thanks for pointing that out. I think I found it in the part about clearing >> You say that I can check that the password isn't blank, but the only >> way I can figure out how to do that is to log on as that user. Is >> there another way of doing that? Regarding giving the user a form, >> I'm not sure what you mean by that. Are you talking about having >> them tell me the password so that I can enter it for them, or are you >> talking about an Access form, or something else? > > I'm talking about using an Access form to change passwords, and using code > to determine if their password is blank. > > You'd create an unbound form with three textboxes and a command button. > The three textboxes are for the user to enter their username (or have it > default to CurrentUser()), their old password, and their new password > (maybe even another textbox to confirm the new password). There is sample > code in the security FAQ for how to change a password. the password. Show quoteHide quote > Thanks for providing the code example and the sketch of the form I would > As for checking if it's blank, you can do this in on startup (in your main > form, or have a hidden form that opens at startup and checks this. You > could attempt to open a DAO workspace in code using the CurrentUser() for > the username, and a blank password. > > If the password is wrong (i.e. they have a password set), you can trap the > error. > > If you get no error then you'll know it is blank, and can throw up a nice > message, and then open your change password form. > > Dim ws as Workspace > Set ws = DBEngine.CreateWorkspace("tempws", CurrentUser(),"") > If Err=0 then > 'they have a blank password > 'open a change password form > DoCmd.OpenForm "frmChangePassword" > Else > 'they don't have a blank password > 'do nothing > End If use. Again, more study is needed, but I think I can figure it out. A lot of new information has been added to my brain in the past few days, and it's taking a while to incorporate it all. > I saw something about that in Jack MacDonald's article as well. I'll need >> Since I will also be >> using the database, it may be necessary to set up an administrator >> who can only administer accounts, but not work directly with data. > > That is also covered in the security FAQ. You'd need to create a second > mdw for production, while keeping your first secure mdw for development. > Look in the FAQ. to study that some more. I think I understand that only members of the Admins group may manage user accounts. Permissions are stored in the database (mdb) file, so when Workgroup File 1 has the same user and group information as Workgroup File 2, the database will "think" that it is the same group of users, and all permissions will continue to apply. The difference is that Workgroup File 2 does not have I still need to mull this over for a while, but as I will be administering security at first (for databases in which security is not that big an issue) I don't need to worry about it right away. By the way, creating duplicate users and groups seems like a good reason not to use the PIDs generated by the wizard. >> Thanks for that link, and for the referring me back to the FAQ. One of the >> I will try again to comprehend the MS FAQ. I must say it is really >> too bad that such important information has not been updated in over >> six years. I'm not sure how much to believe (for instance, it is >> among the very few documents I have read that mention without any >> caveats using a database password), but in any case there is a >> discussion of RWOP queries which should be of value now that I know a >> little more about how the security works. > > I've also got some info at www.jmwild.com/RWOP.htm problems with the FAQ is that there are parts I clearly can skip (about Access 2.0, for instance), but sometimes I skip too far. This is another concept I expect I will understand in time. My early grasp of it is that for somebody to create a query they need permission to the underlying tables. A RWOP query can let users sort of borrow those table permissions from the query owner without actually needing permission to the tables. One thing I'm still trying to sort out has to do with permissions. As I understand it, a user who is a member of two groups will have the least restrictive permissions. If one group can add data only, and another can add or edit but not delete data, the user will be able to add and edit data. What I can't quite sort out is whether this "least restrictive" rule applies to users as well. In the example just given, if the user is given permission to delete data, but that permission is not allowed any group of with that user is a member, will the user be able to delete data anyhow? I think so, because the least restrictive permission, whether it is a user permission or a group permission, "wins". Users don't need any permissions at all as long as they belong to groups that have permissions. Do I understand correctly? Show quoteHide quote > Admin owns nothing.>>> The main thing is that neither the Users Group, nor the Admin User >>> own anything. These two entities are common to every mdw. So if >>> either owns something, then anyone with Access (i.e. they'd be using >>> system.mdw) could, as owner, do anything with the object. >> >> I have already banished the Admin user to the Users group, and >> removed all permissions from the Users group, thanks in large part to >> your instructions and reinforced by other things I have read (Jack >> MacDonald's paper in particular). > > That may not be sufficient. If you used the wizard in 2002 or 2003, then > you're likely OK. However just double-check that Admin is not the owner > of the Database Object (or any other object either). Even without any > permissions, the 'owner' trumps all. The owner can always take over. Joan, thanks again for all of your help. I don't think I could have done gotten this far, at least not anywhere near this quickly, without it. If you have a chance to answer the few lingering questions, that would be great, but I think that I have enough to keep me busy for a while. I have undertaken several times to learn user-level security, but this is the first time I feel like I might actually be getting it. Show quoteHide quote > > -- > Joan Wild > Microsoft Access MVP > BruceM wrote:
> I saw something about that in Jack MacDonald's article as well. I'll Exactly. But since mdw2 has a different Admins Group than mdw1, they won't > need to study that some more. I think I understand that only members > of the Admins group may manage user accounts. Permissions are stored > in the database (mdb) file, so when Workgroup File 1 has the same > user and group information as Workgroup File 2, the database will > "think" that it is the same group of users, and all permissions will > continue to apply. have the same permissions. So mdw2 Admins Group will be able to manage users that is: create/delete users and add/delete them from groups, but won't have any other permissions. > One thing I'm still trying to sort out has to do with permissions. As I Right.> understand it, a user who is a member of two groups will have > the least restrictive permissions. If one group can add data only, > and another can add or edit but not delete data, the user will be > able to add and edit data. > What I can't quite sort out is whether Yes they will.> this "least restrictive" rule applies to users as well. In the > example just given, if the user is given permission to delete data, > but that permission is not allowed any group of with that user is a > member, will the user be able to delete data anyhow? I think so, > because the least restrictive permission, whether it is a user Yes.> permission or a group permission, "wins". Users don't need any > permissions at all as long as they belong to groups that have > permissions. Do I understand correctly? > Joan, thanks again for all of your help. I don't think I could have You're welcome; it sounds to me like you are "getting it". It takes time, > done gotten this far, at least not anywhere near this quickly, > without it. If you have a chance to answer the few lingering > questions, that would be great, but I think that I have enough to > keep me busy for a while. I have undertaken several times to learn > user-level security, but this is the first time I feel like I might > actually be getting it. but when it clicks it makes sense. -- Joan Wild Microsoft Access MVP Hello Joan !
I have read through a few of the posts on security issues, but have yet to resolve the issue that I am having. I would be very greatful if you could point me in the right direction. I have an MDB file that I secured a few weeks back which was working fine. I did something yesterday when I unzipped a backup copy of the database (although I unzipped it to a different directory) that has caused me problems. I have an MDW file of the same name as the MDB, residing in the same directory. I join the workgroup for the MDB - which has the two users that I created when I secured the database, but when I try to open the database, I get the message about not having the necessary permission and to contact the system admin. I am thinking that I am logged in as the universal admin (since I am not prompted for a password) and am wondering how I go about trying to log in as the user I had created when I secured the database who has amin permissions. I am not being prompted to log in as I used to be. Can you help me sort this out ? Show quoteHide quote "Joan Wild" wrote: > > BruceM wrote: > > > I saw something about that in Jack MacDonald's article as well. I'll > > need to study that some more. I think I understand that only members > > of the Admins group may manage user accounts. Permissions are stored > > in the database (mdb) file, so when Workgroup File 1 has the same > > user and group information as Workgroup File 2, the database will > > "think" that it is the same group of users, and all permissions will > > continue to apply. > > Exactly. But since mdw2 has a different Admins Group than mdw1, they won't > have the same permissions. So mdw2 Admins Group will be able to manage > users that is: create/delete users and add/delete them from groups, but > won't have any other permissions. > > > One thing I'm still trying to sort out has to do with permissions. As I > > understand it, a user who is a member of two groups will have > > the least restrictive permissions. If one group can add data only, > > and another can add or edit but not delete data, the user will be > > able to add and edit data. > > Right. > > > What I can't quite sort out is whether > > this "least restrictive" rule applies to users as well. In the > > example just given, if the user is given permission to delete data, > > but that permission is not allowed any group of with that user is a > > member, will the user be able to delete data anyhow? > > Yes they will. > > I think so, > > because the least restrictive permission, whether it is a user > > permission or a group permission, "wins". Users don't need any > > permissions at all as long as they belong to groups that have > > permissions. Do I understand correctly? > > Yes. > > > Joan, thanks again for all of your help. I don't think I could have > > done gotten this far, at least not anywhere near this quickly, > > without it. If you have a chance to answer the few lingering > > questions, that would be great, but I think that I have enough to > > keep me busy for a while. I have undertaken several times to learn > > user-level security, but this is the first time I feel like I might > > actually be getting it. > > You're welcome; it sounds to me like you are "getting it". It takes time, > but when it clicks it makes sense. > > -- > Joan Wild > Microsoft Access MVP > > > "Joe G" wrote: That's not a good idea. Both the mdb and the mdw need to create an > Hello Joan ! > > I have an MDB file that I secured a few weeks back which was working fine. > I did something yesterday when I unzipped a backup copy of the database > (although I unzipped it to a different directory) that has caused me problems. > > I have an MDW file of the same name as the MDB, residing in the same > directory. associated ldb file. They can't if they have the same name. Rename the mdw file (and then modify any shortcuts as necessary). > I join the workgroup for the MDB - which has the two users that I created Are you certain you have joined the correct mdw file?> when I secured the database, but when I try to open the database, I get the > message about not having the necessary permission and to contact the system > admin. > I am thinking that I am logged in as the universal admin (since I am not When you open Access, go to Workgroup Administrator and verify the mdw you > prompted for a password) and am wondering how I go about trying to log in as > the user I had created when I secured the database who has amin permissions. > I am not being prompted to log in as I used to be. are using by default. It should be the standard system.mdw that ships with Access. Use a desktop shortcut to launch your secure mdb. "path to msaccess.exe" "path to mdb" /wrkgrp "path to mdw" When you launch via the shortcut, you should get a login prompt. If you don't then perhaps you've somehow cleared the password for the 'Admin' user or your shortcut has a problem, in which case it will use system.mdw. In either case hit Ctrl-G and type DbEngine.SystemDB which will tell you the mdw it is *using*. If it is your secure mdw then go to Tools, security, accounts, password tab - it will show you that you are logged in as Admin - set a password for this user. If it is the system.mdw then your shortcut has an error in it. -- Joan Wild Microsoft Access MVP Joan,
I mis-stated one thing below. My MDB is BladeRunner.MDB which is in a directory under MyDocuments\BladeRunner. The security file is Security.mdw and there is a Security.ldb all in the same directory. I created a shortcut but when I launch, I get the same permission message. I am by default using the secured mdw: ? dbEngine.SystemDb C:\Documents and Settings\Joe\My Documents\BladeRunner\Security.mdw I am still not prompted for a password, but appear to be logged on as Admin. I cannot change the admin password, and it tells me that the old password is incorrect. I see the users that I created, but cannot change those passwords or get prompted to log in. I am sure confused and getting nervous about this...I have invested a large chunk of time in this development effort, and sure hope you can help me understand what I've done here. Thanks again for your help. Joe Show quoteHide quote "Joan Wild" wrote: > "Joe G" wrote: > > > Hello Joan ! > > > > I have an MDB file that I secured a few weeks back which was working fine. > > I did something yesterday when I unzipped a backup copy of the database > > (although I unzipped it to a different directory) that has caused me problems. > > > > I have an MDW file of the same name as the MDB, residing in the same > > directory. > > That's not a good idea. Both the mdb and the mdw need to create an > associated ldb file. They can't if they have the same name. Rename the mdw > file (and then modify any shortcuts as necessary). > > > I join the workgroup for the MDB - which has the two users that I created > > when I secured the database, but when I try to open the database, I get the > > message about not having the necessary permission and to contact the system > > admin. > > Are you certain you have joined the correct mdw file? > > > I am thinking that I am logged in as the universal admin (since I am not > > prompted for a password) and am wondering how I go about trying to log in as > > the user I had created when I secured the database who has amin permissions. > > I am not being prompted to log in as I used to be. > > When you open Access, go to Workgroup Administrator and verify the mdw you > are using by default. It should be the standard system.mdw that ships with > Access. Use a desktop shortcut to launch your secure mdb. > "path to msaccess.exe" "path to mdb" /wrkgrp "path to mdw" > > When you launch via the shortcut, you should get a login prompt. If you > don't then perhaps you've somehow cleared the password for the 'Admin' user > or your shortcut has a problem, in which case it will use system.mdw. In > either case hit Ctrl-G and type DbEngine.SystemDB which will tell you the mdw > it is *using*. > > If it is your secure mdw then go to Tools, security, accounts, password tab > - it will show you that you are logged in as Admin - set a password for this > user. > > If it is the system.mdw then your shortcut has an error in it. > > -- > Joan Wild > Microsoft Access MVP > OK, so you know you are using security.mdw, but you get no login. That means
that the Admin password is currently blank. Go into the Accounts dialog and change password tab. Set a password for the Admin user (remember that the old password is blank). Close Access and try your shortcut again. -- Show quoteHide quoteJoan Wild Microsoft Access MVP "Joe G" wrote: > Joan, > I mis-stated one thing below. My MDB is BladeRunner.MDB which is in a > directory under MyDocuments\BladeRunner. The security file is Security.mdw > and there is a Security.ldb all in the same directory. I created a shortcut > but when I launch, I get the same permission message. > > I am by default using the secured mdw: > > ? dbEngine.SystemDb > C:\Documents and Settings\Joe\My Documents\BladeRunner\Security.mdw > > I am still not prompted for a password, but appear to be logged on as Admin. > I cannot change the admin password, and it tells me that the old password is > incorrect. I see the users that I created, but cannot change those passwords > or get prompted to log in. > > I am sure confused and getting nervous about this...I have invested a large > chunk of time in this development effort, and sure hope you can help me > understand what I've done here. Thanks again for your help. > > Joe > > > > > > "Joan Wild" wrote: > > > "Joe G" wrote: > > > > > Hello Joan ! > > > > > > I have an MDB file that I secured a few weeks back which was working fine. > > > I did something yesterday when I unzipped a backup copy of the database > > > (although I unzipped it to a different directory) that has caused me problems. > > > > > > I have an MDW file of the same name as the MDB, residing in the same > > > directory. > > > > That's not a good idea. Both the mdb and the mdw need to create an > > associated ldb file. They can't if they have the same name. Rename the mdw > > file (and then modify any shortcuts as necessary). > > > > > I join the workgroup for the MDB - which has the two users that I created > > > when I secured the database, but when I try to open the database, I get the > > > message about not having the necessary permission and to contact the system > > > admin. > > > > Are you certain you have joined the correct mdw file? > > > > > I am thinking that I am logged in as the universal admin (since I am not > > > prompted for a password) and am wondering how I go about trying to log in as > > > the user I had created when I secured the database who has amin permissions. > > > I am not being prompted to log in as I used to be. > > > > When you open Access, go to Workgroup Administrator and verify the mdw you > > are using by default. It should be the standard system.mdw that ships with > > Access. Use a desktop shortcut to launch your secure mdb. > > "path to msaccess.exe" "path to mdb" /wrkgrp "path to mdw" > > > > When you launch via the shortcut, you should get a login prompt. If you > > don't then perhaps you've somehow cleared the password for the 'Admin' user > > or your shortcut has a problem, in which case it will use system.mdw. In > > either case hit Ctrl-G and type DbEngine.SystemDB which will tell you the mdw > > it is *using*. > > > > If it is your secure mdw then go to Tools, security, accounts, password tab > > - it will show you that you are logged in as Admin - set a password for this > > user. > > > > If it is the system.mdw then your shortcut has an error in it. > > > > -- > > Joan Wild > > Microsoft Access MVP > > OK. Changed the password for admin, but then get the same message that I
don't have the necessary permissions. Cannot change the password for user Joe, who also had admin rights when I created the secured database. His password is not blank nor is it what I thought it was. Show quoteHide quote "Joan Wild" wrote: > OK, so you know you are using security.mdw, but you get no login. That means > that the Admin password is currently blank. Go into the Accounts dialog and > change password tab. Set a password for the Admin user (remember that the > old password is blank). > > Close Access and try your shortcut again. > -- > Joan Wild > Microsoft Access MVP > > > "Joe G" wrote: > > > Joan, > > I mis-stated one thing below. My MDB is BladeRunner.MDB which is in a > > directory under MyDocuments\BladeRunner. The security file is Security.mdw > > and there is a Security.ldb all in the same directory. I created a shortcut > > but when I launch, I get the same permission message. > > > > I am by default using the secured mdw: > > > > ? dbEngine.SystemDb > > C:\Documents and Settings\Joe\My Documents\BladeRunner\Security.mdw > > > > I am still not prompted for a password, but appear to be logged on as Admin. > > I cannot change the admin password, and it tells me that the old password is > > incorrect. I see the users that I created, but cannot change those passwords > > or get prompted to log in. > > > > I am sure confused and getting nervous about this...I have invested a large > > chunk of time in this development effort, and sure hope you can help me > > understand what I've done here. Thanks again for your help. > > > > Joe > > > > > > > > > > > > "Joan Wild" wrote: > > > > > "Joe G" wrote: > > > > > > > Hello Joan ! > > > > > > > > I have an MDB file that I secured a few weeks back which was working fine. > > > > I did something yesterday when I unzipped a backup copy of the database > > > > (although I unzipped it to a different directory) that has caused me problems. > > > > > > > > I have an MDW file of the same name as the MDB, residing in the same > > > > directory. > > > > > > That's not a good idea. Both the mdb and the mdw need to create an > > > associated ldb file. They can't if they have the same name. Rename the mdw > > > file (and then modify any shortcuts as necessary). > > > > > > > I join the workgroup for the MDB - which has the two users that I created > > > > when I secured the database, but when I try to open the database, I get the > > > > message about not having the necessary permission and to contact the system > > > > admin. > > > > > > Are you certain you have joined the correct mdw file? > > > > > > > I am thinking that I am logged in as the universal admin (since I am not > > > > prompted for a password) and am wondering how I go about trying to log in as > > > > the user I had created when I secured the database who has amin permissions. > > > > I am not being prompted to log in as I used to be. > > > > > > When you open Access, go to Workgroup Administrator and verify the mdw you > > > are using by default. It should be the standard system.mdw that ships with > > > Access. Use a desktop shortcut to launch your secure mdb. > > > "path to msaccess.exe" "path to mdb" /wrkgrp "path to mdw" > > > > > > When you launch via the shortcut, you should get a login prompt. If you > > > don't then perhaps you've somehow cleared the password for the 'Admin' user > > > or your shortcut has a problem, in which case it will use system.mdw. In > > > either case hit Ctrl-G and type DbEngine.SystemDB which will tell you the mdw > > > it is *using*. > > > > > > If it is your secure mdw then go to Tools, security, accounts, password tab > > > - it will show you that you are logged in as Admin - set a password for this > > > user. > > > > > > If it is the system.mdw then your shortcut has an error in it. > > > > > > -- > > > Joan Wild > > > Microsoft Access MVP > > > Remember that passwords are case sensitive.
Since this started when you restored a backup, perhaps that backup doesn't have the permissions set correctly. When you check the owner tab in the permissions dialog, what user is listed as owner of everything? -- Show quoteHide quoteJoan Wild Microsoft Access MVP "Joe G" wrote: > OK. Changed the password for admin, but then get the same message that I > don't have the necessary permissions. Cannot change the password for user > Joe, who also had admin rights when I created the secured database. His > password is not blank nor is it what I thought it was. > > "Joan Wild" wrote: > > > OK, so you know you are using security.mdw, but you get no login. That means > > that the Admin password is currently blank. Go into the Accounts dialog and > > change password tab. Set a password for the Admin user (remember that the > > old password is blank). > > > > Close Access and try your shortcut again. > > -- > > Joan Wild > > Microsoft Access MVP > > > > > > "Joe G" wrote: > > > > > Joan, > > > I mis-stated one thing below. My MDB is BladeRunner.MDB which is in a > > > directory under MyDocuments\BladeRunner. The security file is Security.mdw > > > and there is a Security.ldb all in the same directory. I created a shortcut > > > but when I launch, I get the same permission message. > > > > > > I am by default using the secured mdw: > > > > > > ? dbEngine.SystemDb > > > C:\Documents and Settings\Joe\My Documents\BladeRunner\Security.mdw > > > > > > I am still not prompted for a password, but appear to be logged on as Admin. > > > I cannot change the admin password, and it tells me that the old password is > > > incorrect. I see the users that I created, but cannot change those passwords > > > or get prompted to log in. > > > > > > I am sure confused and getting nervous about this...I have invested a large > > > chunk of time in this development effort, and sure hope you can help me > > > understand what I've done here. Thanks again for your help. > > > > > > Joe > > > > > > > > > > > > > > > > > > "Joan Wild" wrote: > > > > > > > "Joe G" wrote: > > > > > > > > > Hello Joan ! > > > > > > > > > > I have an MDB file that I secured a few weeks back which was working fine. > > > > > I did something yesterday when I unzipped a backup copy of the database > > > > > (although I unzipped it to a different directory) that has caused me problems. > > > > > > > > > > I have an MDW file of the same name as the MDB, residing in the same > > > > > directory. > > > > > > > > That's not a good idea. Both the mdb and the mdw need to create an > > > > associated ldb file. They can't if they have the same name. Rename the mdw > > > > file (and then modify any shortcuts as necessary). > > > > > > > > > I join the workgroup for the MDB - which has the two users that I created > > > > > when I secured the database, but when I try to open the database, I get the > > > > > message about not having the necessary permission and to contact the system > > > > > admin. > > > > > > > > Are you certain you have joined the correct mdw file? > > > > > > > > > I am thinking that I am logged in as the universal admin (since I am not > > > > > prompted for a password) and am wondering how I go about trying to log in as > > > > > the user I had created when I secured the database who has amin permissions. > > > > > I am not being prompted to log in as I used to be. > > > > > > > > When you open Access, go to Workgroup Administrator and verify the mdw you > > > > are using by default. It should be the standard system.mdw that ships with > > > > Access. Use a desktop shortcut to launch your secure mdb. > > > > "path to msaccess.exe" "path to mdb" /wrkgrp "path to mdw" > > > > > > > > When you launch via the shortcut, you should get a login prompt. If you > > > > don't then perhaps you've somehow cleared the password for the 'Admin' user > > > > or your shortcut has a problem, in which case it will use system.mdw. In > > > > either case hit Ctrl-G and type DbEngine.SystemDB which will tell you the mdw > > > > it is *using*. > > > > > > > > If it is your secure mdw then go to Tools, security, accounts, password tab > > > > - it will show you that you are logged in as Admin - set a password for this > > > > user. > > > > > > > > If it is the system.mdw then your shortcut has an error in it. > > > > > > > > -- > > > > Joan Wild > > > > Microsoft Access MVP > > > > Double checked the case sensitivity...none of the backups are working. I
don't get the permissions tab enabled, even though I log in as Admin. Are the user names stored in the MDB or the MDW ? All of my backups at this point had been using the same security MDW. I am assuming that this MDW is the correct one because I see users listed. Are you an employee of Microsoft, Joan ? I am relatively knew to MS Access. I have been developing with PowerBuilder for the last ten plus years. Again. Appreciate the help. Joe Show quoteHide quote "Joan Wild" wrote: > Remember that passwords are case sensitive. > > Since this started when you restored a backup, perhaps that backup doesn't > have the permissions set correctly. When you check the owner tab in the > permissions dialog, what user is listed as owner of everything? > > -- > Joan Wild > Microsoft Access MVP > > > "Joe G" wrote: > > > OK. Changed the password for admin, but then get the same message that I > > don't have the necessary permissions. Cannot change the password for user > > Joe, who also had admin rights when I created the secured database. His > > password is not blank nor is it what I thought it was. > > > > "Joan Wild" wrote: > > > > > OK, so you know you are using security.mdw, but you get no login. That means > > > that the Admin password is currently blank. Go into the Accounts dialog and > > > change password tab. Set a password for the Admin user (remember that the > > > old password is blank). > > > > > > Close Access and try your shortcut again. > > > -- > > > Joan Wild > > > Microsoft Access MVP > > > > > > > > > "Joe G" wrote: > > > > > > > Joan, > > > > I mis-stated one thing below. My MDB is BladeRunner.MDB which is in a > > > > directory under MyDocuments\BladeRunner. The security file is Security.mdw > > > > and there is a Security.ldb all in the same directory. I created a shortcut > > > > but when I launch, I get the same permission message. > > > > > > > > I am by default using the secured mdw: > > > > > > > > ? dbEngine.SystemDb > > > > C:\Documents and Settings\Joe\My Documents\BladeRunner\Security.mdw > > > > > > > > I am still not prompted for a password, but appear to be logged on as Admin. > > > > I cannot change the admin password, and it tells me that the old password is > > > > incorrect. I see the users that I created, but cannot change those passwords > > > > or get prompted to log in. > > > > > > > > I am sure confused and getting nervous about this...I have invested a large > > > > chunk of time in this development effort, and sure hope you can help me > > > > understand what I've done here. Thanks again for your help. > > > > > > > > Joe > > > > > > > > > > > > > > > > > > > > > > > > "Joan Wild" wrote: > > > > > > > > > "Joe G" wrote: > > > > > > > > > > > Hello Joan ! > > > > > > > > > > > > I have an MDB file that I secured a few weeks back which was working fine. > > > > > > I did something yesterday when I unzipped a backup copy of the database > > > > > > (although I unzipped it to a different directory) that has caused me problems. > > > > > > > > > > > > I have an MDW file of the same name as the MDB, residing in the same > > > > > > directory. > > > > > > > > > > That's not a good idea. Both the mdb and the mdw need to create an > > > > > associated ldb file. They can't if they have the same name. Rename the mdw > > > > > file (and then modify any shortcuts as necessary). > > > > > > > > > > > I join the workgroup for the MDB - which has the two users that I created > > > > > > when I secured the database, but when I try to open the database, I get the > > > > > > message about not having the necessary permission and to contact the system > > > > > > admin. > > > > > > > > > > Are you certain you have joined the correct mdw file? > > > > > > > > > > > I am thinking that I am logged in as the universal admin (since I am not > > > > > > prompted for a password) and am wondering how I go about trying to log in as > > > > > > the user I had created when I secured the database who has amin permissions. > > > > > > I am not being prompted to log in as I used to be. > > > > > > > > > > When you open Access, go to Workgroup Administrator and verify the mdw you > > > > > are using by default. It should be the standard system.mdw that ships with > > > > > Access. Use a desktop shortcut to launch your secure mdb. > > > > > "path to msaccess.exe" "path to mdb" /wrkgrp "path to mdw" > > > > > > > > > > When you launch via the shortcut, you should get a login prompt. If you > > > > > don't then perhaps you've somehow cleared the password for the 'Admin' user > > > > > or your shortcut has a problem, in which case it will use system.mdw. In > > > > > either case hit Ctrl-G and type DbEngine.SystemDB which will tell you the mdw > > > > > it is *using*. > > > > > > > > > > If it is your secure mdw then go to Tools, security, accounts, password tab > > > > > - it will show you that you are logged in as Admin - set a password for this > > > > > user. > > > > > > > > > > If it is the system.mdw then your shortcut has an error in it. > > > > > > > > > > -- > > > > > Joan Wild > > > > > Microsoft Access MVP > > > > > You shouldn't be logging in as Admin, since that user doesn't (shouldn't)
have permissions to do anything. You just wanted to set a password for this user so that the login dialog would appear. You now want to log in as the user that owns the database. Usernames/passwords/group membership are stored in the mdw. Permissions are stored in the mdb. So your various backups may have different permissions on the objects. No I am not an employee of MS. -- Show quoteHide quoteJoan Wild Microsoft Access MVP "Joe G" wrote: > Double checked the case sensitivity...none of the backups are working. I > don't get the permissions tab enabled, even though I log in as Admin. > Are the user names stored in the MDB or the MDW ? All of my backups at this > point had been using the same security MDW. I am assuming that this MDW is > the correct one because I see users listed. Are you an employee of > Microsoft, Joan ? > I am relatively knew to MS Access. I have been developing with PowerBuilder > for the last ten plus years. Again. Appreciate the help. > > Joe > > "Joan Wild" wrote: > > > Remember that passwords are case sensitive. > > > > Since this started when you restored a backup, perhaps that backup doesn't > > have the permissions set correctly. When you check the owner tab in the > > permissions dialog, what user is listed as owner of everything? > > > > -- > > Joan Wild > > Microsoft Access MVP > > > > > > "Joe G" wrote: > > > > > OK. Changed the password for admin, but then get the same message that I > > > don't have the necessary permissions. Cannot change the password for user > > > Joe, who also had admin rights when I created the secured database. His > > > password is not blank nor is it what I thought it was. > > > > > > "Joan Wild" wrote: > > > > > > > OK, so you know you are using security.mdw, but you get no login. That means > > > > that the Admin password is currently blank. Go into the Accounts dialog and > > > > change password tab. Set a password for the Admin user (remember that the > > > > old password is blank). > > > > > > > > Close Access and try your shortcut again. > > > > -- > > > > Joan Wild > > > > Microsoft Access MVP > > > > > > > > > > > > "Joe G" wrote: > > > > > > > > > Joan, > > > > > I mis-stated one thing below. My MDB is BladeRunner.MDB which is in a > > > > > directory under MyDocuments\BladeRunner. The security file is Security.mdw > > > > > and there is a Security.ldb all in the same directory. I created a shortcut > > > > > but when I launch, I get the same permission message. > > > > > > > > > > I am by default using the secured mdw: > > > > > > > > > > ? dbEngine.SystemDb > > > > > C:\Documents and Settings\Joe\My Documents\BladeRunner\Security.mdw > > > > > > > > > > I am still not prompted for a password, but appear to be logged on as Admin. > > > > > I cannot change the admin password, and it tells me that the old password is > > > > > incorrect. I see the users that I created, but cannot change those passwords > > > > > or get prompted to log in. > > > > > > > > > > I am sure confused and getting nervous about this...I have invested a large > > > > > chunk of time in this development effort, and sure hope you can help me > > > > > understand what I've done here. Thanks again for your help. > > > > > > > > > > Joe > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > "Joan Wild" wrote: > > > > > > > > > > > "Joe G" wrote: > > > > > > > > > > > > > Hello Joan ! > > > > > > > > > > > > > > I have an MDB file that I secured a few weeks back which was working fine. > > > > > > > I did something yesterday when I unzipped a backup copy of the database > > > > > > > (although I unzipped it to a different directory) that has caused me problems. > > > > > > > > > > > > > > I have an MDW file of the same name as the MDB, residing in the same > > > > > > > directory. > > > > > > > > > > > > That's not a good idea. Both the mdb and the mdw need to create an > > > > > > associated ldb file. They can't if they have the same name. Rename the mdw > > > > > > file (and then modify any shortcuts as necessary). > > > > > > > > > > > > > I join the workgroup for the MDB - which has the two users that I created > > > > > > > when I secured the database, but when I try to open the database, I get the > > > > > > > message about not having the necessary permission and to contact the system > > > > > > > admin. > > > > > > > > > > > > Are you certain you have joined the correct mdw file? > > > > > > > > > > > > > I am thinking that I am logged in as the universal admin (since I am not > > > > > > > prompted for a password) and am wondering how I go about trying to log in as > > > > > > > the user I had created when I secured the database who has amin permissions. > > > > > > > I am not being prompted to log in as I used to be. > > > > > > > > > > > > When you open Access, go to Workgroup Administrator and verify the mdw you > > > > > > are using by default. It should be the standard system.mdw that ships with > > > > > > Access. Use a desktop shortcut to launch your secure mdb. > > > > > > "path to msaccess.exe" "path to mdb" /wrkgrp "path to mdw" > > > > > > > > > > > > When you launch via the shortcut, you should get a login prompt. If you > > > > > > don't then perhaps you've somehow cleared the password for the 'Admin' user > > > > > > or your shortcut has a problem, in which case it will use system.mdw. In > > > > > > either case hit Ctrl-G and type DbEngine.SystemDB which will tell you the mdw > > > > > > it is *using*. > > > > > > > > > > > > If it is your secure mdw then go to Tools, security, accounts, password tab > > > > > > - it will show you that you are logged in as Admin - set a password for this > > > > > > user. > > > > > > > > > > > > If it is the system.mdw then your shortcut has an error in it. > > > > > > > > > > > > -- > > > > > > Joan Wild > > > > > > Microsoft Access MVP > > > > > > Joan,
This response showed up in a different thread than the one in which you intended to post it. Show quoteHide quote "Joan Wild" <jwild@nospamtyenet.com> wrote in message news:BF752029-7556-4CDA-B016-82C46C303B64@microsoft.com... > You shouldn't be logging in as Admin, since that user doesn't (shouldn't) > have permissions to do anything. You just wanted to set a password for > this > user so that the login dialog would appear. > > You now want to log in as the user that owns the database. > > Usernames/passwords/group membership are stored in the mdw. Permissions > are > stored in the mdb. So your various backups may have different permissions > on > the objects. > > No I am not an employee of MS. > > -- > Joan Wild > Microsoft Access MVP > > > "Joe G" wrote: > >> Double checked the case sensitivity...none of the backups are working. I >> don't get the permissions tab enabled, even though I log in as Admin. >> Are the user names stored in the MDB or the MDW ? All of my backups at >> this >> point had been using the same security MDW. I am assuming that this MDW >> is >> the correct one because I see users listed. Are you an employee of >> Microsoft, Joan ? >> I am relatively knew to MS Access. I have been developing with >> PowerBuilder >> for the last ten plus years. Again. Appreciate the help. >> >> Joe >> >> "Joan Wild" wrote: >> >> > Remember that passwords are case sensitive. >> > >> > Since this started when you restored a backup, perhaps that backup >> > doesn't >> > have the permissions set correctly. When you check the owner tab in >> > the >> > permissions dialog, what user is listed as owner of everything? >> > >> > -- >> > Joan Wild >> > Microsoft Access MVP >> > >> > >> > "Joe G" wrote: >> > >> > > OK. Changed the password for admin, but then get the same message >> > > that I >> > > don't have the necessary permissions. Cannot change the password for >> > > user >> > > Joe, who also had admin rights when I created the secured database. >> > > His >> > > password is not blank nor is it what I thought it was. >> > > >> > > "Joan Wild" wrote: >> > > >> > > > OK, so you know you are using security.mdw, but you get no login. >> > > > That means >> > > > that the Admin password is currently blank. Go into the Accounts >> > > > dialog and >> > > > change password tab. Set a password for the Admin user (remember >> > > > that the >> > > > old password is blank). >> > > > >> > > > Close Access and try your shortcut again. >> > > > -- >> > > > Joan Wild >> > > > Microsoft Access MVP >> > > > >> > > > >> > > > "Joe G" wrote: >> > > > >> > > > > Joan, >> > > > > I mis-stated one thing below. My MDB is BladeRunner.MDB which is >> > > > > in a >> > > > > directory under MyDocuments\BladeRunner. The security file is >> > > > > Security.mdw >> > > > > and there is a Security.ldb all in the same directory. I created >> > > > > a shortcut >> > > > > but when I launch, I get the same permission message. >> > > > > >> > > > > I am by default using the secured mdw: >> > > > > >> > > > > ? dbEngine.SystemDb >> > > > > C:\Documents and Settings\Joe\My >> > > > > Documents\BladeRunner\Security.mdw >> > > > > >> > > > > I am still not prompted for a password, but appear to be logged >> > > > > on as Admin. >> > > > > I cannot change the admin password, and it tells me that the old >> > > > > password is >> > > > > incorrect. I see the users that I created, but cannot change >> > > > > those passwords >> > > > > or get prompted to log in. >> > > > > >> > > > > I am sure confused and getting nervous about this...I have >> > > > > invested a large >> > > > > chunk of time in this development effort, and sure hope you can >> > > > > help me >> > > > > understand what I've done here. Thanks again for your help. >> > > > > >> > > > > Joe >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > "Joan Wild" wrote: >> > > > > >> > > > > > "Joe G" wrote: >> > > > > > >> > > > > > > Hello Joan ! >> > > > > > > >> > > > > > > I have an MDB file that I secured a few weeks back which was >> > > > > > > working fine. >> > > > > > > I did something yesterday when I unzipped a backup copy of >> > > > > > > the database >> > > > > > > (although I unzipped it to a different directory) that has >> > > > > > > caused me problems. >> > > > > > > >> > > > > > > I have an MDW file of the same name as the MDB, residing in >> > > > > > > the same >> > > > > > > directory. >> > > > > > >> > > > > > That's not a good idea. Both the mdb and the mdw need to >> > > > > > create an >> > > > > > associated ldb file. They can't if they have the same name. >> > > > > > Rename the mdw >> > > > > > file (and then modify any shortcuts as necessary). >> > > > > > >> > > > > > > I join the workgroup for the MDB - which has the two users >> > > > > > > that I created >> > > > > > > when I secured the database, but when I try to open the >> > > > > > > database, I get the >> > > > > > > message about not having the necessary permission and to >> > > > > > > contact the system >> > > > > > > admin. >> > > > > > >> > > > > > Are you certain you have joined the correct mdw file? >> > > > > > >> > > > > > > I am thinking that I am logged in as the universal admin >> > > > > > > (since I am not >> > > > > > > prompted for a password) and am wondering how I go about >> > > > > > > trying to log in as >> > > > > > > the user I had created when I secured the database who has >> > > > > > > amin permissions. >> > > > > > > I am not being prompted to log in as I used to be. >> > > > > > >> > > > > > When you open Access, go to Workgroup Administrator and verify >> > > > > > the mdw you >> > > > > > are using by default. It should be the standard system.mdw >> > > > > > that ships with >> > > > > > Access. Use a desktop shortcut to launch your secure mdb. >> > > > > > "path to msaccess.exe" "path to mdb" /wrkgrp "path to mdw" >> > > > > > >> > > > > > When you launch via the shortcut, you should get a login >> > > > > > prompt. If you >> > > > > > don't then perhaps you've somehow cleared the password for the >> > > > > > 'Admin' user >> > > > > > or your shortcut has a problem, in which case it will use >> > > > > > system.mdw. In >> > > > > > either case hit Ctrl-G and type DbEngine.SystemDB which will >> > > > > > tell you the mdw >> > > > > > it is *using*. >> > > > > > >> > > > > > If it is your secure mdw then go to Tools, security, accounts, >> > > > > > password tab >> > > > > > - it will show you that you are logged in as Admin - set a >> > > > > > password for this >> > > > > > user. >> > > > > > >> > > > > > If it is the system.mdw then your shortcut has an error in it. >> > > > > > >> > > > > > -- >> > > > > > Joan Wild >> > > > > > Microsoft Access MVP >> > > > > > ?? Not in my newsreader.
-- Show quoteHide quoteJoan Wild Microsoft Access MVP BruceM wrote: > Joan, > > This response showed up in a different thread than the one in which > you intended to post it. > > "Joan Wild" <jwild@nospamtyenet.com> wrote in message > news:BF752029-7556-4CDA-B016-82C46C303B64@microsoft.com... >> You shouldn't be logging in as Admin, since that user doesn't >> (shouldn't) have permissions to do anything. You just wanted to set >> a password for this >> user so that the login dialog would appear. >> >> You now want to log in as the user that owns the database. >> >> Usernames/passwords/group membership are stored in the mdw. Permissions >> are >> stored in the mdb. So your various backups may have different >> permissions on >> the objects. >> >> No I am not an employee of MS. >> >> -- >> Joan Wild >> Microsoft Access MVP >> >> >> "Joe G" wrote: >> >>> Double checked the case sensitivity...none of the backups are >>> working. I don't get the permissions tab enabled, even though I >>> log in as Admin. Are the user names stored in the MDB or the MDW ? All >>> of my backups at this >>> point had been using the same security MDW. I am assuming that >>> this MDW is >>> the correct one because I see users listed. Are you an employee of >>> Microsoft, Joan ? >>> I am relatively knew to MS Access. I have been developing with >>> PowerBuilder >>> for the last ten plus years. Again. Appreciate the help. >>> >>> Joe >>> >>> "Joan Wild" wrote: >>> >>>> Remember that passwords are case sensitive. >>>> >>>> Since this started when you restored a backup, perhaps that backup >>>> doesn't >>>> have the permissions set correctly. When you check the owner tab >>>> in the >>>> permissions dialog, what user is listed as owner of everything? >>>> >>>> -- >>>> Joan Wild >>>> Microsoft Access MVP >>>> >>>> >>>> "Joe G" wrote: >>>> >>>>> OK. Changed the password for admin, but then get the same message >>>>> that I >>>>> don't have the necessary permissions. Cannot change the password >>>>> for user >>>>> Joe, who also had admin rights when I created the secured >>>>> database. His >>>>> password is not blank nor is it what I thought it was. >>>>> >>>>> "Joan Wild" wrote: >>>>> >>>>>> OK, so you know you are using security.mdw, but you get no login. >>>>>> That means >>>>>> that the Admin password is currently blank. Go into the Accounts >>>>>> dialog and >>>>>> change password tab. Set a password for the Admin user (remember >>>>>> that the >>>>>> old password is blank). >>>>>> >>>>>> Close Access and try your shortcut again. >>>>>> -- >>>>>> Joan Wild >>>>>> Microsoft Access MVP >>>>>> >>>>>> >>>>>> "Joe G" wrote: >>>>>> >>>>>>> Joan, >>>>>>> I mis-stated one thing below. My MDB is BladeRunner.MDB which >>>>>>> is in a >>>>>>> directory under MyDocuments\BladeRunner. The security file is >>>>>>> Security.mdw >>>>>>> and there is a Security.ldb all in the same directory. I >>>>>>> created a shortcut >>>>>>> but when I launch, I get the same permission message. >>>>>>> >>>>>>> I am by default using the secured mdw: >>>>>>> >>>>>>> ? dbEngine.SystemDb >>>>>>> C:\Documents and Settings\Joe\My >>>>>>> Documents\BladeRunner\Security.mdw >>>>>>> >>>>>>> I am still not prompted for a password, but appear to be logged >>>>>>> on as Admin. >>>>>>> I cannot change the admin password, and it tells me that the old >>>>>>> password is >>>>>>> incorrect. I see the users that I created, but cannot change >>>>>>> those passwords >>>>>>> or get prompted to log in. >>>>>>> >>>>>>> I am sure confused and getting nervous about this...I have >>>>>>> invested a large >>>>>>> chunk of time in this development effort, and sure hope you can >>>>>>> help me >>>>>>> understand what I've done here. Thanks again for your help. >>>>>>> >>>>>>> Joe >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> "Joan Wild" wrote: >>>>>>> >>>>>>>> "Joe G" wrote: >>>>>>>> >>>>>>>>> Hello Joan ! >>>>>>>>> >>>>>>>>> I have an MDB file that I secured a few weeks back which was >>>>>>>>> working fine. >>>>>>>>> I did something yesterday when I unzipped a backup copy of >>>>>>>>> the database >>>>>>>>> (although I unzipped it to a different directory) that has >>>>>>>>> caused me problems. >>>>>>>>> >>>>>>>>> I have an MDW file of the same name as the MDB, residing in >>>>>>>>> the same >>>>>>>>> directory. >>>>>>>> >>>>>>>> That's not a good idea. Both the mdb and the mdw need to >>>>>>>> create an >>>>>>>> associated ldb file. They can't if they have the same name. >>>>>>>> Rename the mdw >>>>>>>> file (and then modify any shortcuts as necessary). >>>>>>>> >>>>>>>>> I join the workgroup for the MDB - which has the two users >>>>>>>>> that I created >>>>>>>>> when I secured the database, but when I try to open the >>>>>>>>> database, I get the >>>>>>>>> message about not having the necessary permission and to >>>>>>>>> contact the system >>>>>>>>> admin. >>>>>>>> >>>>>>>> Are you certain you have joined the correct mdw file? >>>>>>>> >>>>>>>>> I am thinking that I am logged in as the universal admin >>>>>>>>> (since I am not >>>>>>>>> prompted for a password) and am wondering how I go about >>>>>>>>> trying to log in as >>>>>>>>> the user I had created when I secured the database who has >>>>>>>>> amin permissions. >>>>>>>>> I am not being prompted to log in as I used to be. >>>>>>>> >>>>>>>> When you open Access, go to Workgroup Administrator and verify >>>>>>>> the mdw you >>>>>>>> are using by default. It should be the standard system.mdw >>>>>>>> that ships with >>>>>>>> Access. Use a desktop shortcut to launch your secure mdb. >>>>>>>> "path to msaccess.exe" "path to mdb" /wrkgrp "path to mdw" >>>>>>>> >>>>>>>> When you launch via the shortcut, you should get a login >>>>>>>> prompt. If you >>>>>>>> don't then perhaps you've somehow cleared the password for the >>>>>>>> 'Admin' user >>>>>>>> or your shortcut has a problem, in which case it will use >>>>>>>> system.mdw. In >>>>>>>> either case hit Ctrl-G and type DbEngine.SystemDB which will >>>>>>>> tell you the mdw >>>>>>>> it is *using*. >>>>>>>> >>>>>>>> If it is your secure mdw then go to Tools, security, accounts, >>>>>>>> password tab >>>>>>>> - it will show you that you are logged in as Admin - set a >>>>>>>> password for this >>>>>>>> user. >>>>>>>> >>>>>>>> If it is the system.mdw then your shortcut has an error in it. >>>>>>>> >>>>>>>> -- >>>>>>>> Joan Wild >>>>>>>> Microsoft Access MVP Bruce,
Actually, Joe G interjected his question intoyour original thread and all the posts between he and Joan were not showing up yesterday. They are all appearing today. Some problem with the synchronization on the servers. Show quoteHide quote "BruceM" <bam***@yawhodawtcalm.not> wrote in message news:O0tf$CMFHHA.1080@TK2MSFTNGP05.phx.gbl... > Joan, > > This response showed up in a different thread than the one in which you > intended to post it. > > "Joan Wild" <jwild@nospamtyenet.com> wrote in message > news:BF752029-7556-4CDA-B016-82C46C303B64@microsoft.com... >> You shouldn't be logging in as Admin, since that user doesn't (shouldn't) >> have permissions to do anything. You just wanted to set a password for >> this >> user so that the login dialog would appear. >> >> You now want to log in as the user that owns the database. >> >> Usernames/passwords/group membership are stored in the mdw. Permissions >> are >> stored in the mdb. So your various backups may have different >> permissions on >> the objects. >> >> No I am not an employee of MS. >> >> -- >> Joan Wild >> Microsoft Access MVP >> >> >> "Joe G" wrote: >> >>> Double checked the case sensitivity...none of the backups are working. >>> I >>> don't get the permissions tab enabled, even though I log in as Admin. >>> Are the user names stored in the MDB or the MDW ? All of my backups at >>> this >>> point had been using the same security MDW. I am assuming that this MDW >>> is >>> the correct one because I see users listed. Are you an employee of >>> Microsoft, Joan ? >>> I am relatively knew to MS Access. I have been developing with >>> PowerBuilder >>> for the last ten plus years. Again. Appreciate the help. >>> >>> Joe >>> >>> "Joan Wild" wrote: >>> >>> > Remember that passwords are case sensitive. >>> > >>> > Since this started when you restored a backup, perhaps that backup >>> > doesn't >>> > have the permissions set correctly. When you check the owner tab in >>> > the >>> > permissions dialog, what user is listed as owner of everything? >>> > >>> > -- >>> > Joan Wild >>> > Microsoft Access MVP >>> > >>> > >>> > "Joe G" wrote: >>> > >>> > > OK. Changed the password for admin, but then get the same message >>> > > that I >>> > > don't have the necessary permissions. Cannot change the password >>> > > for user >>> > > Joe, who also had admin rights when I created the secured database. >>> > > His >>> > > password is not blank nor is it what I thought it was. >>> > > >>> > > "Joan Wild" wrote: >>> > > >>> > > > OK, so you know you are using security.mdw, but you get no login. >>> > > > That means >>> > > > that the Admin password is currently blank. Go into the Accounts >>> > > > dialog and >>> > > > change password tab. Set a password for the Admin user (remember >>> > > > that the >>> > > > old password is blank). >>> > > > >>> > > > Close Access and try your shortcut again. >>> > > > -- >>> > > > Joan Wild >>> > > > Microsoft Access MVP >>> > > > >>> > > > >>> > > > "Joe G" wrote: >>> > > > >>> > > > > Joan, >>> > > > > I mis-stated one thing below. My MDB is BladeRunner.MDB which >>> > > > > is in a >>> > > > > directory under MyDocuments\BladeRunner. The security file is >>> > > > > Security.mdw >>> > > > > and there is a Security.ldb all in the same directory. I >>> > > > > created a shortcut >>> > > > > but when I launch, I get the same permission message. >>> > > > > >>> > > > > I am by default using the secured mdw: >>> > > > > >>> > > > > ? dbEngine.SystemDb >>> > > > > C:\Documents and Settings\Joe\My >>> > > > > Documents\BladeRunner\Security.mdw >>> > > > > >>> > > > > I am still not prompted for a password, but appear to be logged >>> > > > > on as Admin. >>> > > > > I cannot change the admin password, and it tells me that the old >>> > > > > password is >>> > > > > incorrect. I see the users that I created, but cannot change >>> > > > > those passwords >>> > > > > or get prompted to log in. >>> > > > > >>> > > > > I am sure confused and getting nervous about this...I have >>> > > > > invested a large >>> > > > > chunk of time in this development effort, and sure hope you can >>> > > > > help me >>> > > > > understand what I've done here. Thanks again for your help. >>> > > > > >>> > > > > Joe >>> > > > > >>> > > > > >>> > > > > >>> > > > > >>> > > > > >>> > > > > "Joan Wild" wrote: >>> > > > > >>> > > > > > "Joe G" wrote: >>> > > > > > >>> > > > > > > Hello Joan ! >>> > > > > > > >>> > > > > > > I have an MDB file that I secured a few weeks back which was >>> > > > > > > working fine. >>> > > > > > > I did something yesterday when I unzipped a backup copy of >>> > > > > > > the database >>> > > > > > > (although I unzipped it to a different directory) that has >>> > > > > > > caused me problems. >>> > > > > > > >>> > > > > > > I have an MDW file of the same name as the MDB, residing in >>> > > > > > > the same >>> > > > > > > directory. >>> > > > > > >>> > > > > > That's not a good idea. Both the mdb and the mdw need to >>> > > > > > create an >>> > > > > > associated ldb file. They can't if they have the same name. >>> > > > > > Rename the mdw >>> > > > > > file (and then modify any shortcuts as necessary). >>> > > > > > >>> > > > > > > I join the workgroup for the MDB - which has the two users >>> > > > > > > that I created >>> > > > > > > when I secured the database, but when I try to open the >>> > > > > > > database, I get the >>> > > > > > > message about not having the necessary permission and to >>> > > > > > > contact the system >>> > > > > > > admin. >>> > > > > > >>> > > > > > Are you certain you have joined the correct mdw file? >>> > > > > > >>> > > > > > > I am thinking that I am logged in as the universal admin >>> > > > > > > (since I am not >>> > > > > > > prompted for a password) and am wondering how I go about >>> > > > > > > trying to log in as >>> > > > > > > the user I had created when I secured the database who has >>> > > > > > > amin permissions. >>> > > > > > > I am not being prompted to log in as I used to be. >>> > > > > > >>> > > > > > When you open Access, go to Workgroup Administrator and verify >>> > > > > > the mdw you >>> > > > > > are using by default. It should be the standard system.mdw >>> > > > > > that ships with >>> > > > > > Access. Use a desktop shortcut to launch your secure mdb. >>> > > > > > "path to msaccess.exe" "path to mdb" /wrkgrp "path to mdw" >>> > > > > > >>> > > > > > When you launch via the shortcut, you should get a login >>> > > > > > prompt. If you >>> > > > > > don't then perhaps you've somehow cleared the password for the >>> > > > > > 'Admin' user >>> > > > > > or your shortcut has a problem, in which case it will use >>> > > > > > system.mdw. In >>> > > > > > either case hit Ctrl-G and type DbEngine.SystemDB which will >>> > > > > > tell you the mdw >>> > > > > > it is *using*. >>> > > > > > >>> > > > > > If it is your secure mdw then go to Tools, security, accounts, >>> > > > > > password tab >>> > > > > > - it will show you that you are logged in as Admin - set a >>> > > > > > password for this >>> > > > > > user. >>> > > > > > >>> > > > > > If it is the system.mdw then your shortcut has an error in it. >>> > > > > > >>> > > > > > -- >>> > > > > > Joan Wild >>> > > > > > Microsoft Access MVP >>> > > > > > > > All,
Thank you for allowing me to hop onto this thread. I have never before used this type of forum, and hope that I have not been out of line. I realize now that I probably should have created a new question rather than jump into Bruce's discussion. I am in a deep bind here, and need to resolve this security issue. If anyone can point me in the right direction here, with regard to how I might resolve this in the most expeditious way possible, I would be most grateful. In all of my reading thus far, I have yet to see how to resolve this. I have a security.mdw that for some reason is not allowing me access to my mdb at all. Thanks in advance, Joe Show quoteHide quote "Lynn Trapp" wrote: > Bruce, > Actually, Joe G interjected his question intoyour original thread and all > the posts between he and Joan were not showing up yesterday. They are all > appearing today. Some problem with the synchronization on the servers. > > -- > > Lynn Trapp > Microsoft MVP (Access) > www.ltcomputerdesigns.com > > > "BruceM" <bam***@yawhodawtcalm.not> wrote in message > news:O0tf$CMFHHA.1080@TK2MSFTNGP05.phx.gbl... > > Joan, > > > > This response showed up in a different thread than the one in which you > > intended to post it. > > > > "Joan Wild" <jwild@nospamtyenet.com> wrote in message > > news:BF752029-7556-4CDA-B016-82C46C303B64@microsoft.com... > >> You shouldn't be logging in as Admin, since that user doesn't (shouldn't) > >> have permissions to do anything. You just wanted to set a password for > >> this > >> user so that the login dialog would appear. > >> > >> You now want to log in as the user that owns the database. > >> > >> Usernames/passwords/group membership are stored in the mdw. Permissions > >> are > >> stored in the mdb. So your various backups may have different > >> permissions on > >> the objects. > >> > >> No I am not an employee of MS. > >> > >> -- > >> Joan Wild > >> Microsoft Access MVP > >> > >> > >> "Joe G" wrote: > >> > >>> Double checked the case sensitivity...none of the backups are working. > >>> I > >>> don't get the permissions tab enabled, even though I log in as Admin. > >>> Are the user names stored in the MDB or the MDW ? All of my backups at > >>> this > >>> point had been using the same security MDW. I am assuming that this MDW > >>> is > >>> the correct one because I see users listed. Are you an employee of > >>> Microsoft, Joan ? > >>> I am relatively knew to MS Access. I have been developing with > >>> PowerBuilder > >>> for the last ten plus years. Again. Appreciate the help. > >>> > >>> Joe > >>> > >>> "Joan Wild" wrote: > >>> > >>> > Remember that passwords are case sensitive. > >>> > > >>> > Since this started when you restored a backup, perhaps that backup > >>> > doesn't > >>> > have the permissions set correctly. When you check the owner tab in > >>> > the > >>> > permissions dialog, what user is listed as owner of everything? > >>> > > >>> > -- > >>> > Joan Wild > >>> > Microsoft Access MVP > >>> > > >>> > > >>> > "Joe G" wrote: > >>> > > >>> > > OK. Changed the password for admin, but then get the same message > >>> > > that I > >>> > > don't have the necessary permissions. Cannot change the password > >>> > > for user > >>> > > Joe, who also had admin rights when I created the secured database. > >>> > > His > >>> > > password is not blank nor is it what I thought it was. > >>> > > > >>> > > "Joan Wild" wrote: > >>> > > > >>> > > > OK, so you know you are using security.mdw, but you get no login. > >>> > > > That means > >>> > > > that the Admin password is currently blank. Go into the Accounts > >>> > > > dialog and > >>> > > > change password tab. Set a password for the Admin user (remember > >>> > > > that the > >>> > > > old password is blank). > >>> > > > > >>> > > > Close Access and try your shortcut again. > >>> > > > -- > >>> > > > Joan Wild > >>> > > > Microsoft Access MVP > >>> > > > > >>> > > > > >>> > > > "Joe G" wrote: > >>> > > > > >>> > > > > Joan, > >>> > > > > I mis-stated one thing below. My MDB is BladeRunner.MDB which > >>> > > > > is in a > >>> > > > > directory under MyDocuments\BladeRunner. The security file is > >>> > > > > Security.mdw > >>> > > > > and there is a Security.ldb all in the same directory. I > >>> > > > > created a shortcut > >>> > > > > but when I launch, I get the same permission message. > >>> > > > > > >>> > > > > I am by default using the secured mdw: > >>> > > > > > >>> > > > > ? dbEngine.SystemDb > >>> > > > > C:\Documents and Settings\Joe\My > >>> > > > > Documents\BladeRunner\Security.mdw > >>> > > > > > >>> > > > > I am still not prompted for a password, but appear to be logged > >>> > > > > on as Admin. > >>> > > > > I cannot change the admin password, and it tells me that the old > >>> > > > > password is > >>> > > > > incorrect. I see the users that I created, but cannot change > >>> > > > > those passwords > >>> > > > > or get prompted to log in. > >>> > > > > > >>> > > > > I am sure confused and getting nervous about this...I have > >>> > > > > invested a large > >>> > > > > chunk of time in this development effort, and sure hope you can > >>> > > > > help me > >>> > > > > understand what I've done here. Thanks again for your help. > >>> > > > > > >>> > > > > Joe > >>> > > > > > >>> > > > > > >>> > > > > > >>> > > > > > >>> > > > > > >>> > > > > "Joan Wild" wrote: > >>> > > > > > >>> > > > > > "Joe G" wrote: > >>> > > > > > > >>> > > > > > > Hello Joan ! > >>> > > > > > > > >>> > > > > > > I have an MDB file that I secured a few weeks back which was > >>> > > > > > > working fine. > >>> > > > > > > I did something yesterday when I unzipped a backup copy of > >>> > > > > > > the database > >>> > > > > > > (although I unzipped it to a different directory) that has > >>> > > > > > > caused me problems. > >>> > > > > > > > >>> > > > > > > I have an MDW file of the same name as the MDB, residing in > >>> > > > > > > the same > >>> > > > > > > directory. > >>> > > > > > > >>> > > > > > That's not a good idea. Both the mdb and the mdw need to > >>> > > > > > create an > >>> > > > > > associated ldb file. They can't if they have the same name. > >>> > > > > > Rename the mdw > >>> > > > > > file (and then modify any shortcuts as necessary). > >>> > > > > > > >>> > > > > > > I join the workgroup for the MDB - which has the two users > >>> > > > > > > that I created > >>> > > > > > > when I secured the database, but when I try to open the > >>> > > > > > > database, I get the > >>> > > > > > > message about not having the necessary permission and to > >>> > > > > > > contact the system > >>> > > > > > > admin. > >>> > > > > > > >>> > > > > > Are you certain you have joined the correct mdw file? > >>> > > > > > > >>> > > > > > > I am thinking that I am logged in as the universal admin > >>> > > > > > > (since I am not > >>> > > > > > > prompted for a password) and am wondering how I go about > >>> > > > > > > trying to log in as > >>> > > > > > > the user I had created when I secured the database who has > >>> > > > > > > amin permissions. > >>> > > > > > > I am not being prompted to log in as I used to be. > >>> > > > > > > >>> > > > > > When you open Access, go to Workgroup Administrator and verify > >>> > > > > > the mdw you > >>> > > > > > are using by default. It should be the standard system.mdw > >>> > > > > > that ships with > >>> > > > > > Access. Use a desktop shortcut to launch your secure mdb. > >>> > > > > > "path to msaccess.exe" "path to mdb" /wrkgrp "path to mdw" > >>> > > > > > > >>> > > > > > When you launch via the shortcut, you should get a login > >>> > > > > > prompt. If you > >>> > > > > > don't then perhaps you've somehow cleared the password for the > >>> > > > > > 'Admin' user > >>> > > > > > or your shortcut has a problem, in which case it will use > >>> > > > > > system.mdw. In > >>> > > > > > either case hit Ctrl-G and type DbEngine.SystemDB which will > >>> > > > > > tell you the mdw > >>> > > > > > it is *using*. > >>> > > > > > > >>> > > > > > If it is your secure mdw then go to Tools, security, accounts, > >>> > > > > > password tab > >>> > > > > > - it will show you that you are logged in as Admin - set a > >>> > > > > > password for this > >>> > > > > > user. > >>> > > > > > > >>> > > > > > If it is the system.mdw then your shortcut has an error in it. > >>> > > > > > > >>> > > > > > -- > >>> > > > > > Joan Wild > >>> > > > > > Microsoft Access MVP > >>> > > > > > > > > > > > > Are you able to log in as *any* user at all?
-- Show quoteHide quoteJoan Wild Microsoft Access MVP Joe G wrote: > All, > Thank you for allowing me to hop onto this thread. I have never > before used this type of forum, and hope that I have not been out of > line. I realize now that I probably should have created a new > question rather than jump into Bruce's discussion. > > I am in a deep bind here, and need to resolve this security issue. > If anyone can point me in the right direction here, with regard to > how I might resolve this in the most expeditious way possible, I > would be most grateful. > > In all of my reading thus far, I have yet to see how to resolve this. > I have a security.mdw that for some reason is not allowing me access > to my mdb at all. > > Thanks in advance, > > Joe > > > "Lynn Trapp" wrote: > >> Bruce, >> Actually, Joe G interjected his question intoyour original thread >> and all the posts between he and Joan were not showing up yesterday. >> They are all appearing today. Some problem with the synchronization >> on the servers. >> >> -- >> >> Lynn Trapp >> Microsoft MVP (Access) >> www.ltcomputerdesigns.com >> >> >> "BruceM" <bam***@yawhodawtcalm.not> wrote in message >> news:O0tf$CMFHHA.1080@TK2MSFTNGP05.phx.gbl... >>> Joan, >>> >>> This response showed up in a different thread than the one in which >>> you intended to post it. >>> >>> "Joan Wild" <jwild@nospamtyenet.com> wrote in message >>> news:BF752029-7556-4CDA-B016-82C46C303B64@microsoft.com... >>>> You shouldn't be logging in as Admin, since that user doesn't >>>> (shouldn't) have permissions to do anything. You just wanted to >>>> set a password for this >>>> user so that the login dialog would appear. >>>> >>>> You now want to log in as the user that owns the database. >>>> >>>> Usernames/passwords/group membership are stored in the mdw. >>>> Permissions are >>>> stored in the mdb. So your various backups may have different >>>> permissions on >>>> the objects. >>>> >>>> No I am not an employee of MS. >>>> >>>> -- >>>> Joan Wild >>>> Microsoft Access MVP >>>> >>>> >>>> "Joe G" wrote: >>>> >>>>> Double checked the case sensitivity...none of the backups are >>>>> working. I >>>>> don't get the permissions tab enabled, even though I log in as >>>>> Admin. Are the user names stored in the MDB or the MDW ? All of >>>>> my backups at this >>>>> point had been using the same security MDW. I am assuming that >>>>> this MDW is >>>>> the correct one because I see users listed. Are you an employee >>>>> of Microsoft, Joan ? >>>>> I am relatively knew to MS Access. I have been developing with >>>>> PowerBuilder >>>>> for the last ten plus years. Again. Appreciate the help. >>>>> >>>>> Joe >>>>> >>>>> "Joan Wild" wrote: >>>>> >>>>>> Remember that passwords are case sensitive. >>>>>> >>>>>> Since this started when you restored a backup, perhaps that >>>>>> backup doesn't >>>>>> have the permissions set correctly. When you check the owner >>>>>> tab in the >>>>>> permissions dialog, what user is listed as owner of everything? >>>>>> >>>>>> -- >>>>>> Joan Wild >>>>>> Microsoft Access MVP >>>>>> >>>>>> >>>>>> "Joe G" wrote: >>>>>> >>>>>>> OK. Changed the password for admin, but then get the same >>>>>>> message that I >>>>>>> don't have the necessary permissions. Cannot change the >>>>>>> password for user >>>>>>> Joe, who also had admin rights when I created the secured >>>>>>> database. His >>>>>>> password is not blank nor is it what I thought it was. >>>>>>> >>>>>>> "Joan Wild" wrote: >>>>>>> >>>>>>>> OK, so you know you are using security.mdw, but you get no >>>>>>>> login. That means >>>>>>>> that the Admin password is currently blank. Go into the >>>>>>>> Accounts dialog and >>>>>>>> change password tab. Set a password for the Admin user >>>>>>>> (remember that the >>>>>>>> old password is blank). >>>>>>>> >>>>>>>> Close Access and try your shortcut again. >>>>>>>> -- >>>>>>>> Joan Wild >>>>>>>> Microsoft Access MVP >>>>>>>> >>>>>>>> >>>>>>>> "Joe G" wrote: >>>>>>>> >>>>>>>>> Joan, >>>>>>>>> I mis-stated one thing below. My MDB is BladeRunner.MDB which >>>>>>>>> is in a >>>>>>>>> directory under MyDocuments\BladeRunner. The security file is >>>>>>>>> Security.mdw >>>>>>>>> and there is a Security.ldb all in the same directory. I >>>>>>>>> created a shortcut >>>>>>>>> but when I launch, I get the same permission message. >>>>>>>>> >>>>>>>>> I am by default using the secured mdw: >>>>>>>>> >>>>>>>>> ? dbEngine.SystemDb >>>>>>>>> C:\Documents and Settings\Joe\My >>>>>>>>> Documents\BladeRunner\Security.mdw >>>>>>>>> >>>>>>>>> I am still not prompted for a password, but appear to be >>>>>>>>> logged on as Admin. >>>>>>>>> I cannot change the admin password, and it tells me that the >>>>>>>>> old password is >>>>>>>>> incorrect. I see the users that I created, but cannot change >>>>>>>>> those passwords >>>>>>>>> or get prompted to log in. >>>>>>>>> >>>>>>>>> I am sure confused and getting nervous about this...I have >>>>>>>>> invested a large >>>>>>>>> chunk of time in this development effort, and sure hope you >>>>>>>>> can help me >>>>>>>>> understand what I've done here. Thanks again for your help. >>>>>>>>> >>>>>>>>> Joe >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> "Joan Wild" wrote: >>>>>>>>> >>>>>>>>>> "Joe G" wrote: >>>>>>>>>> >>>>>>>>>>> Hello Joan ! >>>>>>>>>>> >>>>>>>>>>> I have an MDB file that I secured a few weeks back which was >>>>>>>>>>> working fine. >>>>>>>>>>> I did something yesterday when I unzipped a backup copy of >>>>>>>>>>> the database >>>>>>>>>>> (although I unzipped it to a different directory) that has >>>>>>>>>>> caused me problems. >>>>>>>>>>> >>>>>>>>>>> I have an MDW file of the same name as the MDB, residing in >>>>>>>>>>> the same >>>>>>>>>>> directory. >>>>>>>>>> >>>>>>>>>> That's not a good idea. Both the mdb and the mdw need to >>>>>>>>>> create an >>>>>>>>>> associated ldb file. They can't if they have the same name. >>>>>>>>>> Rename the mdw >>>>>>>>>> file (and then modify any shortcuts as necessary). >>>>>>>>>> >>>>>>>>>>> I join the workgroup for the MDB - which has the two users >>>>>>>>>>> that I created >>>>>>>>>>> when I secured the database, but when I try to open the >>>>>>>>>>> database, I get the >>>>>>>>>>> message about not having the necessary permission and to >>>>>>>>>>> contact the system >>>>>>>>>>> admin. >>>>>>>>>> >>>>>>>>>> Are you certain you have joined the correct mdw file? >>>>>>>>>> >>>>>>>>>>> I am thinking that I am logged in as the universal admin >>>>>>>>>>> (since I am not >>>>>>>>>>> prompted for a password) and am wondering how I go about >>>>>>>>>>> trying to log in as >>>>>>>>>>> the user I had created when I secured the database who has >>>>>>>>>>> amin permissions. >>>>>>>>>>> I am not being prompted to log in as I used to be. >>>>>>>>>> >>>>>>>>>> When you open Access, go to Workgroup Administrator and >>>>>>>>>> verify the mdw you >>>>>>>>>> are using by default. It should be the standard system.mdw >>>>>>>>>> that ships with >>>>>>>>>> Access. Use a desktop shortcut to launch your secure mdb. >>>>>>>>>> "path to msaccess.exe" "path to mdb" /wrkgrp "path to mdw" >>>>>>>>>> >>>>>>>>>> When you launch via the shortcut, you should get a login >>>>>>>>>> prompt. If you >>>>>>>>>> don't then perhaps you've somehow cleared the password for >>>>>>>>>> the 'Admin' user >>>>>>>>>> or your shortcut has a problem, in which case it will use >>>>>>>>>> system.mdw. In >>>>>>>>>> either case hit Ctrl-G and type DbEngine.SystemDB which will >>>>>>>>>> tell you the mdw >>>>>>>>>> it is *using*. >>>>>>>>>> >>>>>>>>>> If it is your secure mdw then go to Tools, security, >>>>>>>>>> accounts, password tab >>>>>>>>>> - it will show you that you are logged in as Admin - set a >>>>>>>>>> password for this >>>>>>>>>> user. >>>>>>>>>> >>>>>>>>>> If it is the system.mdw then your shortcut has an error in >>>>>>>>>> it. >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Joan Wild >>>>>>>>>> Microsoft Access MVP Thanks all...I was just able to get back in. Appreciate the help.
Joe Show quoteHide quote "Joe G" wrote: > All, > Thank you for allowing me to hop onto this thread. I have never before used > this type of forum, and hope that I have not been out of line. I realize now > that I probably should have created a new question rather than jump into > Bruce's discussion. > > I am in a deep bind here, and need to resolve this security issue. > If anyone can point me in the right direction here, with regard to how I > might resolve this in the most expeditious way possible, I would be most > grateful. > > In all of my reading thus far, I have yet to see how to resolve this. I > have a security.mdw that for some reason is not allowing me access to my mdb > at all. > > Thanks in advance, > > Joe > > > "Lynn Trapp" wrote: > > > Bruce, > > Actually, Joe G interjected his question intoyour original thread and all > > the posts between he and Joan were not showing up yesterday. They are all > > appearing today. Some problem with the synchronization on the servers. > > > > -- > > > > Lynn Trapp > > Microsoft MVP (Access) > > www.ltcomputerdesigns.com > > > > > > "BruceM" <bam***@yawhodawtcalm.not> wrote in message > > news:O0tf$CMFHHA.1080@TK2MSFTNGP05.phx.gbl... > > > Joan, > > > > > > This response showed up in a different thread than the one in which you > > > intended to post it. > > > > > > "Joan Wild" <jwild@nospamtyenet.com> wrote in message > > > news:BF752029-7556-4CDA-B016-82C46C303B64@microsoft.com... > > >> You shouldn't be logging in as Admin, since that user doesn't (shouldn't) > > >> have permissions to do anything. You just wanted to set a password for > > >> this > > >> user so that the login dialog would appear. > > >> > > >> You now want to log in as the user that owns the database. > > >> > > >> Usernames/passwords/group membership are stored in the mdw. Permissions > > >> are > > >> stored in the mdb. So your various backups may have different > > >> permissions on > > >> the objects. > > >> > > >> No I am not an employee of MS. > > >> > > >> -- > > >> Joan Wild > > >> Microsoft Access MVP > > >> > > >> > > >> "Joe G" wrote: > > >> > > >>> Double checked the case sensitivity...none of the backups are working. > > >>> I > > >>> don't get the permissions tab enabled, even though I log in as Admin. > > >>> Are the user names stored in the MDB or the MDW ? All of my backups at > > >>> this > > >>> point had been using the same security MDW. I am assuming that this MDW > > >>> is > > >>> the correct one because I see users listed. Are you an employee of > > >>> Microsoft, Joan ? > > >>> I am relatively knew to MS Access. I have been developing with > > >>> PowerBuilder > > >>> for the last ten plus years. Again. Appreciate the help. > > >>> > > >>> Joe > > >>> > > >>> "Joan Wild" wrote: > > >>> > > >>> > Remember that passwords are case sensitive. > > >>> > > > >>> > Since this started when you restored a backup, perhaps that backup > > >>> > doesn't > > >>> > have the permissions set correctly. When you check the owner tab in > > >>> > the > > >>> > permissions dialog, what user is listed as owner of everything? > > >>> > > > >>> > -- > > >>> > Joan Wild > > >>> > Microsoft Access MVP > > >>> > > > >>> > > > >>> > "Joe G" wrote: > > >>> > > > >>> > > OK. Changed the password for admin, but then get the same message > > >>> > > that I > > >>> > > don't have the necessary permissions. Cannot change the password > > >>> > > for user > > >>> > > Joe, who also had admin rights when I created the secured database. > > >>> > > His > > >>> > > password is not blank nor is it what I thought it was. > > >>> > > > > >>> > > "Joan Wild" wrote: > > >>> > > > > >>> > > > OK, so you know you are using security.mdw, but you get no login. > > >>> > > > That means > > >>> > > > that the Admin password is currently blank. Go into the Accounts > > >>> > > > dialog and > > >>> > > > change password tab. Set a password for the Admin user (remember > > >>> > > > that the > > >>> > > > old password is blank). > > >>> > > > > > >>> > > > Close Access and try your shortcut again. > > >>> > > > -- > > >>> > > > Joan Wild > > >>> > > > Microsoft Access MVP > > >>> > > > > > >>> > > > > > >>> > > > "Joe G" wrote: > > >>> > > > > > >>> > > > > Joan, > > >>> > > > > I mis-stated one thing below. My MDB is BladeRunner.MDB which > > >>> > > > > is in a > > >>> > > > > directory under MyDocuments\BladeRunner. The security file is > > >>> > > > > Security.mdw > > >>> > > > > and there is a Security.ldb all in the same directory. I > > >>> > > > > created a shortcut > > >>> > > > > but when I launch, I get the same permission message. > > >>> > > > > > > >>> > > > > I am by default using the secured mdw: > > >>> > > > > > > >>> > > > > ? dbEngine.SystemDb > > >>> > > > > C:\Documents and Settings\Joe\My > > >>> > > > > Documents\BladeRunner\Security.mdw > > >>> > > > > > > >>> > > > > I am still not prompted for a password, but appear to be logged > > >>> > > > > on as Admin. > > >>> > > > > I cannot change the admin password, and it tells me that the old > > >>> > > > > password is > > >>> > > > > incorrect. I see the users that I created, but cannot change > > >>> > > > > those passwords > > >>> > > > > or get prompted to log in. > > >>> > > > > > > >>> > > > > I am sure confused and getting nervous about this...I have > > >>> > > > > invested a large > > >>> > > > > chunk of time in this development effort, and sure hope you can > > >>> > > > > help me > > >>> > > > > understand what I've done here. Thanks again for your help. > > >>> > > > > > > >>> > > > > Joe > > >>> > > > > > > >>> > > > > > > >>> > > > > > > >>> > > > > > > >>> > > > > > > >>> > > > > "Joan Wild" wrote: > > >>> > > > > > > >>> > > > > > "Joe G" wrote: > > >>> > > > > > > > >>> > > > > > > Hello Joan ! > > >>> > > > > > > > > >>> > > > > > > I have an MDB file that I secured a few weeks back which was > > >>> > > > > > > working fine. > > >>> > > > > > > I did something yesterday when I unzipped a backup copy of > > >>> > > > > > > the database > > >>> > > > > > > (although I unzipped it to a different directory) that has > > >>> > > > > > > caused me problems. > > >>> > > > > > > > > >>> > > > > > > I have an MDW file of the same name as the MDB, residing in > > >>> > > > > > > the same > > >>> > > > > > > directory. > > >>> > > > > > > > >>> > > > > > That's not a good idea. Both the mdb and the mdw need to > > >>> > > > > > create an > > >>> > > > > > associated ldb file. They can't if they have the same name. > > >>> > > > > > Rename the mdw > > >>> > > > > > file (and then modify any shortcuts as necessary). > > >>> > > > > > > > >>> > > > > > > I join the workgroup for the MDB - which has the two users > > >>> > > > > > > that I created > > >>> > > > > > > when I secured the database, but when I try to open the > > >>> > > > > > > database, I get the > > >>> > > > > > > message about not having the necessary permission and to > > >>> > > > > > > contact the system > > >>> > > > > > > admin. > > >>> > > > > > > > >>> > > > > > Are you certain you have joined the correct mdw file? > > >>> > > > > > > > >>> > > > > > > I am thinking that I am logged in as the universal admin > > >>> > > > > > > (since I am not > > >>> > > > > > > prompted for a password) and am wondering how I go about > > >>> > > > > > > trying to log in as > > >>> > > > > > > the user I had created when I secured the database who has > > >>> > > > > > > amin permissions. > > >>> > > > > > > I am not being prompted to log in as I used to be. > > >>> > > > > > > > >>> > > > > > When you open Access, go to Workgroup Administrator and verify > > >>> > > > > > the mdw you > > >>> > > > > > are using by default. It should be the standard system.mdw > > >>> > > > > > that ships with > > >>> > > > > > Access. Use a desktop shortcut to launch your secure mdb. > > >>> > > > > > "path to msaccess.exe" "path to mdb" /wrkgrp "path to mdw" > > >>> > > > > > > > >>> > > > > > When you launch via the shortcut, you should get a login > > >>> > > > > > prompt. If you > > >>> > > > > > don't then perhaps you've somehow cleared the password for the > > >>> > > > > > 'Admin' user > > >>> > > > > > or your shortcut has a problem, in which case it will use > > >>> > > > > > system.mdw. In > > >>> > > > > > either case hit Ctrl-G and type DbEngine.SystemDB which will > > >>> > > > > > tell you the mdw > > >>> > > > > > it is *using*. > > >>> > > > > > > > >>> > > > > > If it is your secure mdw then go to Tools, security, accounts, > > >>> > > > > > password tab > > >>> > > > > > - it will show you that you are logged in as Admin - set a > > >>> > > > > > password for this > > >>> > > > > > user. > > >>> > > > > > > > >>> > > > > > If it is the system.mdw then your shortcut has an error in it. > > >>> > > > > > > > >>> > > > > > -- > > >>> > > > > > Joan Wild > > >>> > > > > > Microsoft Access MVP > > >>> > > > > > > > > > > > > > > > > > After all that, couldn't you tell us how you resolved it?
-- Show quoteHide quoteJoan Wild Microsoft Access MVP Joe G wrote: > Thanks all...I was just able to get back in. Appreciate the help. > Joe > Yes..the reason for not being forthcoming just now was that I am embarrassed
to say that I had changed the password for the user who owned everything. When the admin account kept coming up with the permission error message, I started to lose hope. Then when I tried logging in as a user, I was able to get in, which then led me to try some passwords on the owner account. I'm not sure I understand why the admin user can no longer get into the database, but as long as Joe can, then I'm good to go on. This is my first access application and I am glad to know that people like you are there for goofy people like myself. Thanks again. Show quoteHide quote "Joan Wild" wrote: > After all that, couldn't you tell us how you resolved it? > > -- > Joan Wild > Microsoft Access MVP > > Joe G wrote: > > Thanks all...I was just able to get back in. Appreciate the help. > > Joe > > > > > The Admin user should not have any permissions on the database at all. The
Admin user is common to all mdw files, including system.mdw that ships with Access. If that user had permission, then anyone with Access using the standard system.mdw would have permissions. The Users Group and the Admin user are common to all mdw files. The Admins Group is not. Hope that helps (and don't be embarrassed) -- Show quoteHide quoteJoan Wild Microsoft Access MVP Joe G wrote: > Yes..the reason for not being forthcoming just now was that I am > embarrassed to say that I had changed the password for the user who > owned everything. > > When the admin account kept coming up with the permission error > message, I started to lose hope. Then when I tried logging in as a > user, I was able to get in, which then led me to try some passwords > on the owner account. > > I'm not sure I understand why the admin user can no longer get into > the database, but as long as Joe can, then I'm good to go on. This > is my first access application and I am glad to know that people like > you are there for goofy people like myself. > > Thanks again. > > > "Joan Wild" wrote: > >> After all that, couldn't you tell us how you resolved it? >> >> -- >> Joan Wild >> Microsoft Access MVP >> >> Joe G wrote: >>> Thanks all...I was just able to get back in. Appreciate the help. >>> Joe There's nothing wrong with joining an existing thread, especially if you
have questions or comments about a specific point in the thread, but your question is more likely to be seen by many eyes if it is its own thread. In this thread your question was seen for sure by Joan Wild and Lynn Trapp. When either or both of them see your question there is an excellent chance that you will receive sound and insightful advice, but unless your topic is very closely related to the topic in the existing thread you increase your chances by starting a new thread. Show quoteHide quote "Joe G" <J***@discussions.microsoft.com> wrote in message news:01493281-5B22-4B6A-9914-2E43371D9FBF@microsoft.com... > All, > Thank you for allowing me to hop onto this thread. I have never before > used > this type of forum, and hope that I have not been out of line. I realize > now > that I probably should have created a new question rather than jump into > Bruce's discussion. > > I am in a deep bind here, and need to resolve this security issue. > If anyone can point me in the right direction here, with regard to how I > might resolve this in the most expeditious way possible, I would be most > grateful. > > In all of my reading thus far, I have yet to see how to resolve this. I > have a security.mdw that for some reason is not allowing me access to my > mdb > at all. > > Thanks in advance, > > Joe > > > "Lynn Trapp" wrote: > >> Bruce, >> Actually, Joe G interjected his question intoyour original thread and all >> the posts between he and Joan were not showing up yesterday. They are all >> appearing today. Some problem with the synchronization on the servers. >> >> -- >> >> Lynn Trapp >> Microsoft MVP (Access) >> www.ltcomputerdesigns.com >> >> >> "BruceM" <bam***@yawhodawtcalm.not> wrote in message >> news:O0tf$CMFHHA.1080@TK2MSFTNGP05.phx.gbl... >> > Joan, >> > >> > This response showed up in a different thread than the one in which you >> > intended to post it. >> > >> > "Joan Wild" <jwild@nospamtyenet.com> wrote in message >> > news:BF752029-7556-4CDA-B016-82C46C303B64@microsoft.com... >> >> You shouldn't be logging in as Admin, since that user doesn't >> >> (shouldn't) >> >> have permissions to do anything. You just wanted to set a password >> >> for >> >> this >> >> user so that the login dialog would appear. >> >> >> >> You now want to log in as the user that owns the database. >> >> >> >> Usernames/passwords/group membership are stored in the mdw. >> >> Permissions >> >> are >> >> stored in the mdb. So your various backups may have different >> >> permissions on >> >> the objects. >> >> >> >> No I am not an employee of MS. >> >> >> >> -- >> >> Joan Wild >> >> Microsoft Access MVP >> >> >> >> >> >> "Joe G" wrote: >> >> >> >>> Double checked the case sensitivity...none of the backups are >> >>> working. >> >>> I >> >>> don't get the permissions tab enabled, even though I log in as Admin. >> >>> Are the user names stored in the MDB or the MDW ? All of my backups >> >>> at >> >>> this >> >>> point had been using the same security MDW. I am assuming that this >> >>> MDW >> >>> is >> >>> the correct one because I see users listed. Are you an employee of >> >>> Microsoft, Joan ? >> >>> I am relatively knew to MS Access. I have been developing with >> >>> PowerBuilder >> >>> for the last ten plus years. Again. Appreciate the help. >> >>> >> >>> Joe >> >>> >> >>> "Joan Wild" wrote: >> >>> >> >>> > Remember that passwords are case sensitive. >> >>> > >> >>> > Since this started when you restored a backup, perhaps that backup >> >>> > doesn't >> >>> > have the permissions set correctly. When you check the owner tab >> >>> > in >> >>> > the >> >>> > permissions dialog, what user is listed as owner of everything? >> >>> > >> >>> > -- >> >>> > Joan Wild >> >>> > Microsoft Access MVP >> >>> > >> >>> > >> >>> > "Joe G" wrote: >> >>> > >> >>> > > OK. Changed the password for admin, but then get the same >> >>> > > message >> >>> > > that I >> >>> > > don't have the necessary permissions. Cannot change the password >> >>> > > for user >> >>> > > Joe, who also had admin rights when I created the secured >> >>> > > database. >> >>> > > His >> >>> > > password is not blank nor is it what I thought it was. >> >>> > > >> >>> > > "Joan Wild" wrote: >> >>> > > >> >>> > > > OK, so you know you are using security.mdw, but you get no >> >>> > > > login. >> >>> > > > That means >> >>> > > > that the Admin password is currently blank. Go into the >> >>> > > > Accounts >> >>> > > > dialog and >> >>> > > > change password tab. Set a password for the Admin user >> >>> > > > (remember >> >>> > > > that the >> >>> > > > old password is blank). >> >>> > > > >> >>> > > > Close Access and try your shortcut again. >> >>> > > > -- >> >>> > > > Joan Wild >> >>> > > > Microsoft Access MVP >> >>> > > > >> >>> > > > >> >>> > > > "Joe G" wrote: >> >>> > > > >> >>> > > > > Joan, >> >>> > > > > I mis-stated one thing below. My MDB is BladeRunner.MDB >> >>> > > > > which >> >>> > > > > is in a >> >>> > > > > directory under MyDocuments\BladeRunner. The security file >> >>> > > > > is >> >>> > > > > Security.mdw >> >>> > > > > and there is a Security.ldb all in the same directory. I >> >>> > > > > created a shortcut >> >>> > > > > but when I launch, I get the same permission message. >> >>> > > > > >> >>> > > > > I am by default using the secured mdw: >> >>> > > > > >> >>> > > > > ? dbEngine.SystemDb >> >>> > > > > C:\Documents and Settings\Joe\My >> >>> > > > > Documents\BladeRunner\Security.mdw >> >>> > > > > >> >>> > > > > I am still not prompted for a password, but appear to be >> >>> > > > > logged >> >>> > > > > on as Admin. >> >>> > > > > I cannot change the admin password, and it tells me that the >> >>> > > > > old >> >>> > > > > password is >> >>> > > > > incorrect. I see the users that I created, but cannot change >> >>> > > > > those passwords >> >>> > > > > or get prompted to log in. >> >>> > > > > >> >>> > > > > I am sure confused and getting nervous about this...I have >> >>> > > > > invested a large >> >>> > > > > chunk of time in this development effort, and sure hope you >> >>> > > > > can >> >>> > > > > help me >> >>> > > > > understand what I've done here. Thanks again for your help. >> >>> > > > > >> >>> > > > > Joe >> >>> > > > > >> >>> > > > > >> >>> > > > > >> >>> > > > > >> >>> > > > > >> >>> > > > > "Joan Wild" wrote: >> >>> > > > > >> >>> > > > > > "Joe G" wrote: >> >>> > > > > > >> >>> > > > > > > Hello Joan ! >> >>> > > > > > > >> >>> > > > > > > I have an MDB file that I secured a few weeks back which >> >>> > > > > > > was >> >>> > > > > > > working fine. >> >>> > > > > > > I did something yesterday when I unzipped a backup copy >> >>> > > > > > > of >> >>> > > > > > > the database >> >>> > > > > > > (although I unzipped it to a different directory) that >> >>> > > > > > > has >> >>> > > > > > > caused me problems. >> >>> > > > > > > >> >>> > > > > > > I have an MDW file of the same name as the MDB, residing >> >>> > > > > > > in >> >>> > > > > > > the same >> >>> > > > > > > directory. >> >>> > > > > > >> >>> > > > > > That's not a good idea. Both the mdb and the mdw need to >> >>> > > > > > create an >> >>> > > > > > associated ldb file. They can't if they have the same >> >>> > > > > > name. >> >>> > > > > > Rename the mdw >> >>> > > > > > file (and then modify any shortcuts as necessary). >> >>> > > > > > >> >>> > > > > > > I join the workgroup for the MDB - which has the two >> >>> > > > > > > users >> >>> > > > > > > that I created >> >>> > > > > > > when I secured the database, but when I try to open the >> >>> > > > > > > database, I get the >> >>> > > > > > > message about not having the necessary permission and to >> >>> > > > > > > contact the system >> >>> > > > > > > admin. >> >>> > > > > > >> >>> > > > > > Are you certain you have joined the correct mdw file? >> >>> > > > > > >> >>> > > > > > > I am thinking that I am logged in as the universal admin >> >>> > > > > > > (since I am not >> >>> > > > > > > prompted for a password) and am wondering how I go about >> >>> > > > > > > trying to log in as >> >>> > > > > > > the user I had created when I secured the database who >> >>> > > > > > > has >> >>> > > > > > > amin permissions. >> >>> > > > > > > I am not being prompted to log in as I used to be. >> >>> > > > > > >> >>> > > > > > When you open Access, go to Workgroup Administrator and >> >>> > > > > > verify >> >>> > > > > > the mdw you >> >>> > > > > > are using by default. It should be the standard system.mdw >> >>> > > > > > that ships with >> >>> > > > > > Access. Use a desktop shortcut to launch your secure mdb. >> >>> > > > > > "path to msaccess.exe" "path to mdb" /wrkgrp "path to mdw" >> >>> > > > > > >> >>> > > > > > When you launch via the shortcut, you should get a login >> >>> > > > > > prompt. If you >> >>> > > > > > don't then perhaps you've somehow cleared the password for >> >>> > > > > > the >> >>> > > > > > 'Admin' user >> >>> > > > > > or your shortcut has a problem, in which case it will use >> >>> > > > > > system.mdw. In >> >>> > > > > > either case hit Ctrl-G and type DbEngine.SystemDB which >> >>> > > > > > will >> >>> > > > > > tell you the mdw >> >>> > > > > > it is *using*. >> >>> > > > > > >> >>> > > > > > If it is your secure mdw then go to Tools, security, >> >>> > > > > > accounts, >> >>> > > > > > password tab >> >>> > > > > > - it will show you that you are logged in as Admin - set a >> >>> > > > > > password for this >> >>> > > > > > user. >> >>> > > > > > >> >>> > > > > > If it is the system.mdw then your shortcut has an error in >> >>> > > > > > it. >> >>> > > > > > >> >>> > > > > > -- >> >>> > > > > > Joan Wild >> >>> > > > > > Microsoft Access MVP >> >>> > > > > > >> > >> > >> >> >> 
Other interesting topics
Getting started with security
Frontend Downloads Interesting "Locked In" Problem 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.... Cannot unclick users from group in Security Wizard |
|||||||||||||||||||||||
