Share via

VBA changes in Excel 2013.

Anonymous
2013-05-23T17:12:07+00:00

I have a VBA routine that does not work when started from button on Excel spreadsheet but does work when I run it from the VBA program itself.  This VBA routine works perfectly in Excel 2010, 2007, and 2003.  Diagnostic suggestions are welcome.  I have looked in Walkenbach's book on VBA programming for Excel 2013 but I am not even sure what I am looking for.  I presume there is something in my routine that violates VBA rules for Excel 2013 but does not violate any rules for previous versions of Excel.

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

Answer accepted by question author

Doug Robbins - MVP - Office Apps and Services 323K Reputation points MVP Volunteer Moderator
2013-05-24T06:58:59+00:00

If you right click on the button in the worksheet and then on View Code, does it take you to the code that works when you run it from the Visual Basic Editor?

While I think that it is unlikely that it is something in the code that uniquely will not run in 2013, if you were to paste the code into a response here, others could try running it in 2013 to check you assumption.

Was this answer helpful?

0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Anonymous
    2013-05-27T13:57:47+00:00

    Yes when I right-click on button, I get the correct subroutine as the assigned macro.   The code executed is the complex solution of a model (too large to send).  With execution from the button, the solution does not converge;  with execution from the code, it does converge.  It might be something with the old solver I use but it surely is weird.

    Was this answer helpful?

    0 comments No comments