Hitchhicker's Guide to Getting Help at VBF

1) Don't Panic

2) Take a deep breath...let it out, relax.

3) Determine where the appropriate place to post is. If it's a VB question/problem, determine the VERSION of VB you are using. You have several choices: VB6 and older (this means VB1-6, including 3,4,5 and CCE)... and NOT the .NET versions. For .NET, there are separate sections. Once you figure out the appropriate version, be sure to note this in the post. For VB6 and older, add VB6 (or VB5, VB4 as appropriate) to the subject line. In .NET, there is a drop down next to the Subject for you to select the version.

4) If you are using C#, post in the C# forum. There's also a version selection option in there too.

5) For those with .NET questions, PLEASE post the framework version you are targeting. It makes a difference.
to help, use this chart:
VS2002/2003 - FW 1.0/1.1
VS2005 - FW 2.0
VS2008 - FW 2.0/3.0/3.5
VS2010 - FW 2.0/3.0/3.5/4.0

6) If a database is involved, post in the Database section. Include the above information, AND also the database type and version you are using. SQL Server, Oracle, Access, mySQL, etc.
Also take a look at our Database FAQ & Tutorials Most of the commonly encountered problems are found here. Also, make sure you are using the right connection string. You can get that from here: http://www.connectionstrings.com

7) When you enter the subject line... be descriptive, try to be clear, and describe your problem in 10 words or less. Do NOT use "please help" or "it's broke, help"... that doesn't tell us anything. Try things like "Connection to database failed" or "Login form fails user validation". "Problems in updating an access database" is a good example. Here's a good one, in the Office Dev section "[OUTLOOK] Trying to run a sub on send" ... the poster even included the Office app! Titles like "Searching Files" or "Event Trigger" don't help as much. Neither does "PHP VB.net". Remember the subject is your 3 second ad to get some one to help you, make it count. Otherwise we may assume that your problem is that you have eels in your hovercraft, and will respond accordingly.

8) Now, you are into the post itself. Take a deep breath (yes, again)...let it out, relax.

9) Show what code you do have, (be sure to use or tags as needed. Then explain, in clear sentences what you are struggling with and what the problem is. Statements like "I just need in the login window users default nick is student and pass is student, and for the admin section admin admin" don't help... that doesn't tell us what the problem is. Statements like "It needs to check the username and password against a users table in the database, and I can't figure out how to get the data from the database" does tell us. And it might be that we point you to a link or two... read through the linked material. Do your best, then come back with "I tried, x, y, z... and it didn't seem to work." and explain what errors you are getting or what you expected to happen that didn't. Or explain what did happen that shouldn't have happen. If there is dat involved, please supply some sample data, actual if you can. Include screenshots if you can. Add them to your post as an attachment. Using things like imageshack is fine, but not everyone will be able to get to it, if it's at VBF, then vieweres will at least have a chance at being able to see it.

10) Be honest, let people know that if it is part of the assignment. If the instructor has given the OK to get help from places like this, note that. But at the same time, realize that no one is going to do your assignment for you. Please put SOME effort in to it first. Then follow step 9 above. We are here to HELP, not to do.

11) BEFORE you hit submit, MAKE sure the post is in the right spot. Places to NOT post your problems include Code Bank, Project Requests, or Utility Bank. You post in there and odds are you won't get much help (at least until someone finds the lost post and moves it.)

11) Keep in mind that support here is voluntary, and something people do in their spare time, so it's possible that there may be times when a post doesn't get any hits for a while. Don't bump your thread. You can add to the post or reply to your own post if more information becomes available. But don't bump it just to keep it on the first page. Granted if a REASONABLE amount of time has past, like 12 hours or a day or two, then a bump might be acceptable. But if at all possible, don't bump for the sake of bumping.

12) Be kind, rewind. Check back on your posts, often more info is requested and it goes unanswered, which just leads to many un-informed, or speculative postings, which just may confuse things in the long run.

13) When you do get your solution, thank those involved, rep those that you think deserve it, and mark the thread as Resolved. You can do that by clicking "Thread Tools" at the top of the thread and select "Mark as Resolved". This helps us know that the problem is closed, and speeds up the process as then we can skip over it when looking for posts to help with. It will also help other users who use the search function for something. With a clear subject line, if it has been marked, it signifies that a solution to their problem might be found in there.

14) If you solve the problem on your own, please reply back with what you found was the problem and HOW you fixed. this goes back to helping the next person that comes along. Don't just reply back with "Found problem, fixed it." and nothing else.

15) If you post a thread, then realize after the fact that it is in the wrong spot, let a mod know, and they will move it for you. To do this, click the warning image next to your post, and "Report the thread". In the box that comes up, explain that you accidentally posted in the wrong forum, and could it be moved to "X y Z location".

16) Now for the DO NOTS: DO NOT cross post or write multiple posts. IF YOU ARE NEW to VBF, your first few posts MUST be approved before they can be posted. So don't fret if you don't see your post right away. Multiple posts just confuse us and split the answers, creating more havok. DO NOT post a C# question in the VB section simply because VB gets more traffic - it is VB Forum after all - respect the categories and forums setup. If I go searching for an answer to a C# question, I'm looking in the C# forum, not VB, so intentionally posting in the wrong forum is just bad juju. DO NOT use texting language when posting your problems. Most of us will make allowances for people whose first language isn't English, but for those who it is, you're not typing into a 2" screen, or posting on IM. You are in a forum, there's no need to rush. Take a moment to type things out. Nthng Is MoRe AnnyING thn TxT tht Is In Rndm CaSE n MissGN Ltrs.

17) Remember we are here to help. Help us help you.

-tg