Recover Access 97 Database Queries/Reports?

[ainkca]

I've got an Access 97 database that's asking for a password when I didn't set one.

I did all the password 'hacking' I could figure out. (I figured that was OK since it's my application in the first place). All I got back was a 'garbage' password full of symbols etc. My method was working on other apps I wrote though, and I got the same garbage back for both the methods I tried. This led me to think the methods were sound, but the file was corrupt somehow.

Digging around the net, it sounds like what COULD have happened was a user opened the database inside of another application (like Word or Excel) and then saved it.

Possible solutions (ie, getting the data out using ODBC) don't help much because it's the queries and reports I need. The data in the database was pulling from a separate place anyway.

The corruption appears to have happened Feb 10th. The oldest backup we had was from the 11th (OF COURSE). YARGH!!!!!!!

Any ideas or am I out of luck? I know it should be no big deal to redo the queries, but the tables they're based on (not my design) were put together in such a bad way that it was brutal getting everything to work. I can't change the design because the data is in a purchased Access application, and I don't have permission to make changes. Not to mention I don't want to be responsible for it's behaviour etc, if I touch it.

Thanks for any help you can be... I hope I've given enough info to help with a reasonable answer.

ainkca

 

[jbehrne]

Hi,

You could try creating a new db and then importing everything from the corrupted one into it...

HTH,

jbehrne

 

[ainkca]

Sorry, I should have mentioned that I tried that already, but I forgot. It asks me for the password and I can't get any further.

I also should have mentioned that I don't think it's a workgroup issue either, as I get the same thing on all our other servers. (Load balanced servers that are identically set up... each one would have a workgroup file, unless I've misunderstood something)

Thanks for the suggestion though.

 

[GDGarth]

Is it asking for a user log in, or a database password? If it's a user log in, did the database have security implemented? If so, do you have a backup copy of the .mdw file? If it didn't have security, try using a fresh copy of system.mdw (this is the default workgroup file installed with Access.

Make sure you're joined to system.mdw. Try opening Access without opening a database - does it prompt you for a password? Then try opening the database.

 

[ainkca]

It's asking for a database password. No security was set on the database, (shame on me) I wasn't done developing, and only 4 other users have access to that folder on the network.

I can open other databases and create new one without any trouble.

When I copy the workgroup file from another server(one I haven't logged on to and tried to open the file) I get the same error.

I have not tried 'joining' the workgroup file... I'll look up how to do that and give it a try.

 

[GDGarth]

It seems pretty obvious to me that someone has set a password for the database. If it was accessible to a bunch of others, you may never be able to sort it out. If it really is only 4 people, one of them may eventually fess up. Unfortunately, it's entirely possible that whoever did it didn't even know they'd done it.

Joining the workgroup won't make any difference, in this case. I'd concentrate on trying to find out who put the password in the database.

This is one of the reasons I install security before I put anything on the network - so no one can inadvertantly do something like this.

 

[ainkca]

I was convinced someone set the password as well, but the password sniffers I've tried have just returned binary garbage as the password. And I know the sniffer is working because it works on other databases.

I really think someone opened it in another app. (I'll be the first to admit I'm wrong of course, but that's really what I think).

I've not given up, but I may need to break down and call one of those database repair companies. Has anyone ever dealt with one of them?