I don't think the problem here is a lack of background research. I mean, yes, that's always a good thing to add to a question; the more effort you can demonstrate that you've put into solving a problem yourself, the more willing people will be to help you.
But the real reason we want you to include information about attempted solutions is that it essentially forces you to provide more specific details about the actual problem that you're having. The lack of those details is the real problem with your question, as it stands now.
If you had provided a comprehensive description of the problem, along with detailed information about your code and system configuration, and ideally a small, self-contained example, I couldn't give a hoot about how much research you had done yourself. I would not close the question for that reason, and I would vote to re-open it if someone else had done so.
Why? Because with all of that information, your question becomes answerable. And that's our basic requirement for all questions asked here.
As it stands now, all we can do is guess about what your problem is. My crystal ball shattered a few months back, so I'm not much help anymore. I know a guy with one, but his has gotten foggy recently, and that doesn't work very well with the Q&A model of a site like Stack Overflow. It turns into a game of
20 100 questions in the comments thread, which isn't much help to anyone. Even if you eventually get a solution, the information churned up in the comments generally isn't edited back into the question proper and no official answer gets posed, which means it isn't useful to anyone else in the future. Since our mission here is to build up a comprehensive database of high-quality answers to programming questions, debugging your code is not a good way to spend our time.
The answers you've received to that question are all perfectly reasonable answers, but there's no way to tell which one is correct. There isn't enough information provided in the question to be able to judge. All of the answerers were just guessing at what might be the best solution for you. They were trying their best, of course—nothing against them. It's just that this kind of thing is more suited for a traditional forum or dialogue, where you can have back-and-forth exchanges. That's not our model.
Remember that most of us are sitting too far away to see your screen. You have to give us enough information to be able to help you. Whatever you can think of—detailed descriptions, information about your environment, repro steps, actual source code, stack traces, screen shots, etc. You've got to make it clear what the problem you're trying to solve is, and why you need to solve that problem.
If you edit your question to add that in, I'll vote to re-open it. Heck, I'll even throw you an upvote