>I saw your post over on MSDN pointing to the solution you showed me over here on UT.
>
>I have posted a few Q's there, but I rarely get many responses. That seems like a busy forum, but I sure like UT a lot. I wish there was more traffic here, because I like the format, and I can really learn a lot from reading the topics that other people are discussing.
>
>Also, I wish UT would allow attachment of screen shots. (not that MSDN does).
>
>>You're welcome glad I could help.<g>

I was trying to get my second medal back on MSDN<g>

UT has been an invaluable resource for me at times, so I tend to come here first. For most of the topics here, by the time I've read them someone else has already answered them. So I keep an eye on the WPF stuff since it's pretty much just me and Viv and now you with WPF experience here.

I get bored with my own questions sometimes and I also find that I learn a lot by answering other peoples questions. It forces you to look at things a little differently sometimes.

But there is not a lot of traffic here on WPF so I do some posting over on MSDN as well. The MSDN WPF forum is so busy that many posts don't get answered till Marco (the Moderator) gets around to them a week later, he does a good job, but it's just too much volume. C++ stuff over there gets answered almost as fast as here by comparison. It's just too many people with questions on WPF and too few with answers at this point.

One thing on the original subject of this thread... not sure why but I just ran across a case where SelectedValue didn't work, I had to change it to SelectedItem and then it worked fine.