VBAJET.dll errors using DAO CreateWorkspace()

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Just wondering if anyone has seen this before.

I am getting an error only on one PC operating Windows XP with Access XP
(2002). Whenever I issue this code from an independent VB Script to connect
to a database file secured with user-level security:

Set eng = New DAO.DBEngine
eng.SystemDB = "<Path To Workgroup File>"
Set wk = eng.CreateWorkspace("WS1", "<User Name>", "<Password>")

I get the following error on the last line:

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.

On the bad PC I uninstalled and reinstalled Access Runtime (the same package
used on 50+ other PCs that are working fine with this code on Win98, Win2k
and WinXP) and continue to get the same error.

I don't know what else to do short of re-imaging the machine. Does anyone
have any experience with this error?

Thanks
Jeff
 
JeffK said:
Just wondering if anyone has seen this before.

I am getting an error only on one PC operating Windows XP with Access
XP (2002). Whenever I issue this code from an independent VB Script
to connect to a database file secured with user-level security:

Set eng = New DAO.DBEngine
eng.SystemDB = "<Path To Workgroup File>"
Set wk = eng.CreateWorkspace("WS1", "<User Name>", "<Password>")

I get the following error on the last line:

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.

On the bad PC I uninstalled and reinstalled Access Runtime (the same
package used on 50+ other PCs that are working fine with this code on
Win98, Win2k and WinXP) and continue to get the same error.

I don't know what else to do short of re-imaging the machine. Does
anyone have any experience with this error?

Thanks
Jeff
Click to expand...

I haven't seen this before, and can't say I know much about it, but a
search turns up these articles in the MS KnowledgeBase, which may be
related. Other web pages that turned up in a Google search for that
error message suggest to me that the first article is more relevant, but
I'm just guessing.

http://support.microsoft.com/default.aspx?scid=kb;EN-US;196057

http://support.microsoft.com/default.aspx?scid=kb;EN-US;191735
 
Thanks Dirk! I was excited that this might work for me but unfortunately all
the files referenced in the articles are not only present on the offending
machine but they are all the most updated versions - versions that match all
the other working WinXP machines :(

The problem is occuring in a VB6 exe that connects to a secured Access
database. What's odd is I am able to run Access databases successfully on
the PC, but I cannot connect to them from a source outside Access. I tried
executing the code from an Excel VBA project and get the same error.
 
JeffK said:
Thanks Dirk! I was excited that this might work for me but
unfortunately all the files referenced in the articles are not only
present on the offending machine but they are all the most updated
versions - versions that match all the other working WinXP machines :(

The problem is occuring in a VB6 exe that connects to a secured Access
database. What's odd is I am able to run Access databases
successfully on the PC, but I cannot connect to them from a source
outside Access. I tried executing the code from an Excel VBA project
and get the same error.
Click to expand...

Well, drat! I'd really hoped that those articles would solve your
problem. I'm at something of a loss at this point. As I understand
what you've said, this application runs fine on other machines with the
exact same apparent configuration as the one where it fails. Make sure
that this PC has the latest Jet service pack installed:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;239114

If all the relevant file versions look okay, you might try reregistering
them using regsvr32.exe . Of course, you may already have done this,
but the only thing I can think of is some DLL being out of date or
unregistered.
 
Back
Top