![](/mwf/attachments//avatars/3040-3756.png)
Once again we face the same old conundrum of trying to help someone answer a question that is absent of enough details such as what Brent(BB) already has alluded to... This is just my observation so let the moderator, and/or the administrator sort out the specific guidelines for posting a question in the forum...My epiphany goes like this:
Based on multiple the occasions whereby a poster would ask one question in the title of a thread starting post, and follow up with another separate question within the "meat" if you will - of the post itself... With that thought on my mind, I got an epiphany! Why don't I suggest to the powers that be to add a starting post that would act as a guide to help new posters go about properly asking questions in the AWS forum??? Each sections thread list containing @ the top of the list a specific guideline that would become a closed thread after writing it in every section... The guideline would be something like this:
This is for anyone who is unsure how to properly post a question or set of questions in this forum... Now mind you these suggestions are just that suggestions so let's continue...
When posting a question that involves anything with even the simplest level of complexity. or as simple as one could possibly ask... It is STRONGLY recommended to include as many possible details & specifics of your question in the post and we cannot stress this recommendation enough in order to greatly increase your chances of receiving a concise, intelligent answer that more than likely be in the manner that no further questions will be necessary to comprehensively answer your specific situation...
The reason for this is simple enough to understand if you think about it... Let's say the roles are reversed and I am the person who decides to make their first post as a thread starter with a question in the title and a separate question within the post itself... the person that tries to accommodate the first time poster by attempting to answer at leas one of the questions and then somehow tie their answer together with the other question... This happens too often with varying degrees of success because some or most of the important details & specifics are NOT included within any of the questions and as a result the thread which was started with two vague questions becomes a metastisized ball of confusion with replies that run the gamut in attempting to accommodate the new poster in the hopes of answering their question or questions...
The guideline would act as a sort aid to those who are new to this forum and a tool for all of us to use in the hopes of achieving a goal of reducing the number of questions that are missing the necessary details and specifics which are crucial in receiving the answer or answers they seek and minimize the potential for unnecessary debate that could morph into a heated discussion regarding a totally different topic... In other words, avoid the potential for creating a thread with very confusing goals and purposes that can spark ill feelings and strained relations amongst some of the regular members involved with such a gob of goo that is what once was a simple question without any of the necessary details and specifications required to give an educated, concise and logical answer...
So this is just a draft which in itself is the rationale to justify the possible inclusion of some very logical, common sense (If it's still practiced) suggestions and recommendations on how to properly post a question or questions in the AWS Welding forum... of course these suggestion need to be filtered & refined so that they end up not becoming a short story that will surely lose the attention of any new poster/participant here...
Well now, let's see if I can be of any assistance to add in the process of ultimately giving a clearer path to follow that will conclude with the questions being answered within the post in question... Haha!
![eek :eek:](/f2/epx.png)
![roll :roll:](/f2/epx.png)
![lol :lol:](/f2/epx.png)
![grin :grin:](/f2/epx.png)
So we have a question within a question that can easily create some confusion at attempting to replying with satisfactory answers...
Now I am not going to repeat basically why this can be the case, or what has already been posted by Brent and some of the other replies because it is not necessary...
However, I am going to avoid creating more potential questions with my answers so as not to throw the thread into a tailspin so to speak...
The proposed suggestions in the guidelines must emphasize this also... So as Brent and myself regularly post, I will attempt to answer both questions separately using the K.I.S.S. method...
![grin :grin:](/f2/epx.png)
![wink :wink:](/f2/epx.png)
![cool :cool:](/f2/epx.png)
Okay, here we go...
1.) Question:
"Can you weld painted steel?" Answer Yes you can but, it is strongly recommended and in certain situations mandatory to remove the paint prior to welding...
2.) Question:
"Our GC wants to weld painted steel to avoid removing the lead-based paint. Is there a method for determining if this is acceptable?" Answer: Yes there is a method to use, and it is shown in the contents of the AWS D1.1 Structural Welding Code, and since there isn't a Pre-qualified Welding Procedure Specification to follow as in section 3 of the code, one must qualify the joint that someone wants to weld with paint on the surface according to the clauses found in section 4 of the previously mentioned AWS D1.1 Structural Welding code in which Section 4 specifically covers qualification...
Without getting into further elaborating any more details and specifics in the hopes of helping the OP to understand all of the bases covered, I end my response as I did and wait for a follow up response if any... Now it's up to the poster to ask any more questions in their response... So with that, I'll end here with this...
I can also be guilty of overwhelming a poster by stuffing all sorts of directly & indirectly relevant information regarding the topic in question but, without filtering the response so that consideration is given to the poster's intent of their question/query at times... So in the future I'm going to try and limit my answers to whatever pertains directly to the question/query being asked within the thread in question! Haha! How redundant!
![eek :eek:](/f2/epx.png)
![lol :lol:](/f2/epx.png)
![yell :yell:](/f2/epx.png)
![twisted :twisted:](/f2/epx.png)
![yell :yell:](/f2/epx.png)
![grin :grin:](/f2/epx.png)
Hey, if you can't laugh at yourself then why bother to laugh at all, or better yet find something to laugh at and/or someone to laugh with!!!
Laughter is a healthy practice.
![lol :lol:](/f2/epx.png)
![yell :yell:](/f2/epx.png)
![twisted :twisted:](/f2/epx.png)
![yell :yell:](/f2/epx.png)
![lol :lol:](/f2/epx.png)
![yell :yell:](/f2/epx.png)
![twisted :twisted:](/f2/epx.png)
![yell :yell:](/f2/epx.png)
![lol :lol:](/f2/epx.png)
![wink :wink:](/f2/epx.png)
![cool :cool:](/f2/epx.png)
Respectfully,
Henry