I understand Pete's position and am guilty of over asking as charged. However, I like to get things really straight in my head before I proceed. This leads to less mistakes and better first run projects. There is the other side of the coin though, that some things should be common sense and you really have to try it first to see the results. After the fact questions are really the best ones. For these allow you to understand what you did and how you did it. so when the advice comes you have a better understanding on how to correct it. The best analogy I have is software. All to often people get new software, load it and begin to ask questions. The better approach is to fumble around, use it, get frustrated and then after a few weeks, ask questions. Nothing more aggravating than being asked how do i do this? And when you explain it the next questions is, I don't know were that menu is. Helping is a wonderful thing, but so is innitiative.