I recently spent several frustrating hours trying to discover why my Visual Basic Editor (VBE) lost all of its menus and toolbars in Microsoft Access. The same happens in the VBE of all Office products.
I was using a Surface Pro 3 upgraded to Windows 10 and with Office 2013. I’ve used the VBE many times with this set up, and I could not see what had changed.
Googling brought up several similar issues for Word and Excel VBE, but those involved corrupt registry keys. I tried modifying the registry. I tried Repairing my Office install. I tried uninstalling and reinstalling Office. Nothing worked.
Another thing I noticed was that I could not Restore the VBA window. I could Minimize and Maximize but not Restore. And then I discovered that I couldn’t Restore ANY windows. This made me realize (finally) that I was in the Windows 10 new Tablet Mode. Tablet mode doesn’t allow Restored windows.
I set my Surface to Desktop Mode and all the VBE menus and toolbars appeared as normal.
I’ve reported this to Microsoft and they can reproduce the problem. I’ve been assured that a fix will be forthcoming since the bug affects so many products.
Interestingly, I use Open Live Writer to edit these blogs. It used to be a Microsoft product, but they released it to Open Source. I had the same issue with the Ribbon not appearing when I was in Tablet Mode, so the problem may be more wide-spread than the VBE of Office.
As far as I know, it affects all versions of Office, but only those Window 10 installs that have a touch screen.
I’d love to hear if anyone out there finds an exception, or if any other programs are affected by Tablet Mode.
7 comments:
Thank you for posting this, Roger. It's a big reason not to upgrade my Surface Pro to Win10.
@kgander: but Roger posted the workaround: "I set my Surface to Desktop Mode and all the VBE menus and toolbars appeared as normal."
Very true, Anon. I wouldn't use this as a reason to avoid upgrading. The workaround is trivial...make sure you're on the Desktop when using Office. I just don't want people to waste the time and energy I did until I discovered the solution. Hopefully, they'll slipstream a fix and this issue will be moot.
Gotta love your blog man!! You save my Job several times..
Hi Roger,
just to let you know that you've not been the only one with that problem:
Some months ago it came up in several Access forums (en, it, de) and I could answer it 2-3 times after myself finding the solution in this thread.
cu
Karl Donaubauer
Thanks Karl. Should have asked you first! I did a google search and didn't turn that up.
Thank you! That had me more than bit frustrated....
Post a Comment