Printable View
Hi
I had a slight problem with installing a program that uses OLEDB to talk with SQL server, and OLEDB jet 4.0 to talk with an access database.
On the machines I tested it, it nicely installed oledb 4.0 as I wanted, but on one of the machines of the customer, there was already OLEDB3.51 installed, and it didn't install 4.0 ... does anyone know why??
Tnx
According to Micro$oft, you shouldn't distribute the data access components with your program (if you want your program to have the logo "Design for Windows95/98 etc), but rather install the MDAC from the self-extracting file. You can get it from MDAC and ivoke this file from your setup.
------------------
Serge
Software Developer
[email protected]
[email protected]
ICQ#: 51055819
[This message has been edited by Serge (edited 12-02-1999).]
Funny though that the P&D wizard adds the mdac_typ itself to the setup... but besides that, it doesn't setup correctly (after running dcom98 and my setup the connection with sql server could not be made, I had to run mdac_typ manually (make sure it's not in the same dir as setup.exe since then mdac will start setup.exe ??!!)
Hehe I'm not sure if I want to have an M$ logo *LOL*
But after all, the only problem I had was with the jet-engine part of ADO. (3.51/4.0 stuff) of which I still haven't found something.. it just don't install oledb for the jetengine version 4.0 if 3.51 exists... which basically sucks...