Click to See Complete Forum and Search --> : ADO distribution files
Vit
Oct 23rd, 1999, 09:30 PM
I'm building setup for a project that references ADO 2.0 library. The setup program doesn't return any errors and it looks like setup passes successfully. But when i try to open connection to database I get runtime error 2147221164. It seems to me that I don't include all necessary files for ADO. Anybody knows what's a full kit of these files?
Regards,
Vit
Clunietp
Oct 24th, 1999, 12:20 AM
What driver are you using to connect to your database and what MDAC version are you distributing?
Tom
------------------
Clunietp@yahoo.com
[qualifications and/or certifications here]
Vit
Oct 24th, 1999, 03:44 PM
I connect to MSAccess database through Jet and use MDAC 2.0
Clunietp
Oct 25th, 1999, 10:32 AM
are you using the Microsoft.Jet.OLEDB.3.51 or the Microsoft.Jet.OLEDB.4.0?
Are you distributing the MDAC 2.0 or 2.1? You might be referencing the ADO 2.0 but what MDAC_TYP.EXE are you distributing to your clients?
Vit
Oct 25th, 1999, 03:13 PM
I use ADO 2.0 and distribute MDAC_TYP.Exe with product version 4.71.1015.0 and file version 2.0.0.3002.15. My Jet OLEDB version is 3.51
------------------
Regards,
Vit
[This message has been edited by Vit (edited 10-26-1999).]
Clunietp
Oct 25th, 1999, 09:21 PM
If you enumerate thru the ADO errors collection, do you get any more info?
Clunietp
Oct 25th, 1999, 09:24 PM
I searched thru MSDN support and the online library, only came up with this. It looks unrelated but has that same error code....
http://msdn.microsoft.com/library/officedev/office97/web/015.htm
Vit
Oct 26th, 1999, 01:49 PM
The only info I get is that "ActiveX component can't create object". And my application is not internet-based one
------------------
Regards,
Vit
Clunietp
Oct 26th, 1999, 10:40 PM
Search in the registry on the problem machine for 'Microsoft.Jet.OLEDB.3.51' AND 'Microsoft.Jet.OLEDB.4' or 'Microsoft.Jet.OLEDB.4.0' (sorry, the machine i'm at right now doesn't have MDAC installed)
do you find either one?
Tom
Vit
Oct 27th, 1999, 01:26 PM
Well, I found the problem. MDAC_TYP wanted DCOM to be installed on the user mashine. Without it setup couldn't load some dll-s and register them.
Anyway, thank you very much for your help
------------------
Regards,
Vit
Clunietp
Oct 28th, 1999, 01:42 AM
DOH!
vbforums.com
Copyright Internet.com Inc., All Rights Reserved.