I think we should put our heads together and write a tutorial on how to write a good question.
I suppose Rule #1 should be to use a good subject. Easy to say, not so easy to implement. I can give some examples even if I can't explain it.Need help - worst possible subject
Need help with SUMIFS - better
Need help with SIMIFS from another workbook - even better
Rule #1.5 - It's a corollary to Rule #1 - if you can get your wording right, Google is your friend. Look for a solution that has already been posted. Or at least read what other people have said about it and it may give you ideas on how to phrase your question and what factors may or may not be important.
Rule #2 - Attach a sample workbook. This is probably my biggest peeve. There are questions that can be answered without having to include a workbook: maybe about one in 20. The other 95% of the time, a workbook helps lot and in most cases, the issue can't be resolved at all without a workbook. People are more likely to respond to a thread with a sample workbook. People, including self, either do not have time or inclination to type in data that the poster probably already has.
Rule #3 - Include good data that can illustrate your point. There should be enough data to exercise the logic. If there are exceptions, then include at least one example of each exception. You should have enough data to produce a reasonable output, but we don't need all 750,000 records. Anywhere from a dozen to a hundred records is usually good enough.
Rule #4 - Before and after. Even if you can't produce the result you want, you can create what you want the results to look like manually. Otherwise, how do we know we got it right? It is OK to use pictures for this purpose, but a sample worksheet is probably better.
Rule #5 - Note cross posts. If you are casting your net on every board in hopes of an answer, that's OK, but provide links so we don't waste time answering a question that has already been answered somewhere else.
Rule #6 - 'Fess up. I try to gauge where people's competence level is by the number of posts. However, this is not a reliable indicator. If you are a total novice, that's OK. If you are at an intermediary level, that tells me something too. I like to provide an explanation that doesn't "fly over the user's head" but on the other hand, I don't want to bore them with information they already know.
Rule #7 - Got an error? Record it! Provide a screen shot. Tell us what you had to do to cause the error to happen.
Rule #8 - Tell us what you've tried already. Sometimes we'll think, "Well, of course that won't work." other times it will be "That should work! Why doesn't it?"
Rule #9 - Use a good profile. The version of Office that you are using DOES matter. Also location can be important. Regional settings may matter; they may even affect the code. Once I wrote:
Works great in most English-speaking countries, but does not fly in the Nederlands.
Since jaar is year over there. (I'm learning a lot from all over the map on this board)
Rule #10
Bump judiciously. Many of us responders go first to the unanswered bin - those are posts with zero responses. If you responded to your own post, then you are not on this list.
Rule #11 - Read the rules as posted on the site.
OK, that's off the top of my head. It obviously needs improvement. I am sure I've forgotten things. I am sure there are things that need to be expanded. I'm a big boy and I can take the hits so feel free to criticize.
Bookmarks