We've definitely found Excel 2016 somewhat more 'sensitive' shall we say about where it thinks it is and we find we need to be uber-specific about where things are. yay!!Īnd another thing we had to do was to make sure with all the buttons that we set the property 'TakeFocusOnClick' to false. However, we have opened a ticket with IBM to investigate a possible bug in Tm1 Client 10.2.2 FP7 and Excel 2016 where the selected worksheet gets changed unexpectedly.Īnd, I added the disable events and screen updating false to the start of each VBA subroutine, and that workaround fixed the issue (at least in one workbook). We use a drop down menu system using VBA which essentially does an Excel File/Open. Well, we never use the Application folder to open Excel files. right-click and some other workbook/sheet has the focus, type values in and they look to have not entered only to find them on another workbook that was actually active but not in view. My own experience (but could be my machine) is that when I open a workbook from Applications and work with it, I have some inexplicable things happen which sound similar i.e. Just out of curiosity, do you have the same behaviour when you run the macro after opening the workbook from applications vs opening from your local drive/network?

I am absolutely not asking for assistance on macro coding. Has anyone sees this type of issue when converting to Excel 2016 ? The error occurs in different situations and it not predictably reproducible. So stepping through the macro is not helpful. When the macro error occurs, I click the debug option and we get 'Can't execute in break mode'. But for some unknown reason, during macro execution Excel makes the first worksheet the active worksheet. The second worksheet should remain as the selected and active worksheet. Meaning I open the Excel file, select the second worksheet and click the Macro button to refresh the report, which executes a macro. Excel loses track of which worksheet is the active worksheet. The issue occurs in Workbooks with multiple worksheets. We get a message box Microsoft Visual Basic Run-time error '6': Overflow or Subscript out of Range or some other error that indicates Excel VBA is hosed.

Now, using Excel 2016, some macros error out (they run fine in Excel 2007). In our Development environment, we upgraded Excel 2007 to We have many production TM1 Perspectives Excel workbooks for input and reports that contain bespoke Excel VBA Macros. Windows Excel Client runs TM1 Perspectives 10.2.2 FP7 and Excel 2007 SP3 MSO 32-bit

Excel 2016 macro not working