Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
VB, C#, and VFP data handling examples
Message
From
24/04/2007 19:19:27
John Ryan
Captain-Cooker Appreciation Society
Taumata Whakatangi ..., New Zealand
 
General information
Forum:
Visual FoxPro
Category:
Visual FoxPro and .NET
Miscellaneous
Thread ID:
01215120
Message ID:
01219587
Views:
27
I will be taking a look at dLinq as well as other LINQ stuff real soon now. I don't think that LINQ will help you at all for this stuff. Maybe the entity framework will but that's yet to be determined.

I'm afraid there is a severe disconnect here, with no change tracking. ;-)

Maybe I missed some part of this thread where you are comparing DLINQ (where the Q stands for Query) to typed datasets. They are TWO seperate technologies altogether. One does is not a replacment for the other. I don't really see dLinq replacing the dataset at all.

That's the entire point. As per my earlier response to you: somebody else said that typed datasets were rendered obsolete by entities. I decided to investigate and ran smack into the change tracking issue. But according to some here, change tracking is a "WHO CARES" issue anyway. I choose to disagree with that at this point. I also think that dLinq *is* a viable replacement for Typed Datasets if it includes change tracking and the in-memory features described recently by Anders.

It has nothing to do with VFP or .NET at all. We have an approach that has served us and our clients very well over the years. This approach uses stored procedures and our own custom framework for dealing with stored procedures. Personally I never liked remote which I know you and I have discussed here ad nauseum.

This is the first time I realized you've done away with change tracking.

I don't really like black boxes that do my updates for me. And IMO the native dataset updating and remote views share the same issue. They are black boxes. I guess I am too much of a control freak to let that go :)

You have to at some point... unless you've checked out the underlying code that makes SPs work? ;-)

I think you overgeneralize here but OK.

I can assure you that the RV has *definitely* offered change tracking and contention management since 1995.

Actually I dont think I have ever said that at all. We ALL have different approaches to problems. But... if you do decide to move to .NET you may find yourself trying to stuff a round peg into a square hole.

Why do you say that?
"... 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
Next
Reply
Map
View

Click here to load this message in the networking platform