Possibly you could use "Cancel=True" to prevent the normal action of the end
key.

Sorry. No luck. I tried it at the beginning of the sub and at the
end. No effect. I found it interesting that the "=" did not pop up
the applicable entries from "intellisense" or whatever it is called -
(like other properties do, yet it does not stumble over the line.

Perhaps a scan through the Ctrl-SpaceBar list might turn up another
candidate.

I don't think the Worksheet_Change event has the Cancel option.

without an explicit object, the compiler didn't choke on, simply

Cancel=True

But, interestingly enough, Help Sez it is only a property for Command
Buttons - a.k.a. indicating that it cancels [the UserForm, I guess).

Trying some appropriately sounding objects (Application...) resulted
in "Object does not support..." errors.
I just won't do that End thing...

End followed by an arrow  is a normal key  sequence in Excel that are designed
to function  just like a Ctrl-Arrow and bring you, as you said, to the next
"data edge". It does not do this in the VBA Editor or anywhere else; it's an
Excel spreadsheet-ism.

So if you don't want it to behave that way, I guess your question is: "Is
there some way to disable this functionality?" Because Worksheet_Change or
not, End+Arrow works the way you describe. This is not a bug or anything
like that; it's by design. And again, it would happen that way whether you
have a Worksheet_Change event or not. It has nothing to do with your code.

Knowing that, how would you like to see it handled? Do you want to disable
it under all circumstances in your workbook? Or, knowing that it's by
design, is it OK now? What would you like to see?

3 or 4 coments in the text below......................

This is the same thought I was thinking after
thinging for a while after posting.
I was testing my algorithms and wanted to "stay in the cell" in
order to try all the potential input conditions. I managed test
groups (hardware) for the last ten years or so. Unthingingly, I
continued to do so, then decided to move after an End-keypress. This
is normally not expected, so is clearly a "If it hurts when you do
that, then Don't do that" solution.

This should answer the rest of your questions.

The auto-filled text has only three possible values (Wide, Mid,
Narrow), however, depending on some conditions, only 1, 2, or 3 of
those are valid for a given situation (quite a complex algo). I sense
those conditions and limit the entry  to the appropriate ones -
displaying a MsgBox when user goes astray or suffers from fat-finger
syndrome. I also wanted to make things easy by auto-completing the
entries (fortunately the 1st characters allowed  this). No ammending
the auto-complete allowed.
I could have used Validation, and quite honestly, hadn't thought
of that until just now, but wrestling with modifying the Validation
list probably is no more complex than the array I search to find the
valid combinatins.
The End key  fires the Worksheet_Change Sub just fine, but Return
should normally be used exclusively. I also go to he trouble of
changing the "MoveDirectionAfterReturn" to "vbToRight" since data  is
normally entered in rows. And going back to vbDown upon Exiting Excel.

Hmmm... I'll have to understand this feature:
> If you want to edit the cell contents rather than move
> off the cell you have to press F2.

... But the end  key is a shorter reach on this laptop (:-)