Yep, sorry about that... I got a little frustrated with you... everyone has been trying to tell you that you're asking for "Death by SQL" by doing the UPDATE right...

There's really no physical problem to keep you from using it... However, Microsoft and a bunch of folks on this forum have indicated that in order to guarantee that your...

I guess I'm just going to have to materialize this code and test it...

Would you post the CREATE TABLE statement for the two audit tables and the CREATE FUNCTION...

And, you need to be real careful if this comes anywhere near a GUI... think "SQL Injection".  Theres a huge amount of info on how to prevent it... do a...

I guess I don't understand... obviously, you are finding the correct Windows user name somewhere along the line in your stored procedure because you want to "pass it" to a...

It's the triple quotes in the variable assignment that are the most recent problem...

Try this...

declare @townID varchar(25),

     @sql varchar(1000)

set @townID = '00003' --<<THIS IS WHERE THE...

Old guys rule...   1 million conversions... 11 seconds... works for positive numbers, negative numbers, zero, and NULL...

DECLARE @Places INT

 SELECT TOP 1000000...

If you run this code, you might just want to have your DBA turn on Trace Flag 1204 just to be safe