• Thanks for the additional info. Looks like SQL 2008R2 has fixed this issue but it does exist with SQL 2008. I have not installed SQL 2008 R2 as that's for another article.

    Thanks again,

    Rudy

    Rudy