Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
VB, C#, and VFP data handling examples
Message
From
17/04/2007 21:34:38
John Ryan
Captain-Cooker Appreciation Society
Taumata Whakatangi ..., New Zealand
 
 
To
17/04/2007 21:16:40
General information
Forum:
Visual FoxPro
Category:
Visual FoxPro and .NET
Miscellaneous
Thread ID:
01215120
Message ID:
01217143
Views:
21
Perti,

.NET is missing OLDVAL()/CURVAL().

If you stay connected in NET, you have change tracking. I'm talking about a multi-tier app where you need to pass data between layers. Since data is in objects/entities in NET, you're going to want to pass the data in that form rather than inventing something new. But if you do that with an entity, it arrives at the next level with no change tracking. It's just a set of data, some of which may have been changed. it means the entity is fundamentally unsuitable for this purpose- at least until MS fixes it.

FWIW, If you pass data between VFP layers you also lose change tracking since you can't pass the open view. But VFP makes it easy to cherrypick the edited fields or include a Getfldstate(-1) in the returned data. To achieve that in an Entity would involve far too much work, IMHO.
"... 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
Previous
Reply
Map
View

Click here to load this message in the networking platform