I don't know how such a tradition can be instigated. Other than to simply start doing it. If it is a good enough idea, and if enough people see and benefit from it, then the practice will take on a life of its own.
A thread summary is especially useful when much of the conversation takes place off-list. I suppose I don't have any evidence of that there is off-list traffic. I read just about all the list traffic, and some very interesting topics come up and then seem to dissipate without resolution. Additionally, when I feel less than expert with my own replies, I will keep them off list rather than risk embarassment; thus, I assume that there is significant traffic off the list. At any rate, I would like to see all the replies, even the less informed solutions like my own. So for what it is worth, I will commit to summarizing the responses to any questions I may pose, with comments on the efficacy of the suggestions, and including my own solutions gathered from other off list sources (ni.com, tech support, etc.). If it is worth asking for help about, it is worth summarizing. In this way others can more quickly find soultions in the list archives. I will put the word summary in the subject line of the post. Mike -----Original Message----- From: R. Glenn Givens [mailto:[EMAIL PROTECTED] Sent: Sunday, March 21, 2004 6:23 PM To: Michael Ross Cc: LabView Discussion Group Subject: your suggestions for the list Michael I like your idea of the person asking the question to summarize the general conclusions & alternatives in one final email (unless there were just 1 or 2 responses of course). I have done that sometimes and the response in my "Sent Items" folder is there for me as a summary too. R. Glenn Givens P.Eng. Innovention Industries Inc. Burlington, ON, Canada www.innovin.com
