Jerry,

>>As usual, your insight is brilliant :)<

Well, I don't know about that, but thanks anyway! =)

>It now works since assigning the property to another string variable, as you suggested.<

I don't know if that was the best way to handle the problem or not (hence the disclaimer about my being brilliant <g>), but it's the only thing I could come up with off the top of my head. If anyone else cares to take a stab at it, be my guest. =)

>>It would be nice if someone posts why MS decided to have this behavior in .Net. Sounds like a bug...<

Thoughts anyone?

~~Bonnie