>Agreed- it's a complex way of doing things if there is a simpler alternative. It's also not as suitable in NET as it was in VFP so I agree with you that unbiased consideration in NET often will lead to an alternative. I only asked because I interpreted your original comment as saying that eval() shouldn't have been in VFP, even though it was effectively free in VFP; but now I see that you were talking about avoiding it in your own NET product.

With everything new I would have do deal with, no matter the environment, I would try to avoid that and find a more convential route.