>Hi Kevin,
>
>I'm not sure if you read the following messages.
>
>Mario Montoya: Re: Which is best for Desktop Apps VFP?.NET Thread #860600 Message #861017
>Rick Strahl: Re: VFP .NET killer Thread #856627 Message #856716
>Cetin Basoz: Re: It would be nice to have some constructive VFPvs.Net pos Thread #861269 Message #861341

I have briefly scanned these messages and until I see documented proof I won't be persuaded, and that is no disrespect t any of the above members in the messages, that is just the way I work.

>
>>I agree with this entirely, having a data-engine integrated into a language is "not" flexible, I actually "like" the idea of using classes to access data, maybe that's because I've gotten into OO quite a bit, maybe not, who knows.
>
>These quality messages do show what is wrong with Winforms and that handling (local) data sucks in .NET. Are you disagreeing with the statements for example RickS has made here ?

No, in fact I'm not even going to involve them like you have, I'm going to start with my own tests and when someone points out something I've missed, I'll be happy to acknowledge it.

>I also Don't see why an integrated data engine is NOT flexible.
>
It's integrated into the language, it is far more flexible to have the data-handling done using classes, it may be slower, yes, but it's still more flexible.

>>The way everything is seperate in .Net is nice, you have your language, then you have a set of classes, which are seperate, the Database is always seperate, not tightly bound - it's not a bad thing, it adds a lot of flexibility and until you can fully appreciate where .Net is coming from, most people won't get it.
>
>So you're saying RickS did not get it. Nice statement.....

Still talking about Rick again? Like I said, I'm not involving anyone here, I will post results of a test I'm running in a minute as I like to see things in concrete form first.

Kev