Need to open secure database - any ideas? 1

[Tomadams]

Hi,
I have to modify a database created by a prior developer. None of the original users are available. It tells me I don't have authorization to open the db. Any ideas???

Thanks

 

[cmmrfrds]

You could try putting your own system.mdw file in the same directory that holds the Access MDB file. I believe Access will look in the current directory for the mdw file first.

 

[RobSindle]

Actually the location of the system.mdw file is not the issue. The location of the default workgroup file is stored in the registry. Its also that they were starting up the database via a shortcut that told Access which .mdw file to use for validation.
A shortcut with something like the following in the 'target' box:

"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" /wrkgrp D:\Application\CustomWorkgroupFile.MDW

You can try a couple of things.
There is "break-in" code laying around that exploits the fact that when we were taught to "create the bypasskey property" most were taught:
Set prpAllowBypassKey = db.CreateProperty("AllowBypassKey", dbBoolean, True)
which would leave your database vulnerable to 'getting around the bypasskey' on startup.

The new 'correct' way is:
Set prpAllowBypassKey = db.CreateProperty("AllowBypassKey", dbBoolean, False, True)

Also, there are password crackers out there who will crack the .mdw file for you for a reasonable amount of money (see the web).
Hope this helps.
Rob

 

[Tomadams]

I think the problem lies in the workgorup. Before the app opens i am told that I don't have the necessary authorization. I have copied the .mdb to my C: drive. Any more ideas?

 

[jsteph]

If the db was well-secured, none of the pwd crackers will work on the .mdb--they work where the user/pwds are stored--the .mdw.

If you are in an environment where the original .mdb was run, then you need to look for the .mdw. It need not have an .mdw extension--I rename mine to <something_Generic>.dll and put the shell call with the /wrkgrp command line in a small vb executable, making it harder (though not impossible) to find the workgroup file.

It's my guess that there are MS'ers out there who may sell their services for cracking a well-secured .mdb (even encrypted) without the .mdw.
--Jim

 

[RobSindle]

Agree it would be way helpful to find the .mdw (and Yes, the password crackers only work on the .mdw file). They are available via the web and don't cost too much.

If you don't find the .mdw, it may be a tough go.
Good luck and keep us posted.
Rob