Howto Setup ADO project for proper Installation?

Hi all! I'm FINALLY rolling out the new employee test program, which uses an Access97 DB to store all the answers & questions. Since it will go out to other sites, I'm told to use InstallShield Express to make a setup/install file.

I'm having trouble with a message that says "Active X component not installed" when I test the setup on a Win95 machine. What files do I need to include when I'm using ADO-surely not the DAO35.dlls!! And please tell me I don't have to include all the files like: MSXCL35.dll, MSLTUS35.dll, etc! I'd appreciate any help from someone whose actually packaged an ADO file and had it work! TIA!!

I have not used install shield exspress before. Usually i use the packaging and deployment tool that come together with VB6.0. I don't have any problem packaging my projects. If all your references are right, then you can use this to check what other activex component has not been included in your installshield. By the way, ADO2.0 uses msado20.tlb and ADO2.1 uses msado15.dll.

I have EXACTLY the same problem!

I decided not to use the package and deployment Wizard because you don't seem to have so much controll other it.

I'm using InstallShield Express and ADO. You can invoke the ADO instalation program mdac_typ.exe from within InstallShield but it looks very messy.


Secondly, if the user has to reinstall thge app (s)he won't want to re-run mdac...

in the end I just included mdca_typ.exe on the root of the CD and included instructions in the installshield Readme text stating that they might be required.

With regards to the other problem, VB somtimes seems to add refernces to DAO components whether you need them or not. Try and remove them and see if it complains!

Thanks for the Advice guys! Mark, just HOW do you have Installshield run the MDAC_typ.exe file; and do you have the system reboot THEN go into the regular Installshield installation?

Or if I understand you right, you DON'T run the MDAC, but you tell the user to run it if he can't get the program to work, right?? I appreciate the help!

I don't know if anyone else can make any suggestions but one thing you could do is make a small executable from which the user selects the required components or one which automatically runs mdac and then sets a registry flag so that when the user restarts it knows mdac has been run and only runs the installshield setup.


You can get install sheild to run whatever you want using the "Express Extensions" feature

Quote:

---

Or if I understand you right, you DON'T run the MDAC, but you tell the user to run it if he can't get the program to work, right?? I appreciate the help!

---

Yeah that's what I was intending to do because my app is only going to be installled on two machines.


I decided to use ADO because I had LOTS of DAO compatability problems but is seems to me that ADO just brings a new set of problems.

I understand that
mdac 2.1.2.4202.3 needs dcom to run on win95/98 but not NT
whereas 2.0.0.3002.15 doesn't.

You can't uninstall mdac.

2.1.2.4202.3 doesn't seem to be backward compatable with 2.0.0.3002.15