I'm experiencing a problem similar to KB article 829059 (Visual Basic Editor may open without menus or toolbars in Outlook 2007 or in Outlook 2003) except it's happening in Access 2010. I haven't been able to verify whether this is related to the Editor being maximized. It is happening however when Access is running and the Editor hasn't been opened. I'm currently trying the method of "Clear All Breakpoints" which I read can be a fix. Is there an official fix for this problem? So far, I see no acknowledgement of this being an issue in Office 2010.

Does the method of "Clear All Breakpoints" work?

How many database are affected? When did you find this behavior started? What happened around that?

Is there any special condition to trigger this behavior?

Just in case, the default short cut key to open the VBA Editor is "Alt + F11", is it possible that you or some tools that has sent the command to the system?

See if we can use the Process Monitor to capture more details about what happens when this behavior occurs.

Download and instructions: http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx 

I'm not sure at this point if "Clear All Breakpoints" works. Behavior started in the last couple weeks possibly after some code changes. It's happening on one database (same issue on 2 different machines).

It may well coincide with machine lock/unlock logon. I never made the connection until I read the KB article referenced above.

Relevant? background on program. Program uses a Form Timer Event in which the Form is typically left open and running overnight unattended.  The event based on conditions will fire a MsgBox. It's not unusual to unlock a machine in the morning and have the MsgBox waiting for input. After the problem started occurring I inserted some debugging code to see if there was any correlation between certain conditions and the VBA editor opening and I didn't find any. Just like the KB article the Editor opens with no menus or toolbars. There is no error and no line of code highlighted.

I have a copy of Process Monitor if needed.

"Clear All Breakpoints" did not resolve the problem. Assuming I have Procmon running when this occurs, is there a process/event to look for that indicates that the editor is being opened?

Just in case, the default short cut key to open the VBA Editor is "Alt + F11", is it possible that you or some tools that has sent the command to the system?

See if we can use the Process Monitor to capture more details about what happens when this behavior occurs.

Download and instructions: http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx