• Hi All

    Please note that at the Chandoo.org Forums there is Zero Tolerance to Spam

    Post Spam and you Will Be Deleted as a User

    Hui...

  • When starting a new post, to receive a quicker and more targeted answer, Please include a sample file in the initial post.

Is there a compatibility issue with excel 2013 and 2016?

Hi Folks,

for my work purpose I have created few macros that I may need to use daily basis. we recently upgraded to office 2016 and since then the Excel crashes and i'm unable to run my macros which I was able to run on Office2013. Please help me understand if it is only me or others also facing the same issue. if yes please help me solve this

Thank you in Advance
 
There should not be compatibility issue in terms of macro. I run macro coded in Excel 2003 (or even older) on Excel 2016 without issue.

Most compatibility issue will occur when you run code written in newer version in older version. Often caused by new function/object/method introduced in newer version.

Can you confirm if Office 2016 is installed in 32 bit or 64 bit (not the OS, but the Office itself) and what mode it was for 2013?

Certain add-in coded in VB6.0 will have issue with 64 bit installation.
 
Thanks for offering help! Chihiro


I have 64 bit office 2016, that was upgraded from 64 bit office 2013.

The problem I'm facing is:

I have a macro that populate templates several tables in multiple files from a database (Excel flat file). The macro works fine in excel 2013 version but when I ran the same in excel 2016, it populate data for 3-4 templates and then excel crashes (when I ran the same in Debug mode it worked but crashes after removing breakpoints).

About the template: It is a .xlsm file that has cell change macro. But I'm disabling the events after I open template, assuming events could cause excel to crash.

Please let me know if this explain's my issue.

Thank you
Anantha
 
Sounds more like memory issue rather than code specific issue.

Try turning off all the unnecessary things (animations, calculations, etc etc).

If using Object variable, set it to nothing as soon as it's not required.

Not sure without code and sample workbook.
 
Back
Top