John, I always find your comments insightful. I would add that since VB7
will now have inheritance, this will inch closer to the death of VFP.
Now, PLEASE, everyone, do not flame me on this statement. I love VFP but I
see that VB will (within a year) have inheritance. I would not be surprised
if it also had a built-in data engine as oppossed to hooking into SQL Server
or Access. They might even roll the VFP language into it. I really do not
know. What I do know is that MS loves VB to death and most of MS does not
even know VFP exists. And the corporate world thinks VFP is dead so we have
a self-fullfilling prophecy.
So, VFP may go the way of the buggy whip or may transform into VB directly.
In a world gone insane.
Carl
>I think there are several reasons. I could be wrong on some or all of these, but here goes:
>
>
1. FoxPro is considered legacy, regardless if Visual or not.
>2. If Fox dies, no big deal. If VB dies, MS might be toast.
>3. There are 10-12 times more of them than us.
>4. No one is doing technical review of the material MSDN posts.
>5. Someone IS doing a review and getting VFP quashed.
>6. MSDN folks may already think VFP is dead. Who knows?
>
