Changing Application.DisplayFormulaBar prevents cell edits

In my Excel application, I hide the FormulaBar (and ribbon, status bar, headings, scroll bar, etc.) using the following statement on Workbook Activate event:

Please Login or Register  to view this content.

Of course, I also have the opposite statement on the Workbook Deactivate event.

When I open the workbook, the formula bar hidden (which is good) but I now can't make any edits to cells!!!???

I can click on the cell and navigate from one cell to another using the keyboard or mouse and can even copy the values from the cells (and paste elsewhere) but I can't edit anything.
Clicking on the keyboard doesn't do anything, which is odd because the cells are not locked or anything.

The problem goes away when I make the formula bar visible again by manually checking the box under Excel options.
If I do this once, everything works fine again irrespective of whether the formula bar is visible or not.

Please help!
PS: The irony is I posted yesterday asking how I can achieve this effect (allow copy-paste without edits) for a different application and now Excel shows me it is possible, but when I don't want it and don't understand how / why it's happening. I'm almost convinced Excel is just toying with me!

Can you post all of your code, just changing the .displayformulabar property shouldn't restrict cell editing.

Ragulduy - thank you for your response. Here's my code:

Please Login or Register  to view this content.

The opposite code is on the Deactivate event.

What version of excel are you using? In 2010, at least on my machine, running that macro doesn't restrict cell editing.

Originally Posted by ragulduy

What version of excel are you using? In 2010, at least on my machine, running that macro doesn't restrict cell editing.

Excel 2013

Originally Posted by ragulduy

What version of excel are you using? In 2010, at least on my machine, running that macro doesn't restrict cell editing.

Excel 2013

I can now confirm that the issue persists on my Excel 2013 but works fine on a colleague's Excel 2010.
Darn Microsoft!

Hi,

I can confirm this also happens to me, I'm raising it through the Partners Technical area.

regards
Seán