Access 2003 Can't open Access 97 .mdb--why?

[jsteph]

I'm having a severe problem with an installation of Access 2003. First--all of my other installations of acc2003 can open '97 .mdbs just fine. This particular machine won't allow it. It's Server 2003--I don't know if that makes a difference--the other machines were XP Pro.

Anyway, the exact error I get is:

Cannot open database <blah...blah...> It may not be a database that your application recognizes, or the file may be corrupt

The file is not corrupt. I can open it from '97, and even from 2003 intances on any other machine. I'm logged on as administrator, so I doubt it's a file security issue. I created a new .mdw file with the 2003 workgroup admin, just in case it was that. Then I created a new, empty '97 .mdb with absolutely no security, and it still won't open with the instance of 2003 on this machine.

I've googled, and come up with lots of different bizaare things that don't quite match this situation. I've tried repairing the Office 2003 install, and I've tried re-installing it. Same. What else should I check for on this? Are there any known 3rd party tools that torpedo these installations--like Adobe Acrobat SDK, for instance? Thanks,
--Jim

 

[ThomasLafferty]

How are you opening the DB? Directly from Access (File Open)? From Windows Explorer? By a connection string? If by a connection string, are your reference libraries loaded?

Guessing...Tom

Born once die twice; born twice die once.

 

[jsteph]

Tom,
Thanks...I'm opening it both by dbl-clicking on an .mdb, then by opening the Access 'shortcut' (which really isn't a shortcut, but that's another MS issue), then using the Access 2003 standard file open dialog. Each way gives the same error.
--Jim

 

[PGoRule]

Try converting the any Access 97 database to Access 2003.
Tools->Database Utilities->Convert Databse...
Is it giving some error?

Sharing the best from my side...

--Prashant--

 

[PGoRule]

Try this too...
Install MS-Office Service pack 2.
Service pack 2
Issues that are fixed in Access 2003 by Office 2003 Service Pack 2

Sharing the best from my side...

--Prashant--

 

[jsteph]

PGoRule,
Thanks, but neither are options--I'm already at sp2, so that's out. The machines that actually can open the '97 .mdbs are also on sp2 which makes me wonder if it's a server 2003 issue--and we're fully up to date on all service packs and patches there.

And converting, while it is an option down the road, is not going to get me going now, or even in the next week or so. The main problem here is not so much opening the actual .mdb--but linking to the backend tables. The same error comes when I attempt to open the .mdb, link a table, import a table, form, report, etc., or convert the .mdb.

This machine needs to link to or open dozens of old .mdbs, so to convert all of those would take a lot of time to test, etc. In addition, many are connected to by older client machines which have not yet had access 2003 installed, so we're stuck with 97 format for many of these backends until those clients are updated. It's a real catch 22
--Jim

 

[jsteph]

I'm happy to report I've found the problem. It was an MSKB article:

http://support.microsoft.com/kb/310937/

Which basically said to do the following re-reg's:
regsvr32 "C:\Program Files\Common Files\Microsoft Shared\DAO\DAO360.DLL"

regsvr32 "c:\WINDOWS\system32\msrd3x40.dll"

This did not come up in my original google searches but after refining the search, this came up and it fixed the problem.
--Jim

 

[PGoRule]

Cheers...Happy time...This calls a party.


Sharing the best from my side...

--Prashant--

 

[assets]

It is not a good idea to convert access97 directly convert to access2000 first. If you can find somebody with a copy.

Never give up never give in.

There are no short cuts to anything worth doing

 

[jsteph]

assets,

It is not a good idea to convert access97 directly convert to access2000 first.

Out of curiosity, why do you suggest this?
--Jim

 

[assets]

I found that there were problem with 97 going to 2002. But if i converted it to 2000 first then opened it in 2002 it work fine. there were some forum a couple of years ago on this issue.

Never give up never give in.

There are no short cuts to anything worth doing