Is this a 2013 bug? Or is it me?

[scenario]

My file works in 2010 but not in 2013. Is it a bug or is it me? Any ideas?


I created a financial calculator using simple VBA and ActiveX controls that works perfectly when opened in Excel 2010, but not in 2013. I am looking for any thoughts regarding the problem which I will describe in more detail below.

Summary:
(1) I have ActiveX spin controls linked to most of my number input cells.
(2) I have VBA code to start the spreadsheet in full screen mode.

Problem:
When I open the file in Excel 2013, I can enter data into cells UNTIL I use the spin controls. Once I use any of the spin controls, I lose the ability to type values into the cells. It's as if the cells are locked (they are not).

Notes:
(1) My original workbook had multiple tabs, macros, etc. but... I have been able to replicate the problem in a simple demo spreadsheet (picture below) with one value, one spin control, and one line of code in Workbook_Activate.
(2) The problem does not occur in Excel 2010, only 2013.
(3) I have also been able to replicate the problem with other lines of code in either Workbook_Activate or Workbook_Open. The lines of code involved maximizing the screen, hiding scrollbars, hiding tabs, hiding the command bar, and others.

Attachments:
- I am including screen shots of my simple demo file below. One showing the single input with spin control; the other showing the simple line of code in This Workbook/Workbook_Activate.

Any thoughts on this are greatly appreciated.
In a perfect world, the problem will be the result of a simple mistake on my part that you will be able to correct me on quickly.

Thanks in advance.

 

[ChrisM]

Any chance you are using 32bit 2010 and 64bit 2013? Maybe that is the issue.

 

[scenario]

Any chance you are using 32bit 2010 and 64bit 2013? Maybe that is the issue.

Hi. Thanks for your response Chris.

Both versions are 32 bit and running on the same computer.

 

[ChrisM]

can you post your spin button code?

 

[scenario]

can you post your spin button code?

I didn't code the button. Just used the property settings.
As I think about your question, I haven't tried coding spinup and spindown.
Might have to look at whether that makes a difference.
But if so, interesting that it works fine in 2010.
And why would it only hang up when I add code to Workbook_Activate or Workbook_Open?

Am going to add spinup/down now and see what happens.

 

[circledchicken]

Hmmm...I tried it and I get the same behavior as you - it definitely seems buggy.

Are you using ActiveX controls for a specific reason?
The equivalent form controls don't seem to have the same problem.

 

[scenario]

I thought about switching to the Form Control version, but I was putting off looking into it because...
I have quite a few buttons in the spreadsheet I created (30-40).
And I've written code to change minimums/maximums on most of these buttons based on other changes in the spreadsheet.
But I may have to consider it.

 

[scenario]

I just tried coding the button to increment instead of just using the properties. Still have the same problem.

 

[Michael M]

Why have you got the Workbook activate code in the sheet module ??
Try it in "This Workbook" module

 

[circledchicken]

I think another solution if you don't want to change to form controls is that rather than going to full screen, adjust your code to hide the ribbon and formula bar instead for a similar effect. Doing it that way doesn't cause the same issue.