What kind of sorcery is this? I was doing some basic cleaning up of a large (30MB) file and noticed something inexplicable. I opened the Name Manager window and saw something that didn't look right: my "cad_sortcol_CP" Named Range apparently referred to cells $Y266:$Y50264:
That didn't seem right at all (it usually referenced rows 2 to like 50,000 or something around there. Then I discovered something even weirder. Without changing anything at all in the file, I just put my cursor in a different cell (in row 390), and re-opened the Name Manager window and saw this:
WTF? Tried once more, putting cursor in a cell in row 2820, and re-opened Name Manager:
What on earth is going on here? Why would a named range definition possibly change merely because I put my cursor in a different row(??) You might notice that the starting-row for the 3 named ranges seems to be 29 rows lower than wherever my cursor is. No idea what that could be about. But the chief weirdness is that the range reference would change AT ALL(!?)
(FYI: these 3 named ranges I use in a sorting function in VBA....and the weird thing is that I run the VBA every day, and it has always worked correctly; but this is weirding me out because I don't understand it. Any ideas?)
That didn't seem right at all (it usually referenced rows 2 to like 50,000 or something around there. Then I discovered something even weirder. Without changing anything at all in the file, I just put my cursor in a different cell (in row 390), and re-opened the Name Manager window and saw this:
WTF? Tried once more, putting cursor in a cell in row 2820, and re-opened Name Manager:
What on earth is going on here? Why would a named range definition possibly change merely because I put my cursor in a different row(??) You might notice that the starting-row for the 3 named ranges seems to be 29 rows lower than wherever my cursor is. No idea what that could be about. But the chief weirdness is that the range reference would change AT ALL(!?)
(FYI: these 3 named ranges I use in a sorting function in VBA....and the weird thing is that I run the VBA every day, and it has always worked correctly; but this is weirding me out because I don't understand it. Any ideas?)