2020. 1. 23. 06:08ㆍ카테고리 없음
Step 2: Bypass MDB/ACCDB password. Start your Microsoft Access app. Click on Open Other Files, and then click Open - Browse. Tips: If in Access 2010 or the older Access versions, just select File tab and click Open. In the Open dialog box, browsing for the encrypted.mdb or.accdb file and select it. On Wed, 15 Oct 2008 20:02:34 -0700, Salad.
I have setup a workgroup for a specific database that I have created. The permissions work great for each user but for some reason if the user uses the system.mdw file it will surpass all security for that database file and the user will be allowed full access. I understand that the admin password needed to be changed in order for this not to happen and i even assigned the admin user to not have any permissions to the database (not even be able to open it). Still the user can get in the database.
The weird thing is that on 2 of my computer the system.mdw is located in C:Program FilesCommon FilesSYSTEM and it will surpass all security. On other computers the system.mdw file is located C:WindowsSystem system.mdw and when you try and open the database with using this workgroup it will say do not have permissions to view database.
Some computers have two system.mdw files one in C:WindowsSystem (this file wont pass security) and one file in C:Program FilesMicrosoft OfficeOfficeSystem.mdw (this one will pass security). So my question is why is it doing that. If anyone who isn't in my workgroup happens to be by default assigned to this workgroup they can get in my database. But since there are two mdws how do i know if the security is working please help. Cuz this is making me frustrated!
RE: Super.mdw file surpasses all security (Programmer) 13 Feb 01 12:48. Michael, I have used Access security many times, but I never ran across a problem related to the name of the workgroup file. Rather, I've had this problem because the person setting up security started with a copy of the System.mdw as installed with Access, rather than creating a new workgroup file with a unique Workgroup ID. It winds up having the same Security ID as the default workgroup then. So when a user using an unmodified default system.mdw logs on, the database accepts the SID, and the default Users group has all permissions.Are you sure there's an issue with just having the name 'system.mdw'? Can you point me to any documentation on this?Rick Sprague RE: Super.mdw file surpasses all security (MIS) 13 Feb 01 22:40.
Rick,I cannot recall exactly where I ran across this info. I do rember the rationale. If the security database (.MDW) has the default name ('system.Mdw'), then reference to any System.MDW is an appropiate refernce to the security database. Access looks for the security database and uses whatever info it finds, a sefault system.MDW would appear to allow all users to hace all permissions for all objects. Efectively resulting in an 'unsecured' database.
I am pretty sure I have actually encountered this at a previous job. A user received an upgrade machine, and had default software installations. I had set the secutity file to system.mdw - on a server - however the installation of access switched the reference to the local defalut system.mdw and the user suddenly had all access rights to all objects. Thankfully, the user was quite suprised by this and asked why he suddenly had the capability to do things in the app which he knew were not part of his normal duties. Still took me a while to find the answer and 'fix' the problem.It is possible that I am doing more than necessary in this, but I have always used a different name for the security file since that job.MichaelRedThere is never time to do it right but there is always time to do it over RE: Super.mdw file surpasses all security Guest (visitor) 14 Feb 01 09:47. The name of our security file is not system.mdw we created a new one and titled it security.mdw so i don't think thats the problem. Plus like I said one system.mdw will give full access while the other system.mdw won't.
I never created a file named system.mdw. The default one will work when its in C:Program FilesCommon Files but will not work when it is in C:WindowsSystem. I have one computer that actually has two system.mdw's on it. I never modified it or added a system.mdw to this computer either.
One of the system.mdw gives full access. While the other with the exact same name (although in a different location) dosent give any access to the file. It is wierd b/c they are both system.mdw's and only one will pass through security.
They should be part of a different workgroup called security.mdw that is on the network. If they are a part of this workgroup the security works.
But how can i tell if a new user will automatically be allowed full access when a default system.mdw works in one location and not the other. Please Help!!! I don't understand and i have read numerous books. RE: Super.mdw file surpasses all security (MIS) 14 Feb 01 13:28.
Access Mdb File
I tested the theory with a properly secured database and an associated workgroup that I renamed to system.mdw. I was not given access.
Michael, I strongly suspect that your experience, and that reported in what you read, was a result not of the file name but of the fact that the workgroup file either started out as a copy of the default system.mdw, or was created with the same Workgroup ID and Organization name as the default system.mdw. This is known to leave the very hole that Acquisitive One is experiencing. The common naming was coincidental and not essential.Acquisitive One: The easiest way to fix the problem will be to start with a backup copy of your unsecured database and use the Access User-Level Security Wizard. Follow the instructions very carefully. (The Access 2000 wizard is much more bulletproof; Access 97's wizard will let you screw yourself.)If that's entirely impractical, say so and I'll give you a procedure to do it manually. But it's very tricky, and has to be done exactly right, so use the wizard if you can.Rick Sprague RE: Super.mdw file surpasses all security (Programmer) 15 Feb 01 15:19.
The thread is already big so I try to make it short:1. ACCESS security is 99% safe if it is properly set up.2. The name of the MDW has no importance at all3. You need a new admin GROUP4. Delete all rights from the standard admin and users (both users AND group).5.
If you deliver a MDW containing a 'real' admin then remember that hack programs for 50$ can read usernames and passwords from the MDW. Use the 'double MDW system' to add the missing 1% to the 99%.6. Always lock the maintenance admin (relinking, user administration.) into a 'Prison form'.7. NT security is not applicable on database objects inside the MDB/MDE files.RE: Super.mdw file surpasses all security (Programmer) 30 May 01 11:57. 'Double MDW system':Developer-MDW: Contains all users including Developer (no restrictions)User-MDW: contains all users without Developer but with LimitedAdmin (who will be locked in frmPrison like described before).2. FrmPrison:OnClose: Application.quitPopup/Modal: stays always on topBlock the minimize buttonTest intensively if it is REALLY safe3.The reference book for both techniques (plus a couple of others) is situated between my ears.Happy programming!Francescina RE: Super.mdw file surpasses all security (Programmer) 17 Aug 01 22:01. I'm about a meg and a half behind you guys.
I can't even get into a file I've been given full access to. There's something fundamental I dont understand.Back in Access97 days I used wgadmin to join workgroups but now I'm on W2k and it won't even give me the time of day!Another user, a member of the AES workgroup on a NT system applied security to an Access database and gave me admin rights.
I joined the AES workgroup but when I call up the database I get 'You do not have necessary permissions.' I don't even get to enter my username/password. I think there's something REALLY BASIC I'm missing. RE: Super.mdw file surpasses all security (Programmer) 18 Aug 01 08:01. Off the top (and it is a LOW top), I can only suggest that the workgroup file is not accessible to you (path not in an area you can access) when yyou attempt to log on. Since you were able to 'join' the workgroup, this appears to be not the problem.AFAIK, the workgroup administration has not changed between '97 and 2K. If you are not even given the prompt, it MIGHT be that you have the workgroup specified in a desktop shortcut -AND- it is specified incorrectly?MichaelRedThere is never time to do it right but there is always time to do it over RE: Super.mdw file surpasses all security (TechnicalUser) 28 Jun 02 13:28.
Hi All, I am having a heck of a time getting this security to work, The thing is I can implement the user-level security sucessfully on my pc, but those who are on the network can go righttot he server into the application and start it, bypassing the password logon box. I have read numerous things and have went step, by step with the instructions on this site as well as others, if you have any information on how I can get the securities to work outside of my pc and on other machines on the network, PLEASE PLEASE PLEASE HELP!!!!!!!! RE: Super.mdw file surpasses all security (Programmer) 9 Aug 02 10:23. AcquisitiveOne - Just a thought. I have never had any problems with security, so I have never had to go very deep other into it other than using setting up the permissions. But, have you ever upgraded your systems from one version of Access to another?
Perhaps one of these.mdw files is for a prior version of Access - again, just a shot in the dark.Francescina - Great input on the security. It sounds like you have had a good deal of experience with it. Would you consider writing an FAQ detailing some the items you have mentioned here. I am sure it would be greatly appreciated.Jay RE: Super.mdw file surpasses all security Guest (visitor) 19 Aug 02 07:37. Hi all,I have just read all the messages in this post and i think you have all lost the context of the original question that was asked. I have exactly the same problem. The database security features work fine on a single pc that the database was created on.
I have put the database and the security file onto a network for a small amount of ppl to access. I placed an icon(shortcut as previously outlined) on each of the pc's i wanted to have access and thought everything was fine until oneday the person beside me in the office accessed the database without any user/password promt. This frightened the liven daylights out of me as the database contained sensitive information.I have now researched this problem and havnt found a solution. RE: Super.mdw file surpasses all security. FireViking,You're right about the thread getting WAY off topic.What's going on in your situation is that you haven't fully secured the database.
I promise you that it is NOT possible to get into a properly secured mdb without being attached to the MDW with which it was created.Get the Access Security FAQ (I've got a copy on my website), and read it many, many times. The instructions there for locking down a database may be confusing, but they are accurate.JeremyJeremy WallaceDesigning, Developing, and Deploying Access Databases Since 1995Take a look at the Developers' section of the site for some helpful fundamentals. RE: Super.mdw file surpasses all security (Programmer) 11 Dec 02 02:28.
FireViking,Glad to have helped, and that you've gotten your problem sorted.The reason it works one way and not the other is that the workgroup with which a database is created will always have a way to get into the database, and the default workgroup can always be recreated by Access, whether or not you've secured one copy of that workgroup.Enjoy the holidays.JeremyJeremy WallaceDesigning, Developing, and Deploying Access Databases Since 1995Take a look at the Developers' section of the site for some helpful fundamentals. RE: Super.mdw file surpasses all security (Programmer) 13 Jan 03 03:08. Hi all,Well well!! I cannot beleive this but the security has failed again.
It was all working fine, the database was placed on a network and only those with access and permissions could open it. I tested it on a number of occassions and from different computers and I thought it was a winner. Went on holidays and got a call from a work colleague informing me that the security had failed, everyone now had access, for some reason the database was reverting back to the default system.mdw. I had changed the.mdw to a specific name and this is now not recognised by the database.This is the second time this has happened and cant afford to bother with it anymore. I will write my own security module and use that instead. At least I know that will work.I do remember seeing a while ago now some code that could give permissions to control access. Can someone point me in the right direction please.Thank you all for your input.
RE: Super.mdw file surpasses all security (Programmer) 13 Jan 03 08:06. Fireviking,There is only one possible explanation for this behaviour:You did not delete all rights from the standard user and admin (both users AND groups) and replaced them with custom admin and users.This is why as soon as any standard MDW is used (containing the standard admin and user that have all rights) your application is no longer protected.P.S.:Developing your own security-system will not only be extremely time-consuming but can not be more secure than the standard security-system. RE: Super.mdw file surpasses all security (Programmer) 14 Jan 03 03:20. Hi all,Your suggestion Fran made me take a closer look at the FAQ and follow process more precisely. I realised that I didnt follow the last point of creating a new database and importing all tables etc to remove the open/run properties. I think the most important point is to remove all permissions from the users group and create a new specific group with assigned permissions.This seems to have fixed my problem for now.I am indebted to you. RE: Super.mdw file surpasses all security (Programmer) 14 Jan 03 12:00.
JeremyNYC,Why is it necessary to trap the user to your mdw file? The way I have done security is to:1) Create my own mdw file.2) Remove the 'admin' user from the 'admins' group.3) Create a 'myadmin' user with all rights set at the user level.4) Remove all rights from the 'admins' group and the 'users' group.5) Enable on the 'users' group only the permissions I want everybody to have.In my understanding, this allows my end-users to use whatever mdw file they want, and still be limited to the permissions I selected for the 'users' group. Am I misunderstanding something about Access security?Sleep is for people with no caffeine. RE: Super.mdw file surpasses all security (Programmer) 14 Jan 03 12:34. Never thought about that approach. Does that mean that I could build an mdw and start assigning permissions on my own?
That wouldn't be a good thing. Does it mean that users don't have to log in? Depending on what your database does that could be OK or it could be a big risk. In any case, if you can use any mdw, it's a lower level of security than having to use a specific mdw, which contains user and group accounts designed specifically for the database.JeremyJeremy WallaceAlphaBet City DataworksTake a look at the Developers' section of the site for some helpful fundamentals. RE: Super.mdw file surpasses all security (Programmer) 14 Jan 03 13:24. Jeremy,Actually, they can build an mdw, but can't assign permissions. This is because their administrator rights have been disabled on everything in the database.
I currently don't use the user login (although I might soon, so I may have to re-think this). I believe that by letting the user use any mdw, it is more secure than giving them an mdw with a user with full admin rights. As it was mentioned above, an mdw can be cracked by malicious trolls. The two mdw system mentioned above would protect against this, though.My main reason for allowing users to use their own mdw's is that they aren't forced to use a shortcut I provide. In my circumstances, this actually reduces my workload by decreasing the tech support calls I get. If users get denied access to the database because they are trying to open the database from within access or by double-clicking the icon, then I will have an angry (and often unreasonable) customer tying up my valuable development time. Do you have issues with this, or have you found a way to deal with it?Sleep is for people with no caffeine.
RE: Super.mdw file surpasses all security (Programmer) 14 Jan 03 14:12. KG,I've never had a single tech-support call about a user not being able to get into my databases, unless it's been a lost password or the network was down.I don't see how a system in which anyone can get into your database can be considred secure. Certainly the two mdw approach makes the most sense, if you're actually concerned with security.Of course, if you're (the general you, that is) truly concerned about security, Access is not the product for you.JeremyJeremy WallaceAlphaBet City DataworksTake a look at the Developers' section of the site for some helpful fundamentals. RE: Super.mdw file surpasses all security (Programmer) 14 Jan 03 14:23.
Jeremy,I guess the issue is that I'm viewing Security not as keeping people out of the database, but instead as a way to limit access to the methods I choose (i.e. Not allowing direct editing of tables, etc.).Now that I'm looking at how to limit who has access, I see that your approach makes sense.
How do you allow them to create new users and set their permissions without allowing them to get into protected areas of the program?Sleep is for people with no caffeine. RE: Super.mdw file surpasses all security (Programmer) 14 Jan 03 15:47. KG,Here's some code I use.
I must have gotten some of it from somewhere, but I don't have a note about where. That probably means it came from MS. I have tweaked it some, but it should work in 97 and later versions.JeremyPublic Function ChangePassword(sOldPwd As String, sPwd1 As String, sPwd2 As String)'(c)Copyright 2/6/01 Jeremy WallaceOn Error GoTo ErrorDim wsp As WorkspaceDim uUser As UserSet wsp = DBEngine.Workspaces(0)Set uUser = wsp.Users(CurrentUser)If sPwd1 = sPwd2 ThenuUser.NewPassword sOldPwd, sPwd1DoCmd.CloseForms!frmswitchboard.Visible = TrueElseMsgBox 'The passwords did not match. Please try again.'
, vbOKOnly + vbInformation, 'Data Conflict'End IfExit FunctionError:Select Case Err.NumberCase 3033 'wrong current passwordCase ElseErrorTrap Err.Number, Err.Description, 'ChangePassword'End SelectEnd FunctionPublic Function DeleteUser(ByVal sUserName As String) As Boolean'(c)Copyright 2/6/01 Jeremy WallaceOn Error GoTo ErrorDim ws As WorkspaceSet ws = DBEngine.Workspaces(0)ws.Users.Delete sUserNamews.Users.RefreshExit FunctionError:Select Case Err.NumberCase 3265 'no such userMsgBox 'This user is not present in the Workgroup file.' Exit FunctionCase ElseErrorTrap Err.Number, Err.Description, 'DeleteUser'End SelectEnd FunctionPublic Function CreateUser(ByVal sUserName As String) As BooleanDim ws As WorkspaceDim usr As UserDim grpUsers As GroupDim sSql As StringDim sPID As StringDim sPWD As StringSet ws = DBEngine.Workspaces(0)ws.Users.RefreshOn Error Resume NextsUserName = ws.Users(sUserName).NameIf Err.Number = 0 ThenMsgBox 'The user you are tryping to add already exists.'
, vbOKOnly + vbInformation, 'Can't Add User'CreateUser = FalseElsesPID = 'BR' & sUserNamesPWD = sUserNameSet usr = ws.CreateUser(sUserName, sPID, sPWD)ws.Users.Append usrws.Users.RefreshSet grpUsers = ws.Groups('BRUsers')Set usr = grpUsers.CreateUser(sUserName)grpUsers.Users.Append usrSet grpUsers = ws.Groups('Users')Set usr = grpUsers.CreateUser(sUserName)grpUsers.Users.Append usrgrpUsers.Users.RefreshCreateUser = TrueEnd IfExit FunctionEnd FunctionJeremy WallaceAlphaBet City DataworksTake a look at the Developers' section of the site for some helpful fundamentals. RE: Super.mdw file surpasses all security (Programmer) 14 Jan 03 16:04. Korngeek, Your question:How do you allow them to create new users and set their permissions without allowing them to get into protected areas of the program?The answer:Only users with adminstrator rights (to EVERYTHING) can create new users.If you absolutely need this feature then you have to deliver a MDW that contains a real administrator (and therefore might be hacked) and use the 'prison' form I have been talking about in a former post.This 'prison' form has to be opened automatically once the administrator logs in and gives only access to the user-creation procedure.
If the form is unloaded, minimized, closed or left by any other means then your application needs has to close automatically.I use this 'prison' form trick in a couple of my applications and it works 100%, but as far as I remember it was quite tricky to block all non-authorized operations for the administrator.Happy programmingFrancescina.
I should hope MS would not be very helpful! There wouldn't be much point insetting up security if MS went around telling people how to break it, nowwould there!:-)If the app has been properly secured, you're out of luck. Many apps,however, are not properly secured.
If you download the security FAQ andWhite Paper from and study all the steps necessary toproperly secure an app, you can work back from there to see if the originaldeveloper omitted any of those steps.Only you and your client can answer the question: if this information was ofso little importance, and so seldom used, that the user can not remember thepassword, is it important enough to justify expending this much time andeffort, with no guarantee of success?BTW: All of the above applies to user and group level security only. Fordatabase password protection, see - however, the presenceof an MDW file would seem to imply that user and group level security hasbeen implemented.-Brendan ReynoldsKris Krogstad wrote in messagenews:888vns$14$1@ffx2nh5.news.uu.net.Pete B14.02.00 00:00. Microsoft would be incredibly foolish to crack your databases for you. Haveyou thought about the legal ramifications if they did not? Sheesh.I think in the future you need to just stop having people try to usesecurity. If they are not willing to handle the responsibility then theyshould not be allowed to use the feature.-?MichKa(insensitive fruitarian)random junk of dubious value, a multilingual website, the54-language TSI Form/Report to Data Access Page Wizard,and lots of replication 'stuff' at?' Kris Krogstad' wrote in messagenews:888vns$14$1@ffx2nh5.news.uu.net.
Ok, I have an access DB that I need to get into ASAP. The problem is that the user doesn't remember her password and I don't know who created it or whatnot. I found the MDW that the file is linked to, but am unable tostill get access. Are there any suggestions as to how I can find out the listof usernames and passwords. Even if I have to purchase an app to do so, although I am not happy about that.
MS hasn't been very helpful.Pete B14.02.00 00:00. I heard that, too, in fact at one time PM specifically stated here that hewould not do so anymore. But ads for PK seem to say different, and I haveseen posts here by the co occasionally since then offering such help. Fromtheir website re their data recovery service:'AWarranty/Certification form must be completed in order for serviceddatabases to be returned. We will fax this form with our quote, and returnyour database upon receipt of the signed form. If the database you forwardcontains copyright information from any other party, you will need toprovide proof to us that this other party agrees to your contracting of ourservices.'
I think they just want proof that it is legally yours to do so. But youmay be right.-Pete BMichael (michka) Kaplan wrotein message news:uAL#r3wd$GA.255@cpmsnbbsa02. Pete, they do not break into databases.?MichKa (insensitive fruitarian) random junk of dubious value, a multilingual website, the 54-language TSI Form/Report to Data Access Page Wizard, and lots of replication 'stuff' at? 'Pete B' wrote in message news:sagb74heivs89@news.supernews.com. Kris Krogstad wrote in message news:888vns$14$1@ffx2nh5.news.uu.net.
Ok, I have an access DB that I need to get into ASAP. The problemis that the user doesn't remember her password and I don't know who createdit or whatnot. I found the MDW that the file is linked to, but am unableto still get access. Are there any suggestions as to how I can find out the list of usernames and passwords.
Even if I have to purchase an app to dosoalthough I am not happy about that. MS hasn't been very helpful. Peter Miller14.02.00 00:00. On Mon, 14 Feb 2000 10:27:13 -0600, 'Pete B' 's machinespontaneously emitted the following random collection of characters:If it gets really desperate, they can try PK Solutions, they have awebsite.Pete,I know you're trying to be helpful, but we really don't want this sort of work.Sure, its easy to get them into their files technically, but for legal reasons,we don't pursue this type of work. If people have an inadequately secured file,there are publicly available sources of information (the whitepaper anddejanews) that provide the necessary info to desecure these files.
If thesecurity is properly enforced, it is still quite breakable, but they will not beable to use our expertise because we don't offer such services.I know that one of my pet peeves - debunking the supposed reliability of the Jetsecurity model - is common knowledge, but the notion that we will providede-securing services to folks is incorrect. Please don't refer such work to us,unless there is a corruption angle, or the client is looking to stengthen(rather than dismantle) the security in force.For what its worth, you may want to sound out Larry Linson on this issue. Heused to do some security stuff a while back, but even so, I would not recommendrefering work to him without discussing the matter with him directly first.Cheers,Peter MillerPK SolutionsFor Microsoft Access related tools and services,including our Data Recovery Rescue Service forMicrosoft Access, please visit our site (below).www:e-mail:Tel: +1 (858) 613-0284 x7 Fax: +1 (858) 613-0283Michael (michka) Kaplan14.02.00 00:00.
See Peter's reply.And fwiw any time I am confused on someone's actual position, I just askthem privately instead. 'Please don't refer such work to us' tells it likeit is. And we now explicitly know the focus is on corruption issues.I think this is a valid way to feel. The tools I use to recover from dataerrors write to system tables and could easily be perverted into somethingthat would crack security.
But I would never do that. I won't even workon corruption stuff, as I think PK Solutions has this area covered well andI do not think I would be able to contribute more to the situation.But a replication problem?
I am all over that puppy!-?MichKa(insensitive fruitarian)random junk of dubious value, a multilingual website, the54-language TSI Form/Report to Data Access Page Wizard,and lots of replication 'stuff' at?' Pete B' wrote in messagenews:sah0fh8vivs144@news.supernews.com. If it gets really desperate, they can try PK Solutions, they have a website. Bob W14.02.00 00:00.
The password is probably on a yellow post-it on the screen or under thekeyboard. Look on the floor in case it fell off.;-)-Trevor Best -Kris Krogstad wrote in messagenews:888vns$14$1@ffx2nh5.news.uu.net.
Ok, I have an access DB that I need to get into ASAP. The problem is that the user doesn't remember her password and I don't know who created it or whatnot. I found the MDW that the file is linked to, but am unable tostill get access. Are there any suggestions as to how I can find out the listof usernames and passwords. Even if I have to purchase an app to do so, although I am not happy about that. MS hasn't been very helpful.Larry Linson15.02.00 00:00.
Peter Miller wrote: For what its worth, you may want to sound out Larry Linson on this issue. He used to do some security stuff a while back, but even so, I would not recommend refering work to him without discussing the matter with him directly first.Nope, sorry.
The only kind of security work I ever did was to securedatabases, and felt like nine kinds of fool when it turned out thatMicrosoft had hidden the Access 2.0 security flaw. Well, I guess I didhave a long discussion, mostly private, with michka over whether yourposting the code was goodness or badness but that's not really 'work'.We agreed to disagree, but came away friends from the discussion. Well,electronic friends, as our physical paths haven't yet crossed.I fired your Access 2 'unsecure' code in anger only a few times, firstto demonstrate to myself that it worked; then to demonstrate tosome 'unbelievers' that it did - made 'believers' out of them in ahurry. What I did find was that with a little extra code to handletables, it is great code to create an unsecured copy of a database towhich you do have access; I've used it or similar to do that withA97, as well.My response to this kind of question is 'the only person I'd trust tobreak security in one of my databases doesn't do this kind of workanymore because of potential legal liablity'.
Guess who I mean by that? The only thing I refer to you now is 'data salvage jobs'.I think there may be a company around who'll break security for a fee,but haven't seen a post from them here in quite a long while, and Idon't know anything about them, anyway, other than that they haveposted here.-L. (Larry) LinsonAccess example databases atNew: Book reviews, previously published in North Texas PC NewsScript execution must be enabled and Windows set to Small FontsSent via Deja.comBefore you buy.Kris Krogstad15.02.00 00:00. Thanks,Tha helped, it was right there in front of us, on the creen, and iteven had the admin password on the back of it. J/K Anyway, a little bitmore on this problem of mine.
I am pretty sure I at least know onepassword. I still am unable to get into the database. The error is asfollows on my workstation, when trying to use the users login and password(for MS Access, not Novell or Windows). Not a valid account name orpassword. When I try to login on her workstation, I get the message: 'Youdo not have the necessary permissions to use the.MDB object. Have yoursystem administrator or the person who created this object establish theappropriate permissions for you.'
So, now I am wondering if this has anything to do with actual computer namein the network settings, or something else. I am pretty sure of at leastthe one users password.
Let me just explain how this all started. Thisuser (Office manager) had a corrupt version of Access, I installed 2000, andnow she can't access the MDB file. I linked it to the MDW file, but stillnada. Still need help.Trevor Best wrote in messagenews:88b2ie$2l5p$8@quince.news.easynet.net.Pete B15.02.00 00:00. On Tue, 15 Feb 2000 08:05:59 -0600, 'Pete B' 's machinespontaneously emitted the following random collection of characters:Whatever.
It was just an offhand comment, didn't mean to instigate allthis discussion and dissension, no such stuff intended.:=)No problem. Its just that every time someone publibly suggests us as a solutionto security lockouts, we get a dozen or so posts from others folks with lockoutswho think we may be a good lead. I'm just trying to head off that sort of stuffat the source.Cheers,Peter MillerPK SolutionsFor Microsoft Access related tools and services,including our Data Recovery Rescue Service forMicrosoft Access, please visit our site (below).www:e-mail:Tel: +1 (858) 613-0284 x7 Fax: +1 (858) 613-0283Michael (michka) Kaplan15.02.00 00:00. 'Peter Miller' wrote in messagenews:3jriass9mbffui2r061t3dqgbkphv17a9v@4ax.com. No problem.
Its just that every time someone publibly suggests us as asolution to security lockouts, we get a dozen or so posts from others folks withlockouts who think we may be a good lead. I'm just trying to head off that sort ofstuff at the source.Admirable.
But never understimate the power of human stupidity (I thinkWoodrow Wilson Smith said it originally).-?MichKa(insensitive fruitarian)random junk of dubious value, a multilingual website, the54-language TSI Form/Report to Data Access Page Wizard,and lots of replication 'stuff' atduken.@hotmail.com16.02.00 00:00. I too have had my share of headaches with trying to learn about Accesssecurity. I'm still learning this stuff but I had a thought about thisproblem:Since the woman working in the office has a valid account the original.MDW file recognizes would this theory work? Could she create a blankdatabase under her Access account. Then, she could import all theobjects from the original database into her new database.
Since shewould be the creator of the new database and its objects, wouldn'tAccess give her Owner's rights to all the objects in her new copy ofthe database regardless of what level of user-security her account has?Please don't flame me if I'm off base here. I'm just trying to pay mydebt for what I'm learning from the newsgroup.Dennis DeLucaIn article,Sent via Deja.comBefore you buy.Eric G. Miller16.02.00 00:00.
I missed part of the thread, but you'all might be able to answer thisquestion (which is sort of related). Has anyone heard of a tool/hackthat captures a user's Access logon screen - sending the username/passwordsomewhere? I don't want one, but recently my logon screen has been behavingoddly (and let's just say I have reason to be paranoid). It may just bestandard Windows corruption, but the screen sometimes blinks or doesn't takethe username/password pair the.first. time (this is why I suspect foul play).I'd appreciate a cc: for answers to the affirmative.-+-+ Eric G. Miller GnuPG public key: +-+Michael (michka) Kaplan16.02.00 00:00.