Will MDAC 2.5 mess up an Access 2 or 95 Developers PC ??
I have been investigating all of the issues related to distributing an
Access application with MDAC 2.5.
I am a tool developer currently working with our Test group. The product
developers plan on shipping the product with MDAC 2.5. The product itself
uses an Access 97 database and both DAO and ADO.
This product can be installed on any customer's PC whether they have Win
95/98/Me/NT4/2000, and the customer does not need Office or Access installed
as a pre-requiste.
Some of our customers are themselves developers who still use Access 2 (with
ODBC/Jet, No MDAC) or Access 95 (with Jet, No MDAC or early MDAC).
If we ship our product with Access 97 run-time and simply MDAC 2.5:
** (1) Will we be messing up the computers of our Access 2/95 developer
customers who use ODBC ? **
(2) Will we be messing up the computers of our Access 2/95 developer
customers who use early MDAC ?
It seems that the Microsoft ADO-Jet-MDAC issues stem from different
combinations of different versions of Access, Internet Explorer, operating
systems, and/or various O/S & MDAC service packs.
** Thank you in Advance for ANY insight that you can provide. **
Personally, I think that there is a good chance that there will be problems.
Top DevX Stories
Easy Web Services with SQL Server 2005 HTTP Endpoints
JavaOne 2005: Java Platform Roadmap Focuses on Ease of Development, Sun Focuses on the "Free" in F.O.S.S.
Wed Yourself to UML with the Power of Associations
Microsoft to Add AJAX Capabilities to ASP.NET
IBM's Cloudscape Versus MySQL