\r\n\r\n \r\n \r\n \r\n # 2 \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n  \r\n \r\n 07-23-2004, 07:35 AM\r\n \r\n \r\n \r\n | \r\n
\r\n\r\n\r\n \r\n \r\n \r\n \r\n \r\n \r\n  | \r\n \r\n\r\n \r\n\r\n\r\n\r\n Quote: \r\n \r\n \r\n | \r\n \r\n \r\n Originally Posted by John\r\n \r\n \r\n This couldn\'t be further from the way I feel about the same issue and yes I\'m a professional programmer.
\r\n
\r\nI don\'t hand out code every chance I get because I feel it is better to guide someone than to give to them. \r\n \r\n | \r\n \r\n \r\n I\'m neither a professional programmer nor a particularly experienced one (I\'d say Journeyman for VBA, but not much beyond that) and I agree totally. If you give a person code handouts whenever they have a question, they learn to ask for code handouts rather than learning how to do it on their own. A lot of questions could be answered by using Help on the object/property/method/whatever, and saying that in an answer shouldn\'t be seen as snippy. I\'ve learned more by poking around, trying to answer questions other people ask, than I would have if I only asked a question when I needed help and took the answer without thinking about why it worked. | \r\n \r\n \r\n \r\n\r\n \r\n \r\n\r\n \r\n \r\n \r\n __________________
\r\n James Auwaerter\r\n \r\n \r\n \r\n\r\n \r\n\r\n \r\n\r\n \r\n \r\n \r\n \r\n \r\n  \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n | \r\n
\r\n
\r\n\r\n\r\n
Threaded Mode
