Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MDAC 1

Status
Not open for further replies.

BasicBoy

Programmer
Feb 22, 2008
156
ZA
I get error 430 - Automation does not support expected interface -on the installation machines now that I have started using ADO in my VB6 programs, most probably due to version clashes between Windows and MDAC and my ADO version.
I am installing on XP SP3 machines and Windows 7 machines and everyone gives me the same error.
How can get to the root of this error. I have the Component checked but it cannot tell me what discrepencies there are.
What reference should I use in VB6 for ADO and how can I establish whether it will work on the installation machine.
I am developing on a Windows 7 platform and have no problems adding any of the MDAC references.

Thanks
 
I'd reference the lowest x in my Microsoft ActiveX Data Objects 2.x Libraries

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886
 
Thanks PHV - I have tried that, but I am told (via internet help) that the machine should have excatly the same MDAC version as the program - whether that is true I am unsure of. In fact - when you install Windows XP SP3, you automatically install MDAC 2.8 - and an effort to install MDAC 2.5 oj the machine is useless - it will not take it.
Or am I making some other error that is not even connected to MDAC ?


 
I was having a similar problem. I recently switched from XP to Windows 7. Every time I generated a new ADE from one of my Access Projects it ran just fine for me, but not for anyone else. I finally edited the project on one of the older XP machines. I ended up adding the reference "Microsoft ActiveX Data Objects Recordset 2.8 Library" which seemed to do the trick. I already had the reference "Microsoft ActiveX Data Objects 2.8 Library" all along - and all of my data objects seemed to work fine from my machine, but it wasn't until I added the one that specifically mentions "Recordset" that it worked on older XP machines.
 
Also check the hierarchy of project references. If you don't declare databases/recordsets as DAO or ADO explicitly, Access defaults to the highest-order refence on the list.

Gluais faicilleach le cupan làn
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top