VBA6 crash on reference lookup (Access 2007)

[Phoig]

Anytime VBA attempts to display the references/methods (either by manually
selecting the menu, using the HotKey, or automagically whenever the parser
encounters a period or bang), both VBA and Access crash to desktop. This
happens with *ANY* database, even brand spanking news one with absolutely
nothing in them. There are no add-ins whatsoever & the only references are
the two that VBA won't let me remove. I've kept both Office & Windows as upto
date as possible. Everything works just fine in Word & Excel; only Access
displays this problem (which is where I do the vast majority of my coding.)
Perhaps significantly, attempts to place a command button on a form with the
Wizards enable yields the very helpful "Unable to load DLL" error repeatedly.
The error will continue to pop-up every time a new selection is made for the
function of the command button. This is on my home system & I've not had a
bunch of free time in a long while, so this was the first crack at a couple
of databases that have languished for the last few months. Any ideas &
suggestions appreciated. Thank you!

 

[Phoig]

Been incommunicado for a little while (stupid rotten Fallout 3 sucking up my
freetime... Anywho, yes, all the Service Packs & HotFixes have been
installed. First thing I did was head out to the Microsoft Update page & make
sure that I hadn't missed something.

 

[Phoig]

Okay, installed the hotfix provided via the link you kindly included. Sadly,
however, the problem still exists. I am running the Repair option from the
installation DVD but I don't have a whole lot of hope for that being
successful.

The HotFix does not install automatically. You have to download and install
manually.

Been incommunicado for a little while (stupid rotten Fallout 3 sucking up my
freetime... Anywho, yes, all the Service Packs & HotFixes have been
installed. First thing I did was head out to the Microsoft Update page & make
sure that I hadn't missed something.

You've installed the Office 2007 SP1 and the HotFix, correct?
http://support.microsoft.com/kb/960307

[quoted text clipped - 14 lines]

of databases that have languished for the last few months. Any ideas &
suggestions appreciated. Thank you!

--
RuralGuy (RG for short) aka Allan Bunch MS Access MVP - acXP WinXP Pro
Please post back to this forum so all may benefit.

Message posted via AccessMonster.com

 

[Phoig]

And the repair didn't do a blinkin' thing either. Barring a miracle solution
from someone, I'm going to have to either uninstall & hope a reinstall fixes
it or it'll have to be a full reformat & reinstall (a couple day proposition
given all the software I use.) Not happy, not in the least!

Okay, installed the hotfix provided via the link you kindly included. Sadly,
however, the problem still exists. I am running the Repair option from the
installation DVD but I don't have a whole lot of hope for that being
successful.

The HotFix does not install automatically. You have to download and install
manually.

Been incommunicado for a little while (stupid rotten Fallout 3 sucking up my
freetime... Anywho, yes, all the Service Packs & HotFixes have been
installed. First thing I did was head out to the Microsoft Update page & make
sure that I hadn't missed something.

You've installed the Office 2007 SP1 and the HotFix, correct?
http://support.microsoft.com/kb/960307
[quoted text clipped - 14 lines]
of databases that have languished for the last few months. Any ideas &
suggestions appreciated. Thank you!

--
RuralGuy (RG for short) aka Allan Bunch MS Access MVP - acXP WinXP Pro
Please post back to this forum so all may benefit.

Message posted via AccessMonster.com

 

[Phoig]

Well, looks like the uninstall/reinstall worked - I didn't have a lot of time
to do any serious coding, but I was able to invoke the Intellitype & not only
did Access not crash, but I did get my pop-ups. I had a "Unable to load DLL"
error in Acess itself when attempting to link two tables, but it didn't show
up again when I linked two other tables, so maybe that worked itself out too.
Here's hoping...