Tamar,
Thank you for your explaination. I'm sorry that what I think was our first conversation got off on the wrong foot... I was having a very rough day!!!
Sometimes life just wears me too thin, and yesterday was one of those days.

I think the concern you raised is definately one we all need to be aware of, especially me, because spelling errors could raise doubt about our professionalism... Also, I've had my weakness in this area mentioned to me a few times here at work.

For me, I think I would have received it better had you said something like what you mentioned in you reply...
or
"Rick, I noticed a typo in your post, 'WRONGe Wirds'...
Don't forget to run your spell checker before going live...it helps maintain a professional image. :-) "
or
"Rick, I'm not sure what you mean by 'WRONGe Wirds'...
Could you phrase it differently?"

Thank you for replying,
I needed that!
Rick

-------------
>>Question, Since you admit that the others told me how, and I didn't request further clarification, and you didn't add anything new to the thread...
>>Why'd you send me a near flame?
>
>Sorry, I didn't mean it to be perceived as a flame. That's why I used the "SET NITPICKY ON."
>
>To be honest, I'm never quite sure what to do with spelling and grammar mistakes that I see in public groups. When they don't impact the message (such as many people's use of "loose" when they mean "lose"), I just ignore them. When I think a mistake is causing people to misunderstand the question or answer, I try asking if there's a misunderstanding. Occasionally, I'll send someone a private message, explaining the mistake and the rule.
>
>In this case, I really was concerned about the misspelling getting into your deployed app and tried for a gentle approach. Obviously, I missed the mark and I apologize. You can help me by telling me what would have been a better way to handle it.
>
>Tamar