vbajet.dll not initializing?

I installed trial versions of this app before.  Suddenly, on machines that ran previous versions fine, I get a runtime error VBAjet.dll or VBAjet32.dll not initializing.  I checked the system folders, and both dll's are in there.  Why is this happening?  I reinstalled that app, too, to see if that would work. Nope.  What do I need to take care of, here?  Thanks for help.
RUSTYAsked:
Who is Participating?
 
MirkwoodCommented:
PRB: Error "The Jet VBA File...Failed to Initialize When Called"
Last reviewed: September 28, 1998
Article ID: Q192934
 


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

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.
 

0
 
RUSTYAuthor Commented:
I installed VB6 to see and possibly to port my app up to it.  Decided not to, so uninstalled VB6 and reinstalled VB5.  I intend to continue developing in VB5.  Do I need to format my whole hard drive and start over, or can I delete some files in the registry or system folder and replace them?  
0
 
MirkwoodCommented:
Reinstall DAO again using VB5.
0
 
RUSTYAuthor Commented:
Doesn't seem to matter.  I still have VBAJet32.dll ver 6.1.8167 in the system folder.  If I could download or somehow get the VB5 version of the vbajet.dll's, would it work to just replace them in my system folder?
0
 
RUSTYAuthor Commented:
Are there other files that will have problems now, too?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.