Unable to open code window

MarkHammer

Registered User.
Local time
Today, 15:29
Joined
May 6, 2008
Messages
17
With both Access 2007 and 2010 I am unable to open the VBA code editor. In each, I click Create >> Module or VBA Code and Access goes into a non-responding loop.

Access 2003 works OK.

Advice appreciated.

Mark Hammer, Spokane, WA, US.
 
I'm not familiar with the symptom but have you selected your "Trusted Location" yet?
 
Haven't done anything with trusted locations. Is this a necessary prerequisite for using Access 2007? The procedures at technet for configuring them look pretty involved to me.
 
:confused:OK, did the trusted locations. Still have same problem.

Why would BOTH Access 2007 AND Access 2010 refuse to open a code window, when Access 2003 works just fine?

Running Windows 7 Professional 64-bit, 8 megs RAM.
 
I don't know what is causing your issue. Do you get the same symptom with <ALT> F11 or ^G?
 
I've seen something similar before. Try to open with the shift bypass, go into a form's design view and click the ellipses to go into the form's module.
 
Tried repairing the Office 2007 install; same problem.

Next, uninstalled both Office 2010 and Office 2007, then reinstalled 2007. Same problem with Access 2007: any attempt to open the code window goes into a nonresponding loop.

Also tried opening with the shift bypass, then using the ellipses from form design view; same response.
 
Is your patch level on all of the software up to date? I really do not know what else to try. How about temporarily disabling all of the autoloaded software in msconfig?
 
Did you let the loop run and give it time to 'think'?

Go to the uninstall programs window and see if there are other things installed, like maybe the runtime, or anything you don't recognize.
 
Thanks for the good ideas.

Updates current: Win 7 Pro SP1, Office 2007 SP3, Windows Update is happy.

Let the hung loop run for 50 minutes; still hung.
 
hahah, thats a lot of thinking.

Did you check for the runtime or other stuff you don't recognize? That got me once.
 
I would also try disabling everything in run>msconfig as a test.
 
I am old enough to remember when 8 MB was considered bucketloads of RAM for a PC.

Indeed when I first got into computers it was with a Digital PDP11 mainframe. It ran everything at the university had a huge one MB of RAM if I remember correctly.
 

Users who are viewing this thread

Back
Top Bottom