vba crashes whenever I do anything

[HawaiiTom10]

Hi - Any thoughts on the following:
I have a large Access 2002 database for my coin collection. For some events, I launch vba and run some commands. On update, etc.. Everything was working well, then I ruined it...

I felt like Office XP Pro 2002 was hanging and installed my laptop's Office XP Pro 2003. All office applications upgraded, except visual basic stopped working. I could still launch it from access/form properties/event procedure - but as soon as I started typing, it would crash.

I figured VBA might be realizing I was using my laptop's copy of office and there might be a registration issue.

So, I reverted back to the Office 2002 CD's that I originally had. All applications reverted, but same problem in Visual Basic. I can launch it from Access, but any editing will crash it.

The event viewer lists (when I crash visual basic) the faulting application as msaccess.exe and the faulting module as vbe6.dll.

I don't even know how to trouble shoot from here.
-Tom

Thanks for your time.

 

[Remou]

Have you tried reinstalling Access?

 

[HawaiiTom10]

When I reinstalled Office, that includes Access - right? Thanks for the time.

 

[Remou]

Sorry, my mind was wandering.

I think method 3, here:

http://support.microsoft.com/kb/212669

may apply

 

[HawaiiTom10]

Hi -
I saw this part:
On the Tools menu, point to Macro, and then click Macros.

The Windows Installer detects that the Vbe6.dll file is missing on the system, installs the file from the Office CD, and registers it again.
--------------------------------------

The new .dll gets registered? Is that something that happens over the Internet with MS, or is it just some system level registration?

THanks,
Tom

 

[HawaiiTom10]

I just tried re-installing the .dll from the Office CD. I can still launch the VB editor, but as soon as I try and assign something - it crashes. Going bonkers

 

[Remou]

When you rename the .dll and reinstall, the .dll is added and registered. If this is not working out, it might be best to completely uninstall, reboot, and reinstall the whole of Office.

 

[HawaiiTom10]

What about Microsoft .NET Framework 1.1 and MS .NET Framework 1.1 Hotfix? Do those have anything to do with vb? If I remove them, will the Office CD's re-install? Is it worth doing?

Thanks

 

[Remou]

I think I would start with some smaller things, for example have you looked at decompile?

http://www.granite.ab.ca/access/decompile.htm

Have you installed any necessary fixes / updates for Office?

 

[HawaiiTom10]

GOLDEN. I checked out the link and started to reply that I didn't think the size of the db was the problem. To prove it, I started an empty db and added a combo box to launch vb from. An activeX error came up. If I ignored, my symptoms were the same as I have been describing. Troubleshooting the activeX error, I found an MS article recommending running regsvr32 on the dao350.dll. That didn't fix it, but there was a dao360.dll in the same folder, so I regsvr32 on that one. This cleared away the activeX error. Going back to my original db, visual basic was suddenly happy and functional! Thanks much for the time. God bless the Internet