It would not, of course, be "sad" if Word were NOT developed by cretins. What
is "sad" is that one so muddled in her thinking that her sentences mean quite
the opposite of what she intends presumes to give advice in a help forum.
Maybe if one could express oneself in grunts and gestures here, you could
avoid contradicting yourself and just appearing stupid.

Perhaps you could acquire a mentor who could convey the concept of
unintended consequences in complex systems and explain to you how this
concept accounts for generally well-designed computer programs sometimes
doing unexpected and ridiculous things.

"Jezebel" wrote:

Wow, talk about flailing in the dark! It might indeed, if it were develped
by cretins. But sadly, it was not, so you're way out of your milieu.



"srdiamond" wrote in message
...
That depends on how you define "detect." Of course Word does not represent
how hard the keys are pressed. But Word might very well cause some
computer
activity after a tab that occupies the central processor so it doesn't
detect
a press unless it is longer than normal. This possibility that you seem
too
obtuse to glean is not only a logical possibility but seems to correspond
to
the facts.

"Jezebel" wrote:

There's no way Word can detect how hard you press the keys.



"srdiamond" wrote in message
...
This sounds like a hardware problem but it is a Word problem
experienced
in
connection with Tables:

When entering data into a table in Microsoft Word 2003, using the tab
key
to
navigate from cell to cell, if I don't press the tab key firmly and
sharply
and sometimes even when I do push it that way, the keyboard will either
fail
to execute a tab or it will do so partially. This "partial" response
happens
most often when the first letter the first letter of the table cell is
capitalized, and the letter is omitted. I call it a "partial" response,
because hitting the tab key a second produces the correct capital
letter.

I know it isn't a hardware problem, because repeated use of the tab key
in
NotePad is unploblematic. I think there is some setting that's being
applied
to tables that creates problems. I turned off AutoCorrect, so that's
not
where the problem lies. Any ideas about this?

Stephen Diamond