search

rubberduck-vba / Rubberduck

Every programmer needs a rubberduck. COM add-in for the VBA & VB6 IDE (VBE).
https://rubberduckvba.com
GNU General Public License v3.0
1.92k stars 302 forks source link

Code Inspections window will not open in Access 2007 #5428

Closed cTallakson closed 4 years ago

cTallakson commented 4 years ago

Rubberduck version information The info below can be copy-paste-completed from the first lines of Rubberduck's log or the About box:

Version 2.5.0.5244 OS: Microsoft Windows NT 6.2.9200.0, x64 Host Product: 2007 Microsoft Office system x86 Host Version: 12.0.6735.5000 Host Executable: MSACCESS.EXE

I am not sure why it thinks I am on NT... my PC is running Windows 10 Enterprise 10.0.17763 Build 17763

Description When I first used the add in a few days agao the code inspections window opened and functioned normally as far as I could tell. Suddenly yesterday I can not get the window to open. I tried opening it from the rubberduck dropdown and by changing the rubberduck settings to open the window on loading. Neither method opens the window.

I have tried reinstalling the add in, restarting the pc, and opening different databases. No 2007 Access databases will let me open this window. All other windows appear to work. The code inspection window also works in Excel.

To Reproduce Steps to reproduce the behavior:

  1. Open the VBE in Access 2007
  2. Click on RubberDuck
  3. Scroll down to Code Inspections
  4. Don't see new window

Expected behavior

  1. Open the VBE in Access 2007
  2. Click on RubberDuck
  3. Scroll down to Code Inspections
  4. Get a new code inspection window

Screenshots N/A

Logfile 2020-03-18 16:20:19.1793;TRACE-2.5.0.5244;Rubberduck.Common.LogLevelHelper; Rubberduck version 2.5.0.5244 loading: Operating System: Microsoft Windows NT 6.2.9200.0 x64 Host Product: 2007 Microsoft Office system x86 Host Version: 12.0.6735.5000 Host Executable: MSACCESS.EXE; 2020-03-18 16:20:19.1949;TRACE-2.5.0.5244;Rubberduck.App;Checking for legacy Smart Indenter settings.; 2020-03-18 16:20:19.3980;TRACE-2.5.0.5244;Rubberduck.Common.Hotkeys.Hotkey;Hotkey for the associated command Rubberduck.UI.Command.ComCommands.IndentCurrentModuleCommand was registered with id 49401; 2020-03-18 16:20:19.4196;TRACE-2.5.0.5244;Rubberduck.Common.Hotkeys.Hotkey;Hotkey for the associated command Rubberduck.UI.Command.Refactorings.CodePaneRefactorRenameCommand was registered with id 49361; 2020-03-18 16:20:19.4196;TRACE-2.5.0.5244;Rubberduck.Common.Hotkeys.Hotkey;Hotkey for the associated command Rubberduck.UI.Command.Refactorings.RefactorEncapsulateFieldCommand was registered with id 49400; 2020-03-18 16:20:19.4196;TRACE-2.5.0.5244;Rubberduck.Common.Hotkeys.Hotkey;Hotkey for the associated command Rubberduck.UI.Command.Refactorings.RefactorExtractMethodCommand was registered with id 49395; 2020-03-18 16:20:19.4196;TRACE-2.5.0.5244;Rubberduck.Common.Hotkeys.Hotkey;Hotkey for the associated command Rubberduck.UI.Command.Refactorings.RefactorMoveCloserToUsageCommand was registered with id 49377; 2020-03-18 16:20:19.4196;TRACE-2.5.0.5244;Rubberduck.Common.Hotkeys.Hotkey;Hotkey for the associated command Rubberduck.UI.Command.ComCommands.CodeExplorerCommand was registered with id 49381; 2020-03-18 16:20:19.4196;TRACE-2.5.0.5244;Rubberduck.Common.Hotkeys.Hotkey;Hotkey for the associated command Rubberduck.UI.Command.ComCommands.ExportAllCommand was registered with id 49405; 2020-03-18 16:20:19.4196;TRACE-2.5.0.5244;Rubberduck.Common.Hotkeys.Hotkey;Hotkey for the associated command Rubberduck.UI.Command.ComCommands.FindSymbolCommand was registered with id 49388; 2020-03-18 16:20:19.4196;TRACE-2.5.0.5244;Rubberduck.Common.Hotkeys.Hotkey;Hotkey for the associated command Rubberduck.UI.Command.ComCommands.IndentCurrentProcedureCommand was registered with id 49404; 2020-03-18 16:20:19.4196;TRACE-2.5.0.5244;Rubberduck.Common.Hotkeys.Hotkey;Hotkey for the associated command Rubberduck.UI.Command.ComCommands.InspectionResultsCommand was registered with id 49314; 2020-03-18 16:20:19.4196;TRACE-2.5.0.5244;Rubberduck.Common.Hotkeys.Hotkey;Hotkey for the associated command Rubberduck.UI.Command.ComCommands.ReparseCommand was registered with id 49382; 2020-03-18 16:20:19.4196;TRACE-2.5.0.5244;Rubberduck.Common.Hotkeys.Hotkey;Hotkey for the associated command Rubberduck.UI.Command.ComCommands.TestExplorerCommand was registered with id 49257; 2020-03-18 16:20:19.5467;TRACE-2.5.0.5244;Rubberduck.VBEditor.WindowsApi.SubclassManager;Subclassed hWnd 0x000306FA as CodePane.; 2020-03-18 16:20:21.9019;DEBUG-2.5.0.5244;Rubberduck.UI.Command.MenuItems.ParentMenus.ParentMenuItemBase;(48604061) Executing click handler for menu item 'Code &Inspections', hash code 43888289; 2020-03-18 16:20:21.9019;TRACE-2.5.0.5244;Rubberduck.UI._DockableWindowHost;IOleObject::DoVerb() called with iVerb OLEIVERB_SHOW.; 2020-03-18 16:20:21.9176;TRACE-2.5.0.5244;Rubberduck.Common.Hotkeys.Hotkey;Hotkey for the associated command Rubberduck.UI.Command.ComCommands.IndentCurrentModuleCommand was registered with id 49257; 2020-03-18 16:20:21.9176;TRACE-2.5.0.5244;Rubberduck.Common.Hotkeys.Hotkey;Hotkey for the associated command Rubberduck.UI.Command.Refactorings.CodePaneRefactorRenameCommand was registered with id 49382; 2020-03-18 16:20:21.9176;TRACE-2.5.0.5244;Rubberduck.Common.Hotkeys.Hotkey;Hotkey for the associated command Rubberduck.UI.Command.Refactorings.RefactorEncapsulateFieldCommand was registered with id 49314; 2020-03-18 16:20:21.9176;TRACE-2.5.0.5244;Rubberduck.Common.Hotkeys.Hotkey;Hotkey for the associated command Rubberduck.UI.Command.Refactorings.RefactorExtractMethodCommand was registered with id 49404; 2020-03-18 16:20:21.9176;TRACE-2.5.0.5244;Rubberduck.Common.Hotkeys.Hotkey;Hotkey for the associated command Rubberduck.UI.Command.Refactorings.RefactorMoveCloserToUsageCommand was registered with id 49388; 2020-03-18 16:20:21.9176;TRACE-2.5.0.5244;Rubberduck.Common.Hotkeys.Hotkey;Hotkey for the associated command Rubberduck.UI.Command.ComCommands.CodeExplorerCommand was registered with id 49405; 2020-03-18 16:20:21.9176;TRACE-2.5.0.5244;Rubberduck.Common.Hotkeys.Hotkey;Hotkey for the associated command Rubberduck.UI.Command.ComCommands.ExportAllCommand was registered with id 49381; 2020-03-18 16:20:21.9176;TRACE-2.5.0.5244;Rubberduck.Common.Hotkeys.Hotkey;Hotkey for the associated command Rubberduck.UI.Command.ComCommands.FindSymbolCommand was registered with id 49377; 2020-03-18 16:20:21.9176;TRACE-2.5.0.5244;Rubberduck.Common.Hotkeys.Hotkey;Hotkey for the associated command Rubberduck.UI.Command.ComCommands.IndentCurrentProcedureCommand was registered with id 49395; 2020-03-18 16:20:21.9176;TRACE-2.5.0.5244;Rubberduck.Common.Hotkeys.Hotkey;Hotkey for the associated command Rubberduck.UI.Command.ComCommands.InspectionResultsCommand was registered with id 49400; 2020-03-18 16:20:21.9176;TRACE-2.5.0.5244;Rubberduck.Common.Hotkeys.Hotkey;Hotkey for the associated command Rubberduck.UI.Command.ComCommands.ReparseCommand was registered with id 49361; 2020-03-18 16:20:21.9176;TRACE-2.5.0.5244;Rubberduck.Common.Hotkeys.Hotkey;Hotkey for the associated command Rubberduck.UI.Command.ComCommands.TestExplorerCommand was registered with id 49401; 2020-03-18 16:20:21.9176;TRACE-2.5.0.5244;Rubberduck.UI._DockableWindowHost;IOleObject::DoVerb() called with iVerb OLEIVERB_SHOW.;

Additional context I do have Access 2007 (full version) AND Access 2016 (runtime) installed.

cTallakson commented 4 years ago

RubberduckLog.txt

retailcoder commented 4 years ago

Thanks for the report - sometimes the VBE behaves funny with dockable toolwindows; look for a toolwindow with ridiculous width or height, e.g. you barely see an edge of a border but then you can still grab it & drag to resize. Or if it's not docked then it might be floating on a 2nd monitor, possibly behind another window?

cTallakson commented 4 years ago

Is there a way to force it to launch docked? I have scoured both my monitors and haven't even found an edge.

retailcoder commented 4 years ago

In the Window Settings tab of the settings dialog (from the Rubberduck menu on the main VBE commandbar), you can pick toolwindows to show at startup - tick the "Code Inspections" box and it should be visible at startup.

cTallakson commented 4 years ago

Thanks for the report - sometimes the VBE behaves funny with dockable toolwindows; look for a toolwindow with ridiculous width or height, e.g. you barely see an edge of a border but then you can still grab it & drag to resize. Or if it's not docked then it might be floating on a 2nd monitor, possibly behind another window?

This did lead me to finding the window. It was actually where a third monitor would have been. After setting my background to white, hiding my icons, and minimizing all other windows I opened the code window and still saw nothing. I went around each edge blindly grabbing and on the far right it pulled it back on screen from off my second monitor. I guess I should reword the bug to try and ensure that the window launches on screen?

cTallakson commented 4 years ago

In the Window Settings tab of the settings dialog (from the Rubberduck menu on the main VBE commandbar), you can pick toolwindows to show at startup - tick the "Code Inspections" box and it should be visible at startup.

Actually did this and had the same results. Apparently no mater what caused it to start, any access vbe that launched that window launched it completely off my right monitors right edge.