Click to See Complete Forum and Search --> : Urgent : Run time error 3447 VBAJET32


Mukesh Idnani
February 24th, 1999, 09:27 AM
We tried to Install our Vb Application on the New Machine. It got Installed also, but when I execute my applicaton I get the following Error "Run time error 3447 VBAJET32 Failed to initialize when called". Can any one Please tell me why this Error is coming. Is it because of some mismatch in the DLL files. Because What I Have on this new machine is same as what I had on my Development Machine.


My application is using MS Access 7.0 and Oracle 7.3 as a Databases. I am Using VB 5.0 and Created my application Wizard With Wise Installer 6.0

Chris Eastwood
February 24th, 1999, 10:28 AM
Hi


I found an answer (probably) to your problem on the MSDN - search for article Q192934.


Here's a brief extract :


--------------

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).


------


See the whole thing at http://msdn.microsoft.com


Then search for Q192934 (make sure you select Knowledge Base) when you search.


Regards


Chris Eastwood


CodeGuru - the website for developers

http://www.codeguru.com/vb


Search the MSDN for Q192934