April 29th, 2007 until June 2nd, 2030
1a. Thread titles MUST aptly and concisely describe your problem.
1b. Your title must describe your problem, not your anticipated solution.
1c. Use terms suitable to a Google search and do not words like "Please Help", "Urgent", "Excel Problem"
1d. Do not use Excel formulas in thread titles. E.g. "Help with VLOOKUP" (you have assumed the solution to your problem involves VLOOKUP).
Why? All of the above makes your code search engine friendly and easier for other people with similar problems to find solutions. It turns Ozgrid into a knowledge base, rather than a forum.
ASKING A QUESTION
2a. Search for an answer to your question. If everyone follows rule number 1, you will get a surprisingly accurate result.
2b. Please dont open old Threads. Someone who posted a question 10 years ago is probably still not waiting for a solution, even if you are certain it is the best solution!
2c. Please dont start a new question in an existing thread. This is known as Thread hi-jacking. Start your own thread. Its Free! If you need to, you can link back to the thread that you thought might have been helpful.
3a. You MUST use code tags when posting.
Your code goes here between the tags...
'line of code
Or, highlight your code and click the # button - it will look like this
Why? This will make your code more readable and allow developers to easily copy it for testing.
4a. No double posting. This is because double posts are wasting the time of volunteers by them answering the post when the post may have already been answered.
4b. Do not cross-post without supplying a link to the duplicate question on the other Forum.
4c. Never be rude to the person giving help. Please take the time to thank those who took their time to help you..
4d. Never be rude to the person you're helping.
Why? Because every single person that helps out at Ozgrid does so on their own free time. This is a free to post forum so show some gratitude. Besides, its nice to be nice and you will find that people will help you, if you help them by being a good responsible forum citizen.
Questions that will not be answered :
5a. No asking to crack passwords of any kind. Doing so, even innocently, will get you banned.
5b. No asking for help with homework or college assignments. We will not do it for you. This also applies to the hire Help forum.
5c. Web scraping. Ozgrid will not assist you in systematically acquiring data (even in the public domain) from a other peoples websites. We will show you how to do excel/browser automation with generic examples and answer specific questions related to browser automation VBA methods
6a. Posting in incorrect Forums. If we perceive you have posted in the wrong Forum, we will move your post for you. We want you to have the best possible chance of someone answering your question. We will of course, let you know if we have done this.
6b. Do not argue with moderators and other forum members about the rules. If you feel you are being mistreated, please Report the Post or contact one of the Admin or Super Admins on the site.
* Think about your thread title and search before starting a new thread.
* Dont ask us to do something bad or stupid. We wont do it.
* Be nice!
Despite all the rules- we're actually not a bad bunch of folks! Have a great day and welcome to Ozgrid
Video Tutorials / Excel Dashboards Reports
December 30th, 2006 until March 12th, 2020
Anatomy of a Good Thread Title
Thread titles are used in searching the forum, therefore, it is vital they be written to accurately describe your thread content or overall objective using ONLY search friendly key words. That is, your title used as search terms would return relevant results.
The title must not use non-essential words such as:"Help needed", "Formula problem", "Please help", "urgent", "Code issue", "Need Advice", etc. Such words dilute the title/search results.
The title should not contain VBA code or formula syntax or use abbreviations, jargon, delimiters (e.g. slashes, commas, colons, etc)
The title should not assume or anticipate a solution as in referencing Excel functions or VBA methods - the actual solution is often quite different