Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix Issue #610 (Error if last column of last row is empty) #620

Merged
merged 6 commits into from Sep 5, 2019
Merged

Fix Issue #610 (Error if last column of last row is empty) #620

merged 6 commits into from Sep 5, 2019

Conversation

striezl
Copy link
Contributor

@striezl striezl commented Sep 4, 2019

Ran into the troubles as described in issue #610 an pasted in solution as suggested there.

The value of variable "lv_rc" which is checked here comes from a previous READ TABLE statement in method get_cell(). Apparently ABAP sets the return value to "8", when the last line of a internal
table has been reached with TABLE KEY search, even though from my point of view the ABAP documentation (see attachment) is not 100% precise here. Nevertheless i can't see any reason why "8" (reached last row) should be treated different from "4" (did not last row) in this context.

In fact from my point of view the whole exception handling in method get_table after me->get_cell()... (lines 96 et seq.) is (or has become) pointless and could be removed. But for now I wanted to keep the change as minimal as possible.

2019-09-04_18-32-36

Copy link
Member

@larshp larshp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, thanks

@larshp larshp merged commit 1da0be9 into abap2xlsx:master Sep 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants