how do you handle it if you turn out to be wrong on a code issue with an associate who was correct?

i am usually the first to admit if i am wrong..

i am asking becasue i have to find a tactful way of going back on what i have said...

i enjoy a good discussion about the code and feel that two professionals should be able to agree to disagree but some people really get mad if they are wrong and they really beleive they are right!

I admit as quickly and loudly as possible that I'm wrong. This humility usually bolsters the ego of the other guy, and stops HIM from announcing as quickly and loudly that I'm wrong to anybody that will listen or the world at large.

thanks i will take your advice and eat some crow!

frodo;
crow has been a regular mael for me in the BB's, it's an acquired taste

I always say that my eraser wears out long before the pencil runs out of lead. Face it, you're human, you're going to make mistakes, 'fess up & get it over with. One of the things I like about making mistakes in this forum is that nothing gets hurt except my pride.

Tom

Crow is the main entree...

Humble Pie the desert!

... and be glad that you weren't working as a cardiologist ...

Finally, a topic that I feel fully qualified to speak on. Being wrong!
I have more respect for those who admit when they were wrong than those who try to make excuses or change their original explanation as they go. It can usually be chalked up to a valuable learning experience. Also, it is easier to admit you are wrong if you are not emphatic to the point of being obnoxious in making statements that you may not be 100% on. And how often are we really 100%? I believe we should respect other peoples attempt at interpretations, even though they may be seeing it differently than you. One of you is going to be wrong, and as they say "even a broken clock is right twice each day"

[This message has been edited by Redsy (edited 05-22-2001).]

well I thought I was wrong one time and then i found out I was wrong lol