As this has been a problem since the beginning of time, one would have hoped MS would have come up with a solution to create a backup into a previous...

Fair enough - in the case of number to word using built in functionality is probably preferable .... this was a very specific thread and my response was more 'generic'.......

I don't have access to the function right now but will try to post it later... When I say simple I really mean the call is simple. We handled it...

I'm not sure why doing it on the front-end would be 'better'. By doing it in SQL it remains accessible and usable from ANY front-end, report writing, views etc.......

Alternatively, if the input parameter is allowed to be 'missing' you can get around this by including a default value in the stored procedure definition - eg.

CREATE PROCEDURE dbo.SDoinidis_Duluth_LicenseeActivity

@Address Varchar(163)...

I agree that any references to fields in the # table cannot be checked - my problem is with fields in the Permanent Table. The UPDATE statement is updating...