You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a solution which reads one work sheet in a file with multiple sheets and updates one work sheet in that same file I got an error reported for an uncaught CX_SY_CONVERSION_NUMBER exception just as I was leaving yesterday.
Initially I thought it was as simple as a problem with a value in the sheet we read and would be a quick fix this morning, but after some debugging I found the reason - and I can understand that this isn't something the users can understand or fix themselves.
The error occurs because one of the sheets (not the one we are interested in) has a row where LS_ROW-SPANS contains multiple ranges:
"1:1023 1026:2046 2049:3072 3074:4095 4097:5120 5123:6143 6146:7166 7169:11264 11267:12287 12290:13310 13313:14336 14338:15359 15361:16384"
I suppose the processing technically can be handled by splitting at space first and then enclosing the current code in another WHILE ... ENDWHILE, but I haven't analyzed it in detail yet to see what kind of trouble that may lead to.
I don't think I can share the original file, but I will ask the business what I need to remove/mask before I can share.
The text was updated successfully, but these errors were encountered:
In a solution which reads one work sheet in a file with multiple sheets and updates one work sheet in that same file I got an error reported for an uncaught CX_SY_CONVERSION_NUMBER exception just as I was leaving yesterday.
Initially I thought it was as simple as a problem with a value in the sheet we read and would be a quick fix this morning, but after some debugging I found the reason - and I can understand that this isn't something the users can understand or fix themselves.
The error occurs because one of the sheets (not the one we are interested in) has a row where LS_ROW-SPANS contains multiple ranges:
"1:1023 1026:2046 2049:3072 3074:4095 4097:5120 5123:6143 6146:7166 7169:11264 11267:12287 12290:13310 13313:14336 14338:15359 15361:16384"
I suppose the processing technically can be handled by splitting at space first and then enclosing the current code in another WHILE ... ENDWHILE, but I haven't analyzed it in detail yet to see what kind of trouble that may lead to.
I don't think I can share the original file, but I will ask the business what I need to remove/mask before I can share.
The text was updated successfully, but these errors were encountered: