I just read the thread suggesting how to ask questions the right way, and now I'm paranoid that the method I used is more trouble than it is helpful, so I want to run it by the forums
Generally, when a problem comes my way, I tend to search the web for a quick answer, then use MS Help (sadly, it normally is more efficient in this order), then search the forum for answers, and if I cannot find something which I can apply - not copy, mind you - I will try to write a question.
Generally, it follows this format:
**
Background
I tell what my current project is, what kind of detail I have, so potential helpers can get a grasp of what level I am at.
Goal
Here, I describe the more local goal, not so much of the entire program, but of the intended purpose where, as seen below, a problem occurs.
Problem
Simply put, this describes the problem.
Conclusion/Notes
This normally involves my own theories as to what may be wrong. It usually also includes what I have actively done to solve the problem within the program that is giving me trouble.
**
I mainly do this because it's easy to read and shows people in an ordered fashion what kind of situation it is, what kind of trouble I'm getting into and what kind of a hole I have potentially dug in trying to do/analyze things on my own. However, some people may not like this seemingly overly formal approach, so I figured I would check if this is okay in general before moving on with it.
Anyone who wants to contribute, please feel free to share your opinions. Thanks a lot!
Generally, when a problem comes my way, I tend to search the web for a quick answer, then use MS Help (sadly, it normally is more efficient in this order), then search the forum for answers, and if I cannot find something which I can apply - not copy, mind you - I will try to write a question.
Generally, it follows this format:
**
Background
I tell what my current project is, what kind of detail I have, so potential helpers can get a grasp of what level I am at.
Goal
Here, I describe the more local goal, not so much of the entire program, but of the intended purpose where, as seen below, a problem occurs.
Problem
Simply put, this describes the problem.
Conclusion/Notes
This normally involves my own theories as to what may be wrong. It usually also includes what I have actively done to solve the problem within the program that is giving me trouble.
**
I mainly do this because it's easy to read and shows people in an ordered fashion what kind of situation it is, what kind of trouble I'm getting into and what kind of a hole I have potentially dug in trying to do/analyze things on my own. However, some people may not like this seemingly overly formal approach, so I figured I would check if this is okay in general before moving on with it.
Anyone who wants to contribute, please feel free to share your opinions. Thanks a lot!