Printable View
Help!!!
I'm trying to connect an Access 2000 database to a VB6 application. I've already tried installing the VB6 Service Pack 5, and I'm still receiving the following error:
Run-Time error '-2147467259 (80004005)':
Unrecognized database format <filename and path appears here>
Can anyone offer help and/or suggestions? Thanks!
peet is really good with DB's. Maybe he's online right now...:D;):)
Your title screw up the forum !!! :o
You need not only SP5 but also latest version of MDAC. Get it here www.microsoft.com/data
are you using Microsoft Jet OLEDB 4.0??? If you use that you shouldn't have any problems.
Dang Daok! I'm sorry if you have a problem with the post. I just need a little help. I was using 3.51 and the form wouldn't even load I change the code to 4.0 and now I still get an unrecognized database format. I'm currently downloading the new MDAC, and hopefully it will work, I'll let you guys know. Thanks VB-Warriors!!!
Which MDAC should I download? I'm running Access 2000, VB6, and Windows 98. (No SQL)
2.5 if you have SQL server (because of that cluster problem)
2.6 otherwise.
MDAC 2.6 and above won't have any JET components. So if your problem resides there get 2.5. I think you should have the Jet on your system tho since you got access 2000. Still 2.6 can cause problems. Using 2.5 is the safest bet.
Maybe somewhere in your connection string there is an error? Try to connect to your DB via DataEnvironment. Once you got a connection established get the connection string from your DE and remove it from your project(DE is unnecessary and only works for the simplest queries)
hth,
Helger
You sure? I thought they removed Jet from SP5 which is why you had to get the MDAC?Quote:
Originally posted by Helger
MDAC 2.6 and above won't have any JET components.
I got this from the MS knowledge base:
Starting with Microsoft Data Access Components (MDAC) version 2.6, MDAC no longer contains the following Jet components:
Microsoft Jet
Microsoft Jet OLE DB Provider
ODBC Desktop Database Drivers
For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
Q239114 ACC2000: Updated Version of Microsoft Jet 4.0 Available in Download Center
The "MDAC 2.5 Stack and Windows File Protection" white paper contains a full list of the components that are shipped with MDAC 2.5, along with a discussion of Windows File Protection. Refer to this white paper for more information about the Jet dynamic-link libraries (DLLs) that are included in MDAC 2.5, which are no longer a part of MDAC 2.6.
For more information about MDAC 2.5 and Windows File Protection, see the following Microsoft Web site:
http://www.microsoft.com/data/mdacwfp.htm
Of course that does not mean Jet has not also been removed from SP5. Where did you get that piece of info?
regards,
Helger
yeah you're right I was just going mad for a minute. :)
There are a huge number of possible bugs that cause this error - I've just spent four days trying to fix a clients database that was throwing this error intermitently...
Here's some links from MSDN to help you along...
http://support.microsoft.com/support.../Q183/0/60.ASP
http://support.microsoft.com/support.../q209/1/57.asp
http://support.microsoft.com/support.../Q293/8/05.ASP
http://support.microsoft.com/support.../Q306/2/69.ASP
http://support.microsoft.com/support.../Q238/4/01.ASP
The apparent cause of my problem (the database hasn't fallen over in the last week, so I think it's fixed) was that the database was originally created in Access97, but it needed to be repaired and compacted, and the compact was done using Access 2000. This appeared to have changed the Access system tables or indexes which in turn caused problems. I did a forced conversion of the DB to Access 2000 format and all was well.
Other possible problems/solutions
* Install MDAC 2.6 SP1 - while it doens't contain the Jet drivers, it DOES have the ADO updates required
* Check the network paths - apparently network paths and mapped drives can cause grief
* If you're on a Novell network, well, you're pooched
* There is a setfocus issue to do with the Commandbars (it's in the links above), but it seemed pretty irrlelevant to me
- gaffa
if you are using a data control to connect to your access 2000 database, make sure the connect property is set for Access 2000. when using an Access 97 database, the connect property needs to be set to access.