Well, the implementation may be wrong and simply omitting to consider a defined range’s row of column headers.
That didn’t work however I notice something new & odd is happening that kind of works as a fix.
If I sort on column A: the row is still on the top spot.
If I then sort on column B: same thing happens
If I then sort on column C: sorting works
If I then go back to sorting on column B: sorting works
& then if I sort on column A again: sorting works
The correct sorting of either column A or B only works if I first sort column C.
If do you need to know what happens in your document, share a copy of it, annonymizing the data.
2 Likes
This is getting weirder & weirder, but now the issue is no longer present.
All rows are now properly sorting themselves.
The extension installs an advanced version of the macro code I introduced in this thread. It comes with a 2-button toolbar without touching the existing user interface.
The macro detects a database range at the active cell and handles most of the properties of that database range and any existing sort descriptor of that database range where this forum’s code handled column labels only. The only disregarded sort options are “copy sort results” and “sort columns” which would be rather confusing.
When there is no database range at the active cell, the code dispatches the built-in sort command. The built-in command selects the sort range after sorting, keeping the position of the active cell. My own code does not change the selection because I don’t know how to keep the position of the active cell within a range selection. A jumping cell cursor is rather confusing in this context.