what to do with vba codes when moving from Excel 2010 to 2016

[lynnsong986]

Hello, my company is finally moving from office 2010 to 2016...can someone please let me know how to handle the upgrading when it comes to all the codes residing in different workbooks including personal.xlsb and .xlam? Do I need to export everything then import them again or they will just work without me doing anything? I mean after the upgrading, do I need to re-create the personal.xlsb and all of my .xlam workbooks?

thanks so much in advance.
Lynn

 

[rlv01]

I just moved my 2010 personal.xlsb file straight over. No issues. At this point I have a lot of experience moving vba functionality from 2010 to 2016. Most macros work without issue, but once in awhile you run into something that makes you have change the code to restore functionality. You don't need to mess around with your 2010 xlsm files unless testing under 2016 indicates a problem. The larger problem I've had is not with 2010 vba macros not working under 2016. Instead, the majority of the problems have been large performance hits with macros that do a lot of looping though cells. I have any number of macros that ran really fast in 2010 that ended up being horribly slow in 2016, so I had to re-code not because the macro didn't work, but to try to speed it back up to something acceptable to my user base.

 

[lynnsong986]

Thank you so much for replying. Hopefully everything g will still work for me with 2016 version!