Unanswered Threads

[natefarm]

Looking back at unanswered threads, I see that there are hundreds of them (maybe thousands). Is there some general rule-of-thumb about how far back one should go in looking for unanswered questions to which to respond? I know that I have been frustrated a time or two in the past when a question of mine goes unanswered, which is one of the reasons I started getting on and providing solutions myself. It's probably not worthwhile to answer posts that are months old, but I'm wondering where to draw the line. Thoughts?

[natefarm]

I guess a follow-up question would be, if someone posts a question and gets no answer for several days, what is the appropriate way of bringing it back up without violating rules or annoying people?

[Pepe Le Mokko]

Forum rules suggest waiting about one day before "bumping".

OTH if your question has not been answered although viewed by many people, then there might be something wrong with the question itself ( large project, very long post,etc...)

[natefarm]

Or maybe everyone is stumped . Are there bonus reputation points if you stump all the experts?

[xladept]

I'm perpetually, perennially stumped

[mrsklb09]

It's frustrating from a user/learner point of view that there are many. I came here from Google, working on a mid-sized project and there were so many relevant posts but no answers. However it's the same on many of these large & busy forums, it's not just here.

[FDibbins]

Sometimes, when the forum gets busy, a thread will "slip through the cracks" and end up a few pages down the list. If there are a number of pages of threads, I will often start at the end and work forward. As Pepe said in post #3, if you have not had an answer in a day or so, post something on your thread to bring it back to the top.

@mrsklb09, I know you mentioned in another thread you had a problem posting to the VBA forum. Is this still the case?