>Exactly, you say it right: HIS goals, not saying anything about the goals of others. JVP really did not understand the value of the database engine. He simply had no clue what he was talking about. Time has proven he was wrong. Microsoft now is admitting the importance of deep data integration and why it needs to be in there, thanks to the VFP - team.
>
>The problem as JohnRyan said, is that there are VFP developpers that really develop in the VB/SQL server style. Not doing much with the local data engine. No post processing, no data munging etc. Those indeed would have little trouble to go to .NET/Java/Delphi or whatever. When things start to get a little more complex you're faced with problems that take a lot of time to solve. How many times did we see messages over here about post processing ADO.NET recordsets ??
>.NET currently is a huge step backwards for those who heavily use the local database engine for all kind of things (not just DBF style access). Things will improve on this area as we have seen from microsoft with the LINQ project. But lets first wait and see.
>
>Walter,
>
>What's your practical experience with .NET? How many applications have you developed using it?

C'mon, Kevin, that's hardly a sensible question!!! (make that two)

Why would one be expected to invest all of the time necessary to learn .NET adequately to deliver an application or two when there is enough written out there, by trusted individuals, describing countless shortcomings of the platform???
I mean, you are at the ready to accept literature that is in line with your goals and objectives. Why can you not accept the same for people who determine that 'now is not yet the time...' when it comes to adopting .NET?

I'm sure that someone *can* do just about anything they need to do using .NET. But to many of us it still looks like it would be like using s chisel to build a whole house and we want to wait until it adds a hammer and a saw. Why is it so hard for you to accept that?

cheers


>
>Kevin