Let me be the first to say, "You are da man!"

We have always avoided CLR like the plague, mainly due to deployment issues. We keep a delta of all SQL changes, and just did not ever want to include CLR integration in the deployment mix.

Assuming everything works okay, this method will be "worth its weight in gold". Thanks for giving us a "go to" should the CLR need arise, which is actually on the drawing board...