excel skips to another workbook for no apparent reason

Anonymous
2015-01-24T17:08:03+00:00

Quite often when I try to make an entry into a cell excel appears to freeze.  If I hit the enter button it skips to a different workbook.  There are no links between the two workbooks.  This has been happening for some time and is very annoying.

Microsoft 365 and Office | Excel | For home | Windows

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.

0 comments No comments

130 answers

Sort by: Oldest
  1. Anonymous
    2019-02-14T19:02:30+00:00

    I can't believe it's 2019 and this issue is still a thing

    I get it at random intervals, from three different computers, one of them with W8, the other two with W10.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2019-02-15T15:21:48+00:00

    I'll add my name into the hat. I've been having this issue for many years. It happens every day and it's incredibly annoying.

    it's shocking that this hasn't been fixed yet with the amount of money we've all paid for Office in the 5 years since this was reported...

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2019-02-20T16:10:29+00:00

    Same problem here. It's driving me crazy.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2019-02-20T16:38:59+00:00

    Tumbleweed from Microsoft. 

    I feel like they are treating me like a muppet. Happens because I have no recourse.... A lot of things wrong here.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2019-03-12T14:55:32+00:00

    Just another drop in the bucket here.

    Excel has been doing this to me somewhat rarely for the last 2 years (5-10 times a month rough average).  I ignored it for a while as I only use excel for very basic spreadsheets but after deciding to look it up I realized it was a much bigger (and older) problem.  I can't believe Microsoft hasn't deigned to comment on this issue yet.  Now I am curious to see how long we can keep this thread up.

    Was this answer helpful?

    0 comments No comments