Thanks! Yes, it does, and what you described is what I'm trying to do...build a generic binding manager. The manager loops through all the controls passed to it, and I was wondering how I was going to write the code to determine which controls to 'bind' and which not to.

I figured that to do so, I'd need 4 properties for each control where I wanted binding to take place...coincidentally, I read the article in the UT magazine by Kevin M. on data binding in MM.NET, and he mentioned 4 props that MM.NET used for binding, and they were the same 4. Nice to see I was on the right track...for once!

Thanks, Bonnie...
Kevin