Hi,
I've made it my standard to supply an attachment with my answer. I feel that having an example with formulas/tables/pivots to play with, along with some explanations is a better answer than either alone. I've also found that describing a problem in writing is many times much harder than to use a yellow cell on an attached file showing where a problem lies or where a needed result is desired.
Many times I've created the attachment when the OP didn't supply one. My hope is showing the structure of the problem (normally data in a table) and how to arrive at an answer is more enlightening that a description without the attached example.
I also find that Code in the wrong place (behind a sheet instead of module or userform) is hard to describe and giving back the file that works is much better than trying to explain it. Also when the file is supplied in an answer, the OP (or expert) can set breakpoints and step through code to see what might be failing. This is MUCH better than pasting a line of code saying something like make your "c.Test" a "c.Value" and see if that works.
I pride myself on giving back an attached file. I believe this also shows an extra effort in trying to solve the OP's question.
Many times the education of the OP is found by learning more about DNR or CSE type of information. I think supplying a link to tutorial or instruction pages is more effective than trying to rewrite them in an answer. Saying "read this link" and see how I've used it in this example is a great way to answer questions.
Is my thinking wrong on these points?
Bookmarks