Thanks for the response. That seems to be the same thing as using isnull or coalesce functions, though? I'm looking more for a setting in SQL 2005 to make it so the 'NULL' value doesn't actually return in the output. Otherwise we have to add isnull or coalesce to every single column in the final query of a script. SQL 2000 was this way by default (if your default output is tab delimited text). Maybe a bug in 2000 or 2005?

Sorry I should have made that more clear

Just sort of a nuiscance. We do a ton of ad hoc reporting straight from our various data sources and some members of our reporting audience get confused by the NULL value so we have to either use isnull, coalesce, etc, or find / replace when data's exported to excell...