Rod,
An app that displays and allows editing of subsets of remote data is *easy* in any contemporary development tool and is unlikely to benefit from VFP's local data ability which (as we've discussed before) is VFP's defining feature.
IMHO such a comparison serves little purpose unless to assist dotNETers who want to assert that dotNET is just as good at "data" as VFP!
I also have to ask: are we a victim of our own FUD? In 2006, millions of small businesses use Quickbooks without knowing or caring in what tool it is written, or wanting to jump ship because it uses proprietary file-based storage. Could it be that not all customers see "development tool" as a relevant selection criterion, or perceive shared file-based data as a major risk?
Though I've used remote data for over a decade, the above still strikes me as a huge opportunity. Why exclude it?
"... 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
