[RESOLVED] run-time error -2147467249

[Aelanna]

I'm back with yet another question. ;)

I have a program written in VB6 that uses an Access 97 database. I have distributed this program to several users in various countries using various versions of Windows and Office. Everyone is able to use the program fine except for one person in Russia. She is receiving this error message:

run-time error '-2147467249 (80004005)'
Cannot open database. It may not the database that your application
recognizes, or the file may be corrupt.

She is running XP Professional 2002 Service Pack 1, and Microsoft Office 2003. She has English, Russian, and Arabic on her machine.

She said she receives the same error if she simply tries to open the database file using her Access 2003, so I believe the error is a version incompatibility issue. Is there some way to fix this?

[Hack]

Is she able, using Access, to convert the database to a 2003 format?

[Ecniv]

Perhaps it is how you are connecting to the db?
Access 97 uses um let me think, access dao 3.5 and Access 2003 uses 3.6. Perhaps the required mdacs for the older access are not on the machine and 3.6 is being defaultly used (or something like that). Or the database has been converted up to 2000+ and the connection is still for 97 so doesn't recognise the mdb format.

[Aelanna]

The database hasn't been converted by anyone, and she can't convert it or do anything to it because she can't even open it. The program uses MDAC 2.7. We don't want to convert the database, just open it using the program.

[Aelanna]

No one's had this problem or knows how to fix it?

[NeedSomeAnswers]

As stated by Ecniv, The problem lies with the Mdac.

Access 2003 uses a newer version of the Mdac, so the user probably wont have the Mdac 2.7 installed on thier machine.

You could try installing Mdac 2.7 on her machine this may work !?

The main issue you will have is that Access 97 is old and databases made using it are not directly compatible with newer versions of Access.

[Aelanna]

She tried installing MDAC 2.7 and says it didn't work.

I'm not sure why there should be a problem, though, since the problem isn't opening it in Access, but rather opening it in my program, in VB6. We don't want to open it in Access, we just want my program to run.

[NeedSomeAnswers]

I think you will find it difficult to solve this, i have had a look around and it seems that Access 2000 or later does not support the Microsoft DAO 2.5/3.x compatibility library.

Because of this i don't think you can use a database that has been created in access 97, with DAO 2.7 on a machine that runs Access 2003.

Is thier no way you can get your hands on a newer version of Access, 97 is old and very out of date. The longer you use it the more compatibility problems you are going to find.

If you do get a newer version of Access you will then have to upgrade both the Database (to the newer format) you have & your Code to use newer a version of the DAO objects.

Personnally i would use another database entirely but i guess that some people may not find this practical.

[Aelanna]

Well, I don't have any choice in this. This program I wrote is designed to be compatible with another program I use, so I have to use the database and version it uses.

Since it's only one user out of 75+ having a problem, I'm not overly worried about it. I guess I'll have to find a workaround for her for now. Thanks.