Here’s the scoop: A friend of mine gave me a copy of an Access database file. It’s extension is .mdb but when I try to open it with MS Access, it tells me “Unrecognizable database format.” It then says that it has to be “Jet extension” or something like that, but jet extension IS .mdb but it still won’t open, so how do i get this file to work?
The easiest answer is that your friend gave you an Access2000 file and you’re trying to open it with Access97, or an Access97 file and you’re trying to open it with A95, etc. Check that first and let us know. There is backward compatibility where you can open an A97 file with A2K, but not vice versa. If this is the problem, have your friend save the file as the appropriate dbase that you have.
We are both using 2000.
Then there’s a possibility that the dbase file is corrupt. Open A2K and try to run the compact/repair utility under database utilities. He doesn’t have linked tables to this app, does he/she?
When i try to run the compact/repair tool, I get the same unrecognizable file error. What does “linked tables” mean?
There’s also the possibility your friend created the file with another program which saves the data in Access mdb files but is set up so that those can only be opened with the program used to create it. I’ve encountered a couple of programs that operate that way.
Send your file back to your friend to see if they can open it. If not, it got corrupted in transit to you. Just have them resend the original file. If they can open it then there is something wrong between the two versions of Access you both have.
A linked table is a table that is in another database. The other database could be Access, SQL Server, dBase or any of a large number of database types.
A linked table can be viewed from the Access database, just as if the data was actually being stored there, but not if you are looking at it on a different machine than the one the link was created on, since the source database isn’t available on your system.
The reason I have the file now is b/c his computer got messed bad. It wouldn’t boot any further than POST. So I reinstalled Windows 98 but scandisk made some changes. Changes included renaming Windows directory to “Dir00003” and Program Files to “Dir00008”. But anyway, everything got renamed and now Office programs don’t load right. So I’m wondering if when he does load it back on, whether or not his file will even work at all! And of course I would be the one he’s gonna blame b/c “I was the last one to touch it”.
Is there anyway to send the file to Microsoft and have then “debug” it to make it work?
Muldoon III, I think this situation requires a punt. If your bud’s machine was trashed and then he sent you the file, it sounds very much like it was corrupted from his machine. If I had your bud’s machine, I would slick it and start over. As far as recoverability of this file, you are SOL. I’m sure M$ would love for you to send them this file and charge you appropriately. As someone who works with Access for a living, I have never heard of M$ offering data recoverability services. (If anybody’s ever heard of this, please let me know)
The file was fine BEFORE the machine got funked up though. There IS a backup, however, BUT, what if the backup is just as corrupt as this one? I mean Access doesn’t want to open this .mdb at all! So what are the chances that it will open this one? Could the size of the file have anything to do with it? it’s 32KB long.
32KB is suspiciously small for an Access mdb; I just created a blank one and saved it empty; it was 52KB.