David, yes, I first tried ADO.NET in 2002. It works well until you meet the scaling and resource limits caused by memory residency as opposed to the automatic disk spanning of a VFP cursor. MS has recognized this and plans to offer disk spanning in a future version. This contributes to the "SQL versus DBF" issue as well if you consider the sorts of companies who will be using one as opposed to the other.
Re databinding- I assume you used to bind fields in a VFP form before you started your dotNET work. Are you using databinding in your dotNET work?
regards
j.R
"... 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
