Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Here is a suggested list.

  • Research the problem online first to avoid duplication. Mention what you find.
  • Attempt to solve the problem before asking, and explain what efforts you have made. Programming questions should include code snippets.
  • Simplify and isolate the problem as much as possible. Use elementary problem solving or debugging techniques.
  • Describe problems encountered, with complete error messages and line numbers of code if relevant.
  • Give all information and steps necessary to reproduce the problem. Attach a sample document if necessary.
  • Provide version, operating system and locale when relevant.
  • Clearly state the actual question and desired results.
  • Use common grammar and wording so that people in other countries besides your own can understand.
  • Title should be a short summary and include relevant tags. Do not check community wiki for normal questions.
  • After asking, monitor the question for a few days in case corrections are requested. Edit the question if needed.
  • If a useful answer is given, mark it as correct and consider upvoting. Otherwise, explain in comments why the answer does not work.

Here is a suggested list.list of guidelines for asking questions.

  • Research the problem online first to avoid duplication. Mention what you find.
  • Attempt to solve the problem before asking, and explain what efforts you have made. Programming questions should include code snippets.
  • Simplify and isolate the problem as much as possible. Use elementary problem solving or debugging techniques.
  • Describe problems encountered, with complete error messages and line numbers of code if relevant.
  • Give all information and steps necessary to reproduce the problem. Attach a sample document if necessary.
  • Provide version, operating system and locale when relevant.
  • Clearly state the actual question and desired results.
  • Use common grammar and wording so that people in other countries besides your own can understand.
  • Title should be a short summary and include relevant tags. Do not check community wiki for normal questions.
  • After asking, monitor the question for a few days in case corrections are requested. Edit the question if needed.
  • If a useful answer is given, mark it as correct and consider upvoting. Otherwise, explain in comments why the answer does not work.

Here is a suggested list of guidelines for asking questions.

  • Research the problem online first to avoid duplication. Mention what you find.
  • Attempt to solve the problem before asking, and explain what efforts you have made. Programming questions should include code snippets.
  • Simplify and isolate the problem as much as possible. Use elementary problem solving or debugging techniques.
  • Describe problems encountered, with complete error messages and line numbers of code if relevant.
  • Give all information and steps necessary to reproduce the problem. Attach a sample document if necessary.
  • Provide version, operating system and locale when relevant.
  • Clearly state the actual question and desired results.
  • Use common grammar and wording so that people in other countries besides your own can understand.
  • Title should be a short summary and include relevant tags. Do not not check community wiki for normal questions.
  • After asking, monitor the question for a few days in case corrections are requested. Edit the question if needed.
  • If a useful answer is given, mark it as correct and consider upvoting. Otherwise, explain in comments why the answer does not work.

Here is a suggested list of guidelines for asking questions.

  • Research the problem online first to avoid duplication. Mention what you find.
  • Attempt to solve the problem before asking, and explain what efforts you have made. Programming questions should include code snippets.
  • Simplify and isolate the problem as much as possible. Use elementary problem solving or debugging techniques.
  • Describe problems encountered, with complete error messages and line numbers of code if relevant.
  • Give all information and steps necessary to reproduce the problem. Attach a sample document if necessary.
  • Provide version, operating system and locale when relevant.
  • Clearly state the actual question and desired results.
  • Use common grammar and wording so that people in other countries besides your own can understand.
  • Title should be a short summary and include relevant tags. Do not check community wiki wiki for normal questions.
  • After asking, monitor the question for a few days in case corrections are requested. Edit the question if needed.
  • If a useful answer is given, mark it as correct and consider upvoting. Otherwise, explain in comments why the answer does not work.

Here is a suggested list of guidelines for asking questions.

  • Research the problem online first to avoid duplication. Mention what you find.
  • Attempt to solve the problem before asking, and explain what efforts you have made. Programming questions should include code snippets.
  • Simplify and isolate the problem as much as possible. Use elementary problem solving or debugging techniques.
  • Describe problems encountered, with complete error messages and line numbers of code if relevant.
  • Give all information and steps necessary to reproduce the problem. Attach a sample document if necessary.
  • Provide version, operating system and locale when relevant.
  • Clearly state the actual question and desired results.
  • Use common grammar and wording so that people in other countries besides your own can understand.
  • Title should be a short summary and include relevant tags. For normal questions, Do do not check community wikiwiki. for normal questions.
  • After asking, monitor the question for a few days in case corrections are requested. Edit the question if needed.
  • If a useful answer is given, mark it as correct and consider upvoting. Otherwise, explain in comments why the answer does not work.

Here is a suggested list of guidelines for asking questions.

  • Research the problem online first to avoid duplication. Mention what you find.
  • Attempt to solve the problem before asking, and explain what efforts you have made. Programming questions should include code snippets.
  • Simplify and isolate the problem as much as possible. Use elementary problem solving or debugging techniques.
  • Describe problems encountered, with complete error messages and line numbers of code if relevant.
  • Give all information and steps necessary to reproduce the problem. Attach a sample document if necessary.
  • Provide version, operating system and locale when relevant.
  • Clearly state the actual question and desired results.
  • Use common grammar and wording so that people in other countries besides your own can understand.
  • Title should be a short summary and include relevant tags. For normal questions, do not check community wiki.
  • After asking, monitor the question for a few days in case corrections are requested. Edit the question if needed.
  • If a useful answer is given, mark it as correct by clicking ✔ in the upper left area of the answer, and consider upvoting. Otherwise, explain in comments why the answer does not work.

Here is a suggested list of guidelines for asking questions.

  • Research the problem online first to avoid duplication. Mention what you find.
  • Attempt to solve the problem before asking, and explain what efforts you have made. Programming questions should include code snippets.
  • Simplify and isolate the problem as much as possible. Use elementary problem solving or debugging techniques.
  • Describe problems encountered, with complete error messages and line numbers of code if relevant.
  • Give all information and steps necessary to reproduce the problem. Attach a sample document if necessary.
  • Provide version, operating system and locale when relevant.
  • Clearly state the actual question and desired results.
  • Use common grammar and wording so that people in other countries besides your own can understand.
  • Title should be a short summary summary, and include relevant tags. For normal questions, do Do not check community wiki.
  • After asking, monitor the question for a few days in case corrections are requested. Edit the question if needed.
  • If a useful answer is given, mark it as correct by clicking ✔ in the upper left area of the answer, and consider upvoting. Otherwise, explain in comments why the answer does not work.

Here is a suggested list of guidelines for asking questions.

  • Research the problem online first to avoid duplication. Mention what you find.
  • Attempt to solve the problem before asking, and explain what efforts you have made. Programming questions should include code snippets.
  • Simplify and isolate the problem as much as possible. Use elementary problem solving or debugging techniques.
  • Describe problems encountered, with complete error messages and line numbers of code if relevant.
  • Give all information and steps necessary to reproduce the problem. Attach a sample document if necessary.
  • Provide version, operating system and locale when relevant.
  • Clearly state the actual question and desired results.
  • Use common grammar and wording so that people in other countries besides your own can understand.
  • Title should be a short summary, and include relevant tags. Do not check community wiki.the "community wiki" checkbox.
  • After asking, monitor the question for a few days in case corrections are requested. Edit the question if needed.
  • If a useful answer is given, mark it as correct by clicking ✔ in the upper left area of the answer, and consider upvoting. Otherwise, explain in comments why the answer does not work.

Here is a suggested list of guidelines for asking questions.

  • Research the problem online first to avoid duplication. Mention what you find.
  • Attempt to solve the problem before asking, and explain what efforts you have made. Programming questions should include code snippets.
  • Simplify and isolate the problem as much as possible. Use elementary problem solving or debugging techniques.
  • Describe problems encountered, with complete error messages and line numbers of code if relevant.
  • Give all information and steps necessary to reproduce the problem. Attach a sample document if necessary.
  • Provide version, operating system and locale when relevant.
  • Clearly state the actual question and desired results.
  • Use common grammar and wording so that people in other countries besides your own can understand.
  • Title should be a short summary, and include relevant tags. Do not check the "community wiki" checkbox.
  • After asking, monitor the question for a few days in case corrections or clarifications are requested. Edit To respond to requests, edit the question if needed.or possibly use comments, but do not use the answer box.
  • If a useful answer is given, mark it as correct by clicking ✔ in the upper left area of the answer, and consider upvoting. Otherwise, explain in comments why the answer does not work.

Here is a suggested list of guidelines for asking questions.

  • Research the problem online first to avoid duplication. Mention what you find.
  • Attempt to solve the problem before asking, and explain what efforts you have made. Programming questions should include code snippets.
  • Simplify and isolate the problem as much as possible. Use elementary problem solving or debugging techniques.
  • Describe problems encountered, with complete error messages and line numbers of code if relevant.
  • Give all information and steps necessary to reproduce the problem. Attach a sample document if necessary.
  • Provide version, operating system and locale when relevant.
  • Clearly state the actual question and desired results.
  • Use common grammar and wording so that people in other countries besides your own can understand.
  • Title should be a short summary, and include relevant tags. Do not check the "community wiki" checkbox.
  • After asking, monitor the question for a few days in case corrections or clarifications are requested. To respond to requests, If needed, edit the question or possibly use comments, but do not use the answer box.
  • If a useful answer is given, mark it as correct by clicking ✔ in the upper left area of the answer, and consider upvoting. Otherwise, explain in comments why the answer does not work.

Here is a suggested list of guidelines for asking questions.

  • Research the problem online first to avoid duplication. Mention what you find.
  • Attempt to solve the problem before asking, and explain what efforts you have made. Programming questions should include code snippets.
  • Simplify and isolate the problem as much as possible. Use elementary problem solving or debugging techniques.
  • Describe problems encountered, with complete error messages and line numbers of code if relevant.
  • Give all information and steps necessary to reproduce the problem. Attach a sample document if necessary.
  • Provide version, operating system and locale when relevant.
  • Clearly state the actual question and desired results.
  • Use common grammar and wording so that people in other countries besides your own can understand.
  • Title should be a short summary, and include relevant tags. Do not check the "community wiki" checkbox.
  • After asking, monitor the question for a few days in case corrections or clarifications are requested. If needed, edit Edit the question or possibly use comments, comments as needed, but do not use the answer box.. The answer box is for answers only.
  • If a useful answer is given, mark it as correct by clicking ✔ in the upper left area of the answer, and consider upvoting. Otherwise, explain in comments a comment below the answer why the answer does it is not work.acceptable.

Here is a suggested list of guidelines for asking questions.

  • Research the problem online first to avoid duplication. Mention what you find.
  • Attempt to solve the problem before asking, and explain what efforts you have made. Programming questions should include code snippets.
  • Simplify and isolate the problem as much as possible. Use elementary problem solving or debugging techniques.
  • Describe problems encountered, with complete error messages and line numbers of code if relevant.
  • Give all information and steps necessary to reproduce the problem. Attach a sample document if necessary.
  • Provide version, operating system and locale when relevant.
  • Clearly state the actual question and desired results.
  • Use common grammar and wording so that people in other countries besides your own can understand.
  • Title should be a short summary, and include relevant tags. Do not check the "community wiki" checkbox.
  • After asking, monitor the question for a few days in case corrections or clarifications are requested. Edit the question or use comments as needed, but do not use the answer box. The answer box is for answers only. unless you are providing an answer to your own question.
  • If a useful answer is given, mark it as correct by clicking ✔ in the upper left area of the answer, and consider upvoting. Otherwise, explain in a comment below the answer why it is not acceptable.

Here is a suggested list of guidelines for asking questions.

  • Research the problem online first to avoid duplication. Mention what you find.
  • Attempt to solve the problem before asking, and explain what efforts you have made. Programming questions should include code snippets.
  • Simplify and isolate the problem as much as possible. Use elementary problem solving or debugging techniques.
  • Describe problems encountered, with complete error messages and line numbers of code if relevant.
  • Give all information and steps necessary to reproduce the problem. Attach a sample document if necessary.
  • Provide version, operating system and locale when relevant.
  • Clearly state the actual question and desired results.
  • Use common grammar and wording so that people in other countries besides your own can understand.understand. Calc formulas should use ; rather than , for the separator, as it is universal.
  • Title should be a short summary, and include relevant tags. Do not check the "community wiki" checkbox.
  • After asking, monitor the question for a few days in case corrections or clarifications are requested. Edit the question or use comments as needed, but do not use the answer box unless you are providing an answer to your own question.
  • If a useful answer is given, mark it as correct by clicking ✔ in the upper left area of the answer, and consider upvoting. Otherwise, explain in a comment below the answer why it is not acceptable.

Here is a suggested list of guidelines for asking questions.

  • Research the problem online first to avoid duplication. Mention what you find.
  • Attempt to solve the problem before asking, and explain what efforts you have made. Programming questions should include code snippets.
  • Simplify and isolate the problem as much as possible. Use elementary problem solving or debugging techniques.
  • Describe problems encountered, with complete error messages and line numbers of code if relevant.
  • Give all information and steps necessary to reproduce the problem. Attach a sample document if necessary.
  • Provide version, operating system and locale when relevant.
  • Clearly state the actual question and desired results.
  • Use common grammar and wording so that people in other countries besides your own can understand. Calc formulas should use ; rather than , for the separator, as it is universal.the semicolon works with any locale.
  • Title should be a short summary, and include relevant tags. Do not check the "community wiki" checkbox.
  • After asking, monitor the question for a few days in case corrections or clarifications are requested. Edit the question or use comments as needed, but do not use the answer box unless you are providing an answer to your own question.
  • If a useful answer is given, mark it as correct by clicking ✔ in the upper left area of the answer, and consider upvoting. Otherwise, explain in a comment below the answer why it is not acceptable.

Here is a suggested list of guidelines for asking questions.

  • Research the problem online first to avoid duplication. Mention what you find.
  • Attempt to solve the problem before asking, and explain what efforts you have made. Programming questions should include code snippets.
  • Simplify and isolate the problem as much as possible. Use elementary problem solving or debugging techniques.
  • Describe problems encountered, with complete error messages and line numbers of code if relevant.
  • Give all information and steps necessary to reproduce the problem. Attach a sample document if necessary.
  • Provide version, operating system and locale when relevant.
  • Clearly state the actual question and desired results.
  • Use common grammar and wording so that people in other countries besides your own can understand. Calc formulas should use ; rather than , for the separator, as the semicolon works semicolons work with any locale.
  • Title should be a short summary, and include relevant tags. Do not check the "community wiki" checkbox.
  • After asking, monitor the question for a few days in case corrections or clarifications are requested. Edit the question or use comments as needed, but do not use the answer box unless you are providing an answer to your own question.
  • If a useful answer is given, mark it as correct by clicking ✔ in the upper left area of the answer, and consider upvoting. Otherwise, explain in a comment below the answer why it is not acceptable.

Here is a suggested list of guidelines for asking questions.

  • Research the problem online first to avoid duplication. Mention what you find.
  • Attempt to solve the problem before asking, and explain what efforts you have made. Programming questions should include code snippets.
  • Simplify and isolate the problem as much as possible. Use elementary problem solving or debugging techniques.
  • Describe problems encountered, with complete error messages and line numbers of code if relevant.
  • Give all information and steps necessary to reproduce the problem. Attach a sample document if necessary.
  • Provide version, operating system and locale when relevant.
  • Clearly state the actual question and desired results.
  • Use common grammar and wording so that people in other countries besides your own can understand. Calc formulas should use ; rather than , for the separator, as semicolons work with any locale.
  • Title should be a short summary, and include relevant tags. Do not check the "community wiki" checkbox.
  • After asking, monitor the question for a few days in case corrections or clarifications are requested. Edit the question or use comments add a comment as needed, but do not use the answer box unless you are providing an answer to your own question.
  • If a useful answer is given, mark it as correct by clicking ✔ in the upper left area of the answer, and consider upvoting. Otherwise, explain in a comment below the answer why it is not acceptable.

Here is a suggested list of guidelines for asking questions.

  • Research the problem online first to avoid duplication. duplication. Mention what you find.
  • Attempt to solve the problem before asking, and explain what efforts you have made. Programming questions should include code snippets.
  • Simplify and isolate the problem as much as possible. Use elementary problem solving or debugging techniques.
  • Describe problems encountered, with complete error messages and line numbers of code if relevant.
  • Give all information and steps necessary to reproduce the problem. Attach Attach a sample document if necessary.
  • Provide version, operating system and locale when relevant.
  • Clearly state the actual question and desired results.
  • Use common grammar and wording so that people in other countries besides your own can understand. Calc formulas should use ; rather than , for the separator, as semicolons work with any locale.separator.
  • Title should be a short summary, summary, and include relevant tags. Do not check the "community wiki" checkbox.
  • After asking, monitor the question for a few days in case corrections or clarifications are requested. Edit the question or add a comment as needed, but do not use the answer box unless you are providing an answer to your own question.
  • If a useful answer is given, mark it as correct correct by clicking ✔ in the upper left area of the answer, and consider upvoting. Otherwise, explain in a comment below the answer why it is not acceptable.

Here is a suggested list of guidelines for asking questions.

  • Research the problem online first to avoid duplication. Mention what you find.
  • find. Attempt to solve the problem before asking, and explain what efforts you have made. Programming questions should include code snippets.
  • Simplify and isolate the problem as much as possible. Use elementary problem solving or debugging techniques.
  • techniques. Describe problems encountered, with complete encountered and show error messages and line numbers of code if relevant.messages.
  • Give all information and steps necessary to reproduce the problem. Attach * a sample document if necessary.
  • necessary. Provide version, operating system and locale when relevant.
  • Clearly state the actual question and desired results.
  • Use common grammar and wording so that people in other countries besides your own can understand. Calc formulas should use ; for the separator.
  • Title Clearly state the actual question and desired results. The title should be a short summary, and include relevant tags. Do not check the "community wiki" checkbox.
  • After asking, monitor the question for a few days in case corrections or clarifications are requested. Edit the question or add a comment as needed, but do not use the answer box unless you are providing an answer to your own question.question.*
  • If a useful answer is given, mark it as correct by clicking ✔ in the upper left area of the answer, and consider upvoting. upvoting.* Otherwise, explain in a comment below the answer why it is not acceptable.

* Requires the number of karma points listed here.

Here is a suggested list of guidelines for asking questions.

  • Research the problem online first to avoid duplication. Mention what you find. Attempt to solve the problem before asking, and explain what efforts you have made. Programming questions should include code snippets.
  • Simplify and isolate the problem as much as possible. Use elementary problem solving or debugging techniques. Describe problems encountered and show error messages.
  • Give all information and steps necessary to reproduce the problem. Attach* a sample document if necessary. Provide version, operating system and locale when relevant.
  • Use common grammar and wording so that people in other countries besides your own can understand. Calc formulas should use ; for the separator.
  • Clearly state the actual question and desired results. The title should be a short summary, and include add relevant tags. tags. Do not check the "community wiki" checkbox.
  • After asking, monitor the question for a few days in case corrections or clarifications are requested. Edit the question or add a comment as needed, but do not use the answer box unless you are providing an answer to your own question.*
  • If a useful answer is given, mark it as correct by clicking ✔ in the upper left area of the answer, and consider upvoting.* Otherwise, explain in a comment below the answer why it is not acceptable.

* Requires the number of karma points listed here.