DOCUMENT:Q189671  11-AUG-1998  [vbwin]
TITLE   :BUG: Problems with MDAC20.Cab Shipping in VS 6.0 and VB 6.0
PRODUCT :Microsoft Visual Basic for Windows
PROD/VER:
OPER/SYS:WINDOWS
KEYWORDS:

======================================================================
---------------------------------------------------------------------
The information in this article applies to:

 - Remote Data Service 2.0
 - Microsoft Visual Basic Professional and Enterprise Editions for
   Windows, version 6.0
 - Microsoft Visual Studio 6.0
---------------------------------------------------------------------

SYMPTOMS
========

The MDAC20.Cab file was built as a lightweight way to distribute version
2.0 of the RDS and ADOR technologies to a machine without installing all of
the MDAC components.

The version of MDAC20.Cab that ships with Visual Basic 6.0 and Visual
Studio 6.0 (with a Modified Date of 6/22/98) will not install properly if
used in a redistribution scenario. Not all of the files required to use the
RDS and ADOR technologies were included in the file. This means that if you
use this file to redistribute these technologies onto a clean machine,
those technologies will not work on that machine.

If you distribute MDAC20.Cab to a machine that does not have all of the
MDAC 2.0 components installed, applications that use MDAC 1.5 components
will no longer function properly.

The MDAC_Typ.Exe file included with Visual Basic 6.0 and Visual Studio 6.0
will install all of the MDAC 2.0 components, including RDS and ADOR. If all
of the MDAC 2.0 components are installed prior to installing RDS and ADOR
via the MDAC20.Cab file, an application that requires RDS and/or ADOR will
function properly.

Installing all of the MDAC 2.0 components via MDAC_Typ.Exe after attempting
to install RDS and ADOR via MDAC20.Cab will properly install the MDAC 2.0
components and ensure that applications that use either the 1.5 or 2.0
version of the MDAC components will function properly.

STATUS
======

Microsoft has confirmed this to be a bug in the Microsoft products listed
at the beginning of this article. We are researching this bug and will post
new information here in the Microsoft Knowledge Base as it becomes
available.

MORE INFORMATION
================

The Visual Basic Package and Deployment Wizard that ships with Visual
Studio 6.0 and Visual Basic 6.0 will use MDAC20.Cab if you reference ADOR
and/or RDS but not ADO, RDO, DAO, the ADO Data Control or the Data
Environment. To make sure that the Wizard uses MDAC_Typ.Exe instead of
MDAC20.Cab, change the following entries in the VB6Dep.Ini file:

   [MSADOR15.dll]
   Dest=$(CommonFilesSys)\ADO
   Replace Conditional=mdac_typ.exe
   CABFileName=mdac20.cab
   CABDefaultURL=http://activex.microsoft.com/controls/vb6
   CABINFFile=mdac20c.inf

   [MSADCO.dll]
   Dest=$(CommonFilesSys)\MSADC
   Replace Conditional=mdac_typ.exe
   CABFileName=mdac20.cab
   CABDefaultURL=http://activex.microsoft.com/controls/vb6
   CABINFFile=mdac20c.inf

to:

   [MSADOR15.dll]
   Dest=$(CommonFilesSys)\ADO
   Replace=mdac_typ.exe
   CABFileName=mdac_typ.cab
   CABDefaultURL=http://activex.microsoft.com/controls/vb6
   CABRunFile=setup.exe

   [MSADCO.dll]
   Dest=$(CommonFilesSys)\MSADC
   Replace=mdac_typ.exe
   CABFileName=mdac_typ.cab
   CABDefaultURL=http://activex.microsoft.com/controls/vb6
   CABRunFile=setup.exe

The RISC and localized versions of the Visual Basic Package and Deployment
Wizard shipped with an updated version of the VB6Dep.Ini file that contains
these changes.

Additional query words: kbVBp600bug kbDSupport kbdse kbMDAC200 kbVS600bug
kbVS600bug kbvbp
======================================================================
Platform          : WINDOWS
Issue type        : kbbug

=============================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS
PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND.  MICROSOFT DISCLAIMS
ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  IN NO
EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR
ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF
MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.  SOME STATES DO NOT ALLOW THE EXCLUSION
OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES
SO THE FOREGOING LIMITATION MAY NOT APPLY.

Copyright Microsoft Corporation 1998.