In this case I need to set about 15 variables to an empty string. So it saves me a lot of lines in the stored procedure by doing it all in one SELECT line.
>Depends on how many variables I'm setting. Generally, if 3 or less I go with one line - otherwise it gets too 'busy' and can make it difficult to maintain, especially for those who 'inherit' the code. I can't tell you how many times I've had to resort to 'Find' to find where a variable is getting 'reset' and finding it in the middle of a 30 variable store statement.
>
>
>>
>>I see now. I understand that you prefer multiple lines. But if I use my syntax (SELECT...) I can put it all in one line. I am just trying to make my stored procedure, where I have to initialized tons of variable to a empty string, shorter (fewer lines so that it would be easier to read). Do you see anything wrong with this SELECT of multiple variables?
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
