Nah, Bonnie. The problem is that coming into the parsing routine it comes down to knowing what the control is to match the parsed name. If you don't, you are stuck with a generic Control class init and that doesn't work when looking for a non-generic property.

Like I said, I found a workaround but....doggone it, this should have been easy.

>Paul's suggestion should work, or at least point you in the right direction ... perhaps something got lost in the translation to VB?
>
>~~Bonnie
>
>
>
>>No, I suspected before I posted it. I ain't that dumb.
>>
>>Postscript: Tried Paul and Mike's solutions and neither worked...although kudos for trying. I kinda gave up on that approach and moved on. But it occured to me that .Net really needs an equivalent to the EVALUATE() function. I don't want to use the word "literal" since .Net has already hijacked it for other uses but maybe we need a CTxt() function to convert a string to what we call a literal. I was talking to some .Net gurus today and they agreed. Man, that would be useful.
>>
>>
>>>>Friggin's .Net weirdness.
>>>>
>>>>Thanks, Paul. I suspected the solution had something to do with reflection .... I'll try this tomorrow. Appreciate it.
>>>>
>>>
>>>Only suspected after 3 people suggested it? :)