>
1. People are affraid that VFP is going to be discontiniued in the long run. So every clue that points to this direction is jumped on.
>

If people are concerned about this, and if people think this is a possibility, all the more reason why people would wan't to look at other tools..

>
2. Integration of two or trhee different languages brings technical and knowledge problems, especially for a small team and single persons.
>

Only to the people that did not take time to learn...

>
3. I don't know why you insist to look at VB 7. Personally I think that the combination of VFP and C++ is a lot more powerfull than VFP and VB. O.K. C++ is more difficult to learn than VB, but thinking outside the MS box might be another choice (Delphi).
>

VC is a hard pill to swallow. Most things that a VFP developer would need to do are accomidated in VB. Of the two environments, VB is the easier and more correct path to go down...