06-03-2002, 03:32 PM
How do I know what version of MDAC is running on my system....and how to ship it to the end user....
currently im developing an application using MS Access as the database...on user systems it is giving errors...most probably because of a different MDAC Version....
are there any risks with the user installing the MDAC supplied by me....
how do i install it on the end users' systems...
06-03-2002, 03:55 PM
If you are using PDW it's just a matter of putting the MDAC_TYP.exe file into the directory for PDW.
The default location (if VB was set up in the default location) the MDAC_TYPE.exe it needs to go is:
C:\Program Files\Microsoft Visual Studio\VB98\Wizards\PDWizard\Redist
I believe the default version that exist is 2.1.
You just need to drop the version of MDAC_TYP.exe that you want into the above folder.
06-03-2002, 03:57 PM
You could just take a look at the Setup.lst file produced by the
P&DW. If you add mdac_typ.exe to the install package, it will
show what version. However, if you are using ADO in your VB
app, the mdac_typ version will be the same as the ADO object
library version. ADO 2.5 comes from mdac 2.5.
06-03-2002, 05:17 PM
well when i create the package...it shows me there arent dependencies for some files....
well that is ok...but when i install the application, it says some files are in use...close all other applications before installation....they are some dlls...
well let me list the errors...
setup error 168----problem updating registry
msado15.dll error unable to register library
msvcrt.dll file in use
msado20.tlb in use
plz guide me as im pretty new to all this...
06-04-2002, 07:50 AM
msvcrt.dll is the Microsoft Visual C++ run-time and it doesn't
surprise me that it is in use. I would ignore it. On the other hand,
both msado15.dll and msado20.tlb are part of the mdac_typ.exe
data access components, and if you really have shut down all
running apps, should not be in use. I can't tell if you are saying
the error happens when mdac_typ.exe is being installed, or it
happens when installing your app. If you use the P&DW, it
always checks the version of mdac_typ already on the target PC,
and if it is older than the install version, or doesn't exist on the
target PC, it is installed first. After that, you have to manually
restart the VB install.
06-04-2002, 08:58 AM
there are no apps running...how shud i stop them from running if they are...im using P&DW....but initially itself it says..it has problem updating registry...and for the msado15 it says could not update registry...we can ignore msvcrt error but the user has to know that...
please guide me .....a little more specifically...:(
06-04-2002, 09:12 AM
First of all, you should check your install to see if you have included
mdac_typ.exe. Either run the P&DW wizard again, or open the
setup.lst file and look for a line containing mdac_typ.exe. If you
haven't included it, then you need to. See if you have version 2.5.
If you don't, then download it from www.microsoft.com/data/download.htm
06-04-2002, 09:46 AM
i have included MDAC but my system has version 2.0...but i guess if i have developed the app using ver 2.0 then i shud not face any probs installing it on my own system....or do i have to install the new one itself...
i am really confused...MS says install it at ur own risk...and roll back is also difficult...hope i dont have to lose my app...its **** huge....and taken months together to develop....
plz help me
06-04-2002, 10:08 AM
You do not want to distribute version 2.0 with your app. Even if
your app uses 2.0, 2.5 should be backwards compatible. There is
no danger of losing your app. If the system you are installing on
has no mdac or an older version, it will install the newer version.
If it has a newer version, it will just skip the mdac install. The one
problem I can see with this is if the target computer only has
version 2.6 or higher, it won't have the Jet components, and yet it
will skip the mdac install from your install.
Those errors you mentioned earlier, are they from trying to install
on a different PC without VB installed, or from installing on your
own PC with VB installed? You can't tell anything from running the
install on your own PC.
06-04-2002, 10:15 AM
that is what im worried abt...i have developed the app altogether on my system and im facing probs with installation on my own system....i dont think itz a prob with mdac but with other dlls...like i said it says some dlls in use and could not update registry...readonly and stuff....
cant figure out what but i think itz not conc with mdac.....
06-04-2002, 10:22 AM
As I just said, you can't test an install on your own system. The
fact that VB is already installed means you just can't tell what is
working and what isn't. If you have a friend that doesn't have VB
installed, see if they will let you test your install on their PC.