Help: Runtime error 3447: the Jet VBA file failed to initialize.

[shippman]

VB5: THis is a new error that just started. We use InstallSheild Express to distribute the application. Access 97 is the DB. This error occurs on about 10% of installations. We cannot find any common bond. We did just load VB5 service pack 3 update. Once this error occurs, the computer is POISONED and will not allow our application to go past this error. This includes previous users of our software who are updating. <br>
<br>
Here is the complete error:<br>
&quot;Runtime error 3447: 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 application that returned the error.&quot;<br>
<br>
Any ideas would be appreciated.<br>
<br>

 

[Ctussey]

Have you checked the following:<br>
1: Do all users have the drive to the Access file mapped to the same letter?<br>
If its not on a network, check to see if the user installed the program to the default setting.<br>
2: Could the users all use the program earlier, and if not, you may want to check that the dlls were packaged with the install shield program, and that they registered.<br>
<br>
<br>

 

[edderic]

This error most commonly occurs when you deploy a Visual Basic 5.0 application from a development computer that has the Visual Studio 6.0 versions of the DAO and Jet files installed. The Jet files that come with the Visual Studio 6.0 products require an additional file, Expsrv.dll. Because the Vb5dep.ini file does not include this file in the dependency information for Jet, the Visual Basic 5.0 Setup Wizard does not include Expsrv.dll in the Setup files for your application. <br>
<br>
<br>
Use one of the following resolutions, depending upon your situation. <br>
<br>
Expsrv.dll Is Missing from Setup Files<br>
If you are deploying a Visual Basic 5.0 application from a development computer that has the Visual Studio 6.0 versions of the DAO and Jet files installed, you can work around the problem by adding Expsrv.dll in the File Summary screen of the Setup Wizard. However, you might encounter problems distributing other updated components. <br>
<br>
The safest alternatives are as follows: <br>
Develop and create setup files for your Visual Basic 5.0 application on a &quot;clean&quot; computer. (See the MORE INFORMATION section later in this article.)<br>
<br>
-or-<br>
<br>
<br>
Upgrade the application to Visual Basic 6.0 and create the setup files using the Package and Deployment Wizard (PDW).<br>
<br>
-or-<br>
<br>
<br>
Download and install the latest MDAC components from:<br>
<br>
<A HREF="

http://www.microsoft.com/data/"

TARGET="_new">

http://www.microsoft.com/data/</A><br>

<br>
Then run the setup for your application again.<br>
<br>
<br>
<p>Eric De Decker<br><a href=mailto:vbg.be@vbgroup.nl>vbg.be@vbgroup.nl</a><br><a href=

http://members.tripod.lycos.nl/VisualBasicCenter/>Visual

Basic Center</a><br>

 

[shippman]

Eric was right on the money. We added the expsvr.dll file to our InstallSheild setup kit and the error went away.<br>
<br>
We will probably upgrade to 6.0 to avoid any further occurances.<br>
<br>
Thanks Mark/ ShipRite Software