Timeline for Why was my question closed? Is VBA on Topic for SuperUser
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 16, 2019 at 19:38 | vote | accept | FreeSoftwareServers | ||
| Jul 21, 2019 at 0:28 | history | edited | Giacomo1968 | CC BY-SA 4.0 |
added 2 characters in body
|
| Jul 13, 2019 at 6:29 | comment | added | FreeSoftwareServers |
@DavidPostill well, that is what SU is, a community, if they feel it is off topic, so be it. BTW I spent an hour researching using case statements before posting this question and resolved it by testing using numbers which made me realize the issue was that it needed ""
|
|
| Jul 13, 2019 at 3:42 | comment | added | Ramhound | I do not agree with the comments of the user who voted to close your question, they handled the entire situation poorly, they should have flagged and moved on instead of submitting a close vote after they received a downvote. I however, do agree the question should have been closed, mainly for the reasons @fixer1234 expressed. If the user thought the question was not well researched, they should have downvoted, and issued a closed vote. The default reason for a downvote is an indication the question either needs work or is not well researched. | |
| Jul 12, 2019 at 23:28 | comment | added | fixer1234 | 3. The site's purpose is to share solutions. There used to be a close reason for questions too specific to the author to be of value to anybody else. That's no longer one of the standard close reasons, and I don't think this question falls in that category. | |
| Jul 12, 2019 at 23:16 | comment | added | fixer1234 | 2. "Beginner coding error" should not be justification for closure; beginner questions are welcome. However, at least minimal research is expected before posting, so general learning questions and ones that are readily answered by a simple search tend to not get a good reception. | |
| Jul 12, 2019 at 23:16 | comment | added | fixer1234 | 1. VBA seems to have a gray area. Questions like "how do I solve this Excel problem, and VBA solutions are OK" are almost always considered on-topic if the scope is reasonable. And people are asked to show their their own attempt to solve it, which could include some VBA code. But questions consisting entirely of debugging non-trivial code are often considered programming problems, more suited to SO. The distinction seems to be whether the focus is solving a problem using VBA vs. fixing code; the distinction isn't always a clean one. (cont'd) | |
| Jul 12, 2019 at 23:10 | answer | added | Ramhound | timeline score: 10 | |
| Jul 12, 2019 at 20:20 | comment | added | DavidPostill Mod | It went to reopen review after your edit and the community voted to leave it closed. | |
| Jul 12, 2019 at 13:57 | comment | added | FreeSoftwareServers |
Sure, I did put a Microsoft-excel tag, but I can add it to the body.
|
|
| Jul 12, 2019 at 13:31 | comment | added | Burgi | You don't explictly mention Excel so it is possible people have misunderstood the context of your question, incorrectly assuming it is a pure coding question. I would suggest just clarifying the context and it should be good to reopen. | |
| Jul 12, 2019 at 11:50 | history | asked | FreeSoftwareServers | CC BY-SA 4.0 |