Fernando,

Just an FYI...I was part of that same discussion with a few noteables - soliciting opinions about whether Fox should be part of .NET. This by the way, goes back about 4 years - just prior to when started law school.

As I recall, I was either the lone dissenter - or one of two. My opinion at the time was no - fox should not become part of .NET. I proferred two reasons.


1. To take Fox out of its current environment would be to in effect - complete the dis-enfranchisement process process that Fox developers have had to contend with for several years. i.e., the product would become just like VB. This gets to the second reason

2. Technically, based on the ground-rules from MS - it would have been a no-go. As a condition for Fox going to .NET - one would have to contend with the loss of the VFP cursor model. As much of a technical reason this is - it does relate to number 1 above. Again, you would have something that would closely approximate VB .NET. And if that were so, why bother? Why devote the resources to what would be a wasted effort.

Guaranteed Fernando, had MS tried 4 years ago to port Fox to .NET, you never would have seen VFP 8 or 9.

If you want Fox to remain in existence as long as possible and understood the issues involved, you won't ask questions like this.

In a nutshell Fernando, been there, done that...these discussions already occurred, with people that actually had the power to make it happen....