Handle idiosyncrasy of .UsedRange on empty sheet #26
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Instead of returning something relatively intuitive, like Nothing,
when .UsedRange is called on an empty Worksheet, Excel 2019 instead
returns Range("$A$1").
Thus, since the code tries to reduce the ExportRange to the bounds
of .UsedRange when entire rows and/or columns are selected, if
Selection encompasses $A$1 then it will erroneously set ExportRange
to Range("$A$1"), instead of Nothing.
This commit fixes this behavior by running an explicit check for
.UsedRange == Range("$A$1") and IsEmpty(.UsedRange). If the
sheet is empty, then ExportRange will be set to the appropriate
Nothing.