In addition to our Forum Rules (which all posters should be familiar with), we are also introducing a “Forum Etiquette and Best Practices” for posting to the MetaStock Online Community Forum. Adhering to these guidelines helps to build a cohesive community – one of trust and one in which people are willing to share their ideas and help those who need help. Forums are only as strong as their members – help to do your part to ensure that the MetaStock forum continues to be a valuable tool by following these practices as well.

• There is a person behind the post. Never forget that there is a person behind the original post and replies. Speak as you would to someone who was standing in front of you. “Thank you” goes a long way. Not only does it recognize the time a respondent put into answering your question, but it also alerts others that your question was fully answered. And remember, unless it is an Equis employee, the responders are not paid to help you.
• Research your problem before posting. Forum respondents dedicate much time and effort to answering the same queries over and over again. Prior to posting, do some leg work yourself – search for similar posts, read the help files and/or documentation that comes with your software. Arming yourself with knowledge alerts the responder that you’ve put some effort into it and makes them happy to put effort into the answer as well.
• Be specific and show examples. Detailed explanations with examples help in correctly diagnosing a problem. In addition, pictures go further in terms of describing the problem, and help to break down language barriers.
• Don’t post your “holy grail”, but don’t skirt around it either. Posting incomplete portions of code, abstracts or "likenesses" in the forum is rarely helpful for discovering the underlying causes of problems in MetaStock codes. If you think you have discovered the “holy grail” and don't want to publish your codes in the open forum, contact a trusted forum member by private message and ask for their dedicated assistance. If they agree to support you, only then should you send them the problem code in private.
• The technical analysis world is a tight knit group. Posting part of your project/problem in multiple forums in the hopes of then piecing it together doesn’t win many friends. It does not take much to identify common elements posted in multiple forums all coming from the same source.
  
• Inform the respondent that they didn’t solve your problem. If your problem was not fully resolved, let them know. Nothing destroys the willingness of a member to help you more than when they see the posts they took the time to answer on the Equis forum asked later on another forum.
• Sometimes professional assistance is required. There are occasions when no matter how much effort you put in yourself, you just cannot solve the problem on your own. Hiring an expert can save you a lot of time, frustration, and money.