11-08-2001, 05:23 PM
I was wondering... perhaps a dumb question here... does it matter what version of ADO I use if I deploy an application created in visual basic to other Windows O/S versions? For example, creating something in Win 2000, deploying to Win 95. I'm currently using ADO 2.6 and I prefer it.
11-08-2001, 05:35 PM
As long as you are supplying the mdac_typ as part of the install, that
should be fine. If they already have 2.6 or greater, it should just skip that
part of the install, if less, it should upgrade them.
11-08-2001, 06:20 PM
I've never included the full mdac_typ in a setup before, but I should probably try doing that. If I remember correctly, the mdac_typ file is an exe file right? If it is, I think that would be a little sticky putting it into a setup program wouldn't it?
11-08-2001, 08:05 PM
If you are using the P&DW that ships with VB it works quite nicely. I have built several installations with mdac_typ.exe included and never had a hitch.
11-09-2001, 06:38 PM
p&dw works fine W95 W98 etc but if W2k with out SP2 your prog won't setup.
08-26-2002, 12:58 PM
I created a module that uses an MsAccess database and ADO controls.
Added reference to MSAD015.DLL
When creating the package, the system automatically adds MDAC_TYP.EXE dated Jan 20, 2000.
Can I replace this with a newer version ?
When I include the above module with my install package, the install abends on a RUNDLL32 error with page fault in HPSCNMGR.DLL.
Can someone guide me ?
This is a simple database with 5 tables. Do I have to install or run MDAC_TYP.EXE on the each new machine ? or is this done automatically if the machine does not have the environment ?
08-26-2002, 01:10 PM
I can't tell what version that is from the date. I would guess it
was 2.6. You could replace it with 2.7, but really with Access, you
are almost better off with 2.5. If the version of mdac_typ.exe in
the install is older than the one already on the target pc, it is just
supposed to skip it during the install. I don't know why you are
getting this error.