>>This is what gets my goat as well. I can't even recall all the times I have asked a question on the UT only to have it answered "that is bad design", or, "that is not the right way..." The way I do things was never up for negotiation (unless I explicitly want help in that arena). I am an excellent programmer. If I end up being pushed into a certain way of doing things because of user requirements, hardware limitations, or any other reason out of about a million, I don't want an answer to my question taking the form of saying I should totally change the way I am doing something.
>
>
>Joe - perhaps you could add some text like "I'm stuck with this design, so how do I ..."

You are right...I see what you are saying. Some text to show that I know what I am doing, but still need help with something that may not be the optimal design. Maybe so.

I guess we should ask ourselves what is the goal of UT? Do simply disseminate solutions or to try to educate the masses on proper programming? I don't proclaim to know the answer. But if someone asks about using scrollable forms, I am going to tell them how to use scrollable forms. I like it when folks, whether it be out of ignorance or out of ingenuity, try something new. I see it as a type of evolution, where the fittest ideals will survive. Maybe scrollable forms are the way EVERYTHING should be done, and in 10 years we will all look back and say, "so THAT is hwat the users really wnated all along!" OK, maybe I am high, but I like re-inventing the wheel, and using solutions that may not be the "standard" or "best practice".

So, I gues what I am saying is that you are right: I could add some text to let folks know the design is not negotiable...but in my opinion, I shouldn't have to. Maybe we need a "skill level" attribute for UT users, so that if an "expert" asks something as heretical as "how do I use scrollable forms", folks will tell him/her how to use them instead of saying "scrollable forms...BAD!"

JoeK