ScottPletcher (8/13/2013)
That code's written for SQL 2000; I suggest completely ignoring it.
I wouldn't ignore it because it was written for SQL Server 2000... I'd ignore it because it solves the wrong problem for the latest request.
--Jeff Moden
Change is inevitable... Change for the better is not.