>Ed, > > > >>I wish there were a flag the poster could set to indicate "Any help appreciated" vs "Don't reply unless you have absolutely flawless, immediately usable code that you're willing to provide free tech support for at your expense forever", so that I could figure out when to post SWAGs, pseudocode and first-cut fragments to address problems. Unfortunately, that's not available here. So it seems like a good time to sit back and watch for a while. > >I had mentioned such an idea a while back (and I think it was still this thread...it has gone from a discussion about color, to response guidelines, to MVP issues, back to colors, and now to all sorts of things!). I was saying it would be neat to have a flag maybe as simple as "Newbie" or "Expert" so that if I were to ask about scrollable forms as an "expert" I could maybe avoid the folks who come on and say "don't use scrollable forms because they are non-standard". If I am labeled as an expert, it might tend to make responses be more info-based instead of guidance-based. On the other hand, being an "expert" might cause a lot of folks to not bother with posting the simpler side of responses, which may be what I need in a given instance... I am not sure what sort of labeling scheme would work, if any. >
It's not Newbie vs Expert. There are people who are outraged when someone offers a code snippet that have typos in them, or are subject to side-effects, or contain pseudocode instead of actual VFP statements. If they don't want replies giving best-guess approaches, or where the code might be given off the top of your head, or isn't meticulously checked for typos and side-effects, let us know.
I'll probably be guilty of code errors in some of my future posts; of course, the Snippet Gestapo may have me detained and interrogated for exposing lewd and indecent source files, and have the courts confiscate my keyboard for such wanton displays of indecent coding style. Perhaps I'll be incarcerated for contributing to the delinquency of a consultant.
