Chuck,

I think you need to develop the ability to simplify. You need to define a specific problem in general terms.

There should be one or two lines of code that are giving you a problem. The rest is just a waste of time.

If there is a point in your code where everything seems to be fine, don't show that code or anything before it. And don't show code after the problem code. It isn't relevant. Just show the problem code.

If it is a design issue, then you need to explain the situation.

Joe