>noticed that the INSERT is actually part of the stored procedure.

That part was obvious. I was distracted by the possible NULL (or rather empty value) on the insert, and thinking about that. still got it wrong, just not sure this example focused on the point you wanted to make; could be composed better.

also, are you guys really faced with this issue? for what it's worth, i've never confused what statement are in, or not in, the procedure.

>scripting

ah, i see why you're annoyed.