ADO 2.7 library

noccy

Registered User.
Local time
Today, 22:53
Joined
Aug 19, 2003
Messages
67
Does anybody know if the ADO 2.7 libraries are a part of Windows xp or is it in the vb runtime files?

I have a db where i use this library, made in office 2002.

This db won't work on another machine with office installed.

I have Windows xp, the other machine has windows 2000....could this be the problem?


noccy
 
MDAC

The following is from the MS MSDN site for the MDAC:

ADO 2.8 Programmer's Guide

Installing and Redistributing ADO
Beginning with Microsoft Windows 2000, MDAC is an integrated part of the operating system. Future OS releases will contain MDAC components. The MDAC SDK can be found within the Platform SDK. The Microsoft Data Access Components can be redistributed in English and 18 other languages. The redistribution package is available for download on the Microsoft Universal Data Access Web site.

To install MDAC on Windows 95, Windows 98, Windows NT 4.0, Windows 2000, or Windows Millennium Edition, run the setup program, for the redistribution package, Mdac_typ.exe. This program is available from the Universal Data AccessWeb site.

To cut through the geek talk, the MDAC is where the dll(s) for ADO come from. Updates occur frequently as evidenced that ADO 2.8 is available now. To test the MDAC version and to test your ADO dll's odbcs etc, use the MS component checker which is availble free from MS. Go to the MSDN portion of MS then to the Microsoft Data Access Components section for downloads. Look for the component checker. Then run it on both systems. You'll see which version of the MDAC that you have and if you have any corrupted dll's.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/mdacsdk/htm/mdacstartpage1.asp

The following site shows the current MDAC downloads and the component checker.

http://msdn.microsoft.com/library/default.asp?url=/downloads/list/dataaccess.asp

By the way, I used the Component Checker(CC) once to determine why a customer couldn't read my database, it turned out every one of her ADO dll's were corrupt.
 
Last edited:
tnx m8, helped me fix it =) Everything OK now
 

Users who are viewing this thread

Back
Top Bottom