I'm not sure you saw the ongoing discussion from my later thread
on the same situation starting with message  #7416 . . . with the
working solution --at that point--that is in Message #7430.

The method you just listed DOES sound like a very simple way to
address the cell locations, thank you. I'm going to re-evaluate my
code to see if it would refine the process.

I know everyone here in the group  is busy and volunteering their
time, so perhaps people missed the part  that I was unable  to answer
in my code. I'm very grateful for all the help  I get here, anyway.
It's a very very minor thing, but I am curious if it can be
handled. Unless I misunderstood you, this particular part of the
question wasn't answered by your suggestion, either. That part is:

--copied from previous message #7430:
The only thing I haven't been able to figure out is a very very
minor thing. That is . . . on a supervisor's Team sheet  if a cell
in Column 1 is ALREADY SELECTED and the user  clicks on it, nothing
happens, because the selection hasn't CHANGED--and the code is
firing from the SelectionChange event. So, they have to select
another cell. But since the sheets are protected  from
userinterface, they still can't change  the cell directly. I
couldn't see a way around that part, but it does happen when a sup
opens up a page . . . and selects the cell they had last selected.
The non-computer types might get a bit frustrated with that, but
that might just be part of it, anyway.<----end of copied paragraph

I'm interested in that part. Any ideas?