Hey Craig,

>Not everyone has current PCs. IMO, many of our clients will suffer.

That may be true but VFP needs to be more in the family than out. The more developers that can cross pollinate from VB & C++, the better we all are. Besides, you can still use the old tools for the old PCs. Tougher on you but does not hold the product.

>>3) Development Environment.
>>IMHO, MS can revamp the whole development UI but keep the "command window". It is this that differentiate VFP from other development tools. It is a sort of "dos prompt" for developers.
>
>No, I disagree. If any changes to the Development UI, it will be to integrate it into Visual Studio shell, which I hate. It's much less productive than what we have now.

I agree that VFP's env is better but knowing two env's is a major pain and again will keep people from VFP. There are some things I like about the other env like editing property values in the grid rather than a special box.

Guess I'm more of a move forward and let the rest catch up type.