A family of Microsoft spreadsheet software with tools for analyzing, charting, and communicating data.
What happens if you temporarily disable all add-ins in Excel?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
This problem with the Visual Basic editor began two or three updates ago (about a week to ten days ago):
As I am typing a line of code, the line updates and causes the cursor to jump to the left (or end of the line to jump right, past the cursor) so that typed characters go into the wrong place; space I type are automatically removed before I can type the next word in the line; After successfully completing a line, I hit Enter, the line first updates causing the end of the line to jump to the right of the cursor so that the line breaks before the end and triggers a syntax error popup. On creating a Sub or Function, the update-while-typing generates the bracket set before I'm done typing, again causing characters to go into the wrong place.
I installed the latest updates of Operatiing System—Currently MacOS Big Sur Version 11.6.4— and of Microsoft Office 365. Still the problem persisted. restarting the computer did not help.
I experimented with different configurations of editor preferences, and none corrected the problem. At one point I thought that the absence of the RibbonX_Code module in my Project Modules was to blame. I put one there and for a brief time that seemed to work, but it didn't. Within minutes the problem was back.
I am fairly certain this problem was generated by a recent update to the Microsoft 365 software. Can you fix it?
A family of Microsoft spreadsheet software with tools for analyzing, charting, and communicating data.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
What happens if you temporarily disable all add-ins in Excel?
Thanks. I have only two—Analysis ToolPak and Solver Add-in. I deactivated both with no effect on the problem.
You can use Time Machine to restore Microsoft Excel.app to a previous build and then test to see if the problem persists or goes away with the older build.
Thanks—I have no code with Application.OnTime.
Do you have any code running that uses Application.OnTime? If so, that might explain the behavior.