Yes, it is. It is a highly complex way of doing thingsAgreed- 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.
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us."
-- Shakespeare: Coriolanus, Act 1, scene 1
