Re: MDAC_TYP.EXE

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

"LondonLad" <LondonLad@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:ACEB0E21-AC3F-4238-BBF8-84846BB8BF19@xxxxxxxxxxxxxxxx
Hi
I am creating my first Inno setup and as far as I can tell I want to include
mdac_typ.exe and I have been advised that it must be the same version that is
used in my VB Program.
The version I have down loaded from MS is Ver. 27.1.9040.2 while the ver. I
have installed in my VB program is 25.0.4403.12.
Should I update my vb program?
and if yes what folders do I need to copy it to? as I can see from a search
that it lives in various folders.

Ron

For ADO a scheme was introduced where each new ADO version replaces the old one and installs typelibs for the interface signatures of prior releases. The typelibs "point to" the latest ADO DLL. When developing, you target the lowest level of ADO functionality you require. This is most often ADO 2.5 for VB6, unless you need named parameters (ADO 2.6) or something else added after ADO 2.5 came out. Then your programs will work on any system with ADO 2.5 or later installed.

See http://msdn.microsoft.com/en-us/library/ms676506(VS.85).aspx

Anything prior to ADO 2.5 is now considered "prehistoric."


Be wary of early binding to ADOX. For a long time most Windows systems had an ADOX 2.8, but Vista only has ADOX 6.0 and no such "binary compatibility" typelib for prior-version ADOX clients.


Running an MDAC_TYP.exe should not overwrite a newer version, so if you need to deploy to downlevel systems it probably doesn't hurt. However anything that old may lack Jet 4.0 as well, and MDAC_TYP.exe doesn't contain Jet anymore... there is a separate installer package for each OS that needs to be selected and run separately.

http://msdn.microsoft.com/en-us/data/aa937730.aspx

To handle this automatically you'll probably need a fancier installer than the PDW provides (without customizing Setup1).

.

Relevant Pages