A2K errors with XP upgrade

[jegenes]

I've upgraded from Win98 to XP Pro. The 1st errors I got were "Unable to find VBA6.dll", whenever I clicked on anything on any form, etc. I reinstalled VBA6.DLL and it fixed that (almost...).

Now I'm getting occassional errors when code executes, usually in a form. I've managed to narrow it down to this: whenever a call for a MsgBox comes, it crashes the program, gives the standard WinXP error box, and closes the program. I can place a breakpoint just before the MsgBox command line, and when I step into that particular statement it crashes.

I've recompiled, compacted/repaired, etc, all to no avail. I'm thinking that maybe the VBA6.DLL file I installed isn't the right one. Any ideas on a fix for this? Do I need to go into the program compatibility utility in WinXP?

Thanks a lot

John Egenes

 

[jegenes]

One other thing...

What object library would MsgBox be in? I'm thinking that maybe it's pointing to the wrong library. Thanks

John

 

[jegenes]

Never mind about the last post. I found MsgBox in the VBA library. It's pointing to a file called: msvbvm60.dll I tried renaming other files as that one and using them. It fixed the MsgBox problem but caused other similar ones. I'm 90 percent sure that it's this file that's causing my problems. Don't know if it's corrupted, but I doubt it. I've copied the same file from another computer....same results.

When I open the References box in the VBA code window it shows the following references as being active, and I've added their files here:

Visual Basic for Applications: (file =) msvbvm60.dll
OLE Automation: stdole2.tlb
Microsoft ActiveX Data Objects 2.1 Library: msado21.lib
Microsoft Windows Common Controls 6.0: mscomctl.ocx
Microsoft DAO 3.6 Object Library: dao360.dll
Microsoft Office 9.0 Object Library: ms09.dll
Microsoft Visual Basic for Applications Extensibility 5.3: (couldn't read the filename)

There are no missing references.

Also, there are some other VBA files to choose from (ie: msvbvm50.dll, etc), but I cannot un-check the Visual Basic for Applications box because it gives an error (says the file is in use). If I try to check one of the others, it says that it's a duplicate reference name.... sort of a chicken-and-egg deal.

Also, I tried the Program Compatibility Wizard in WinXP, but it didn't solve the problem, no matter what I chose.

thanks.

--john