Add to this the fact that Microsoft supports only the current release of MDAC and the release before it, and you are arrive at this conclusion: Applications must be designed to work with the current release of MDAC or the release before it.Īs an ADO developer, you should regularly check the MDAC pages on Microsoft's website at From there you can download the latest version of MDAC for free. You can't prevent this upgrade, because MDAC is installed with such commonly used software as Internet Explorer.
#Mdac version upgrade#
Second, whatever version your users have, or you upgrade them to, it is also virtually certain that someone-you, your users, or other application software-will upgrade their existing MDAC to the current release of MDAC. First, it is highly likely that your users will already have MDAC installed on their machines. There are two consequences of this level of availability. MDAC is also distributed with most Microsoft products that have database content.
#Mdac version for free#
Microsoft releases MDAC independently and makes it available for free download and virtually free distribution (there are distribution requirements, but most Delphi developers will have no trouble meeting them). The major releases of MDAC have been versions 1.5, 2.0, 2.1, 2.5, and 2.6. Because ADO is only distributed as part of MDAC, we talk of ADO versions in terms of MDAC releases. Often you will hear people use the terms MDAC and ADO interchangeably, but incorrectly. MDAC is an umbrella for Microsoft's database technologies and includes ADO, OLE DB, ODBC, and RDS (Remote Data Services). NET Preview: The Language and the RTLĪDO is part of a bigger picture called Microsoft Data Access Components (MDAC). NET Architecture from the Delphi Perspectiveĭelphi for. Web Programming with WebBroker and WebSnap Part III - Delphi Database-Oriented Architectures Modeling and OOP Programming (with ModelMaker) Microsoft also has a similar component, but has a dependency of MSXML2.Part II - Delphi Object-Oriented Architectures Use this component checker to find the version of MDAC on user's PC.
#Mdac version install#
But, most of the commands are still the same as for the 2.8 install goes. Sounds a bit not so easy? Well, i will give you the link to couple of articles that will make life easier on this job. they write to an XML log as to what version and other details that you can (read on the fly) make use of and run the installer. There are two COM utilities are available to do the trick. So, before you proceed to automate the installer, your script might need to check the version of MDAC that the user's machine is running, if there is one. However, if you have users having different versions of MDAC, install may not be smooth. There are some known bugs in earlier releases of MDAC up until 2.7 SP1 and the most recent one 2.8 (as of this writing) claim to have fixed the most(?).
Well, MDAC does support a handful of commandline switches that you can make use of, and run an unattended install. If you ever attempt to install MDAC over the network, using a push install type method, you will need to figure out a way to script the installer of MDAC. If you are programming windows forms using VB.Net and SQL/Access db, you would most likely come to find that your program needs MDAC on the machine(s) where it will be installed.