Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
VFP and .NET Data Comparison
Message
From
05/01/2006 13:15:24
Walter Meester
HoogkarspelNetherlands
 
 
To
05/01/2006 04:51:22
General information
Forum:
Visual FoxPro
Category:
Visual FoxPro and .NET
Miscellaneous
Thread ID:
01080965
Message ID:
01083682
Views:
25
Hi srjdan,

Sorry I've missed your private message. I've seen your solution, though I really have not tried it. I do have somewhere my own solution and was going to compare my with yours from a performance standpoint of view. However I do have some other priorities, so I'll check it when I have the time. Meanwhile I just want to thank you for posting your solution. If not for me, it now is recorded up here for anyone who needs it

Thanks again,

Walter,

>
>>Hi srjdan,
>>
>>>>>Yes, you can pass datasets around as they are objects. You can now also serialize them in a binary format when passing across application boundaries (provided both sides are running .NET apps).
>>
>>>>That is cool, and something I'm missing in VFP. I can of course translate it into XML, but it is too slow. Another alternative is using arrays, but memofields are not supported then.
>>
>>>What is wrong with passing cursors as object.properties ?
>>
>>Well, I'm not sure what you've got, but it is a few steps too many and in general either not flexible and transparent or too slow. Can you show what you've got developed. Maybe I've missed something I could use.
>>
>>Thanks,
>>
>>Walter,
>
>
>I had this kind of cursor 'traffic' between sessions objects supported for years now, using pair of functions and one custom object but without support for memo fields. I had need for memo in only one case so I resolved it on the spot back then.
>
>Now that you asked me for it, and also noticing similar question reappearing here from time to time, I invested couple of my hours to provide generic solution that will support memo fields as well.
>
>Funny thing is, that I got NO reply from you at all ??
>Not on first, nor second (correction) nor even private message I hv sent you
>thinking that you haven't noticed my message because thread is progressing fast, you were busy or so ...
>
>Now, since almost week passed, I got indulged to ask why that would be,
>aldough I am not sure should I realy bother myself talking to the Wall.
>
>Final result of that development is published here ( See FAQ#29297 ) and I hope you will enjoy it for your favourite 'datamunging'.
>It is very simple and it works just fine.
>
>No matter how badly it was done, even if just one person find it usefull and make some solution out of it, it was worthed bothering to respond at first place.
>
>Have great & productive day.
>( & Don't bother responding )
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform