Skip to main content

We have a Native COBOL program that reads excel files using COM Automation. After upgrading Microsoft Office from 2010 to 2016, the program takes about twice as long.

Processing the same 270 files before the upgrade took on average 3-4 seconds per file. After the upgrade it takes 7-8 seconds.

Are there any know issues with accessing Excel 2016?

The code is attached, any suggestions are appreciated.

Thanks,

Emi

We have a Native COBOL program that reads excel files using COM Automation. After upgrading Microsoft Office from 2010 to 2016, the program takes about twice as long.

Processing the same 270 files before the upgrade took on average 3-4 seconds per file. After the upgrade it takes 7-8 seconds.

Are there any know issues with accessing Excel 2016?

The code is attached, any suggestions are appreciated.

Thanks,

Emi

I do not believe that the performance issue has anything to do with the COBOL program or it's COM support.

I Googled "excel 2016 macros slow" and received a number of hits from other non-COBOL users that are experiencing the same slow-down.

One example would be:
stackoverflow.com/.../excel-macro-sometimes-incredibly-slow-in-excel-2016-but-not-in-excel-2010-high

Advice varies between different posts.

We have a Native COBOL program that reads excel files using COM Automation. After upgrading Microsoft Office from 2010 to 2016, the program takes about twice as long.

Processing the same 270 files before the upgrade took on average 3-4 seconds per file. After the upgrade it takes 7-8 seconds.

Are there any know issues with accessing Excel 2016?

The code is attached, any suggestions are appreciated.

Thanks,

Emi

I see all these complaints. Will try some of the best practices described here blogs.office.com/.../
Thank you for pointing me in the right direction.

We have a Native COBOL program that reads excel files using COM Automation. After upgrading Microsoft Office from 2010 to 2016, the program takes about twice as long.

Processing the same 270 files before the upgrade took on average 3-4 seconds per file. After the upgrade it takes 7-8 seconds.

Are there any know issues with accessing Excel 2016?

The code is attached, any suggestions are appreciated.

Thanks,

Emi

Turning off ScreenUpdating alone reduced the time per file to 2 secs!
invoke ExcelObject "setScreenUpdating" using by value 0.

We have a Native COBOL program that reads excel files using COM Automation. After upgrading Microsoft Office from 2010 to 2016, the program takes about twice as long.

Processing the same 270 files before the upgrade took on average 3-4 seconds per file. After the upgrade it takes 7-8 seconds.

Are there any know issues with accessing Excel 2016?

The code is attached, any suggestions are appreciated.

Thanks,

Emi

Turning off ScreenUpdating alone reduced the time per file to 2 secs!
invoke ExcelObject "setScreenUpdating" using by value 0.
Terms & ConditionsAccessibility statement