excel skips to another workbook for no apparent reason

It just seems strange that nobody else seems to be having this problem.  Usually when I Google any type of technical problem someone else is having the same issue.  But with this one, nada.

I have got the same issue and I can't seem to find the solution either. IT IS DRIVING ME NUTS!

If anyone has got any suggestion, please come forward with it.

Thank you.

It happens to me all day every day.

Having Excel run in multiple instances just to stop this minor bug is like using a cannon to kill a fly. The reason Microsoft stopped using multiple instances is because a single instance for all workbooks improves the user experience. Changing it therefore diminishes the user experience (aside from this bug)....At least for our company this fix would shutdown three-quarters of our engineering tools.

This is a valid concern. We have little VBA use here, though we do have dozens of worksheets referencing each other. However modern machines are so much faster than in the earlier days that I'm not sure the difference would be perceptible. You might consider trying it to see what impact exists. Perhaps you'd be surprised.

There's no question that a proper fix would have been a big help, but after this many years of a widely-discussed but unresolved problem, nobody is holding their breath for Microsoft action.

At any rate, for us this has been infinitely better than living with the problem. By the way we did not view it as a "minor bug." It was a complete work-stopper. When the sheet flip occurred without being noticed while typing, the new changes went into the wrong sheet. Depending on the workflow, this sometimes replaced cells. This was a constant hourly problem and led to lots of lost work and unexpected consequences.

Let me just say, again, that we were completely stuck with this problem for years, but the registry change has been a 100% solution for us. We don't have to do anything funny when opening files, and everything works pretty much the way it is supposed to. We have other Excel anomalies of course. But this one is really worth trying. There may be multiple issues involved -- other people may be stepping on different flavors of the bug -- but for us we went from 100% pain in the butt to 100% not an issue.

Having Excel run in multiple instances just to stop this minor bug is like using a cannon to kill a fly. The reason Microsoft stopped using multiple instances is because a single instance for all workbooks improves the user experience. Changing it therefore diminishes the user experience (aside from this bug).

If you have Excel sheets referencing each other without VBA then this should (haven't tested) slow the referencing down, and require you to update one workbook whenever you change the other. If you do use VBA then this puts an end to efficiently using "Workbooks(...)" to read other open workbooks.

At least for our company this fix would shutdown three-quarters of our engineering tools.

No, I didn't.  There were a couple of decent suggestions earlier in the string, but I haven't tried any of them.  I sure wish there was a simple remedy, as it is driving me crazy!