DOCUMENT:Q192934  21-SEP-1998  [vbwin]
TITLE   :PRB: Error "The Jet VBA File...Failed to Initialize When Called"
PRODUCT :Microsoft Visual Basic for Windows
PROD/VER:WINDOWS:5.0
OPER/SYS:WINDOWS
KEYWORDS:

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

 - Microsoft Visual Basic Professional and Enterprise Editions for
   Windows, version 5.0, 6.0
---------------------------------------------------------------------

SYMPTOMS
========

After installing a Visual Basic 5.0 application on an end user's computer,
the run-time error 3447 is received when it is executed:

   "The Jet VBA file (VBAJET.dll for 16-bit versions, or VBAJET32.dll for
   32-bit versions) failed to initialize when called. Try reinstalling the
   applications that returned the error."

This occurs when the application is created on a machine with both Visual
Basic 5.0 and 6.0 installed and the setup program for the Visual Basic 5.0
application is created using the Visual Basic 5.0 Application Setup Wizard.

CAUSE
=====

Visual Basic 6.0 installs new versions of the DAO and Jet files on the
development computer. The version of VBAJet32.dll (6.1.8167) that comes
with Visual Basic 6.0 is dependent on Expsrv.dll, but the Visual Basic 5.0
Setup Wizard does not include this file because it is not included in the
dependency information in VB5Dep.ini.

RESOLUTION
==========

You can attempt to work around the problem by adding Expsrv.dll in the File
Summary screen of the Setup Wizard. However, you may run into problems
distributing other updated components as well.

Following are the safest alternatives:

 - Develop and create setup files for your Visual Basic 5.0 application on
   a "clean" computer. (See the MORE INFORMATION section later in this
   article.)

   -or-

 - Upgrade the application to Visual Basic 6.0 and create the setup files
   using the Package and Deployment Wizard (PDW).

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

For the most part, having multiple versions of Visual Basic on the same
machine does not alter the development environment. With regards to
application deployment however, having multiple versions can cause the
application to not install correctly due to newer versions of components
and the inability of the installation application to correctly determine
dependency information and/or register these components. To ensure a good
distribution of the application, the development machine should have only
the necessary version of Visual Basic installed.

REFERENCES
==========

For additional information, please see the following article in the
Microsoft Knowledge Base:

   ARTICLE-ID: Q182116
   TITLE     : INFO: Troubleshooting Visual Basic Setup Wizard Issues

Additional query words: kbdss kbDSupport kbVBp distribute deploy kbVBp
kbWizard kbAppSetup kbVBp500
======================================================================
Version           : WINDOWS:5.0
Platform          : WINDOWS
Issue type        : kbprb

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

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.