Tim has such a good point, but I have seen only two relevant posts
about what I think is a *major* inconsistency.  Surely others have
noticed it.  And surely the SQL Editor team knew Microsoft's standard
UI functions.  But it's amazing that no one has done more complaining
about the problem.

To recap the "standard" functionality for navigating and selecting
words:
  - CTRL-LeftArrow moves to the beginning of the previous word (or
current word, if the caret is in the middle of a word)
  - CTRL-RightArrow moves to the beginning of the next word
  - CTRL-Shift-LeftArrow selects all the characters to the beginning
of the previous word (or current word, if the caret is in the middle of
a word)
  - CTRL-RightArrow selects all the characters to the beginning of the
next word

This behavior has become consistent through all Microsoft products, and
is even consistent in the VS.NET IDE for nearly every language
supported--except SQL!

In the SQL editor, the behavior inside a comment is:
  - CTRL-LeftArrow moves to the beginning of the commented line,
ignoring word breaks & whitespace
  - CTRL-RightArrow moves to the end of the commented line, ignoring
word breaks & whitespace
  - CTRL-Shift-LeftArrow selects all the characters to the beginning
of the commented line, ignoring word breaks & whitespace
  - CTRL-RightArrow selects all the characters to end of the commented
line, ignoring word breaks & whitespace

...and the behavior inside a string (e.g. a single-quoted varchar
value) is:
  - CTRL-LeftArrow moves to the beginning of the string, outside the
quote, ignoring word breaks & whitespace
  - CTRL-RightArrow moves to the end of the string, outside the quote,
ignoring word breaks & whitespace
  - CTRL-Shift-LeftArrow selects all the characters to the beginning
of the string, outside the quote, ignoring word breaks & whitespace
  - CTRL-RightArrow selects all the characters to end of the string,
outside the quote, ignoring word breaks & whitespace

This needs to be fixed; it drives me nuts.
--Boris Nikolaevich