XLSREAD error line 260: Out of Present Range

My script which has been running fine for over a year developed a bug when I did a minor update to the Excel file that it was calling. Between the last time I used this script and now, I also updated to R2018a, but I can't imagine that would have a notable impact on this. Using Office Pro Plus 2016. I tried restarting multiple times, ensuring that all instances of Excel aren't running, but the problem persists. The full error is:

"Error using xlsread (line 260) Invoke Error, Dispatch Exception: Out of present range."

Any ideas would be much appreciated.

[Charles Latchoumane]

I know this is not a good fix but it worked for me, switch you xlsread to 'basic' (adding it in your xlsread option), this will force to read the xls. I also went through the steps to disable add in and graphic acceleration, untick ignore DDE programs (this all alone didn't do it).

Hope it helps whoever wants to move on quickly.

Answer 1

[Walter Roberson]

Is it possible that add-ons to Excel accidentally got turned on? https://www.mathworks.com/matlabcentral/answers/98261-why-do-some-excel-processes-fail-to-terminate-after-using-xlsread-xlswrite-or-xlsfinfo-in-matlab

[Jonathan Kellogg]

I've turned off the two pdf add-ons in Excel, restarted a couple times, confirmed that no Excel processes are running when I start Matlab and still have the issue with the same error code. Any other ideas?

[Walter Roberson]

Potentially related: https://www.excelforum.com/excel-programming-vba-macros/521380-out-of-present-range-error-using-excel.html and https://social.msdn.microsoft.com/Forums/sqlserver/en-US/af5d73cc-a7e4-4544-aa1c-555487c11d8d/out-of-present-range?forum=sqldataaccess

Could the minor change to the file have made it larger enough to have tickled a data type overflow or to have exceeded the Excel maximum rows limit ?

[Jonathan Kellogg]

Your question about row limits made me go triple check the csv version that there weren't excess rows or columns that had somehow gotten activated. While there weren't excess rows (<500), a bunch of hashtags had been introduced in some columns. I'm not sure quite how, but anyways, I deleted those columns (back to A-AT) and now it seems to load properly. Bizarre, but thank you for triggering me to go look at something I thought I had already solved. Still a bizarre error code though.

Hope you have a great weekend, Walter!