PRB: Mismatched Jet DLL Files with Excel and Visual Basic

Last reviewed: September 30, 1997
Article ID: Q148177
The information in this article applies to:
  • Standard, Professional, and Enterprise Editions of Microsoft Visual Basic for Windows, 16-bit and 32-bit, versions 4.0, 4.0a
  • Microsoft Excel for Windows 95, version 7.0

SYMPTOMS

If you install Microsoft Excel from a network server and then install Visual Basic 4.0, you may run into an error message that you cannot create a workspace and that you need to check the installation of VBAJET32.DLL.

CAUSE

The error message is the result of mismatched files. The Microsoft Excel setup program installs the Jet/VBA files on to the network system directory while Visual Basic setup program installs the Jet/VBA files on to the local system directory.

RESOLUTION

To work around this problem, copy the Jet/VBA files installed by Visual Basic located on the local system directory to the network system directory.

STATUS

We are researching the problem and will post more information here in the Knowledge Base as it becomes available.

MORE INFORMATION

This problem occurs only if Microsoft Excel is installed first, followed by the Visual Basic installation. The problem does not occur when Visual Basic is installed by itself.


Additional query words: Excel95 XL7
Keywords : SetIns VB4ALL VB4WIN vbwin GnrlVb kbprg
Technology : kbvba
Version : WINDOWS:4.0 4.0a
Platform : NT 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.

Last reviewed: September 30, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.