PMFJI Walter but I just cant resist, your last couple of responses seem to lack common sense... perhaps I'm just not grasping where your trying to go with this.

>>If people are concerned about this, and if people think this is a possibility, all the more reason why people would want to look at other tools..
>
>Yep, this is one possiblity, the other is gaining as much info on VFPs future as you can get an guess there will be a VFP 8.

Considering that "gaining as much info on VFPs future" is something we can not control, we can only get as much info as M$ cares to divulge... this remark seems quite silly to me. I dont about others but I'm am not about to hang my career on a "guess". Learning another development tool is like an insurance policy in my opinion. And the fact that M$ has delayed VS7 gives all of us ample time to cover another base in the game of technology so that we not left with holding onto a guess.

>>Only to the people that did not take time to learn...
>
>I think the word 'take' could easely replaced by 'have'. As we both know there are so much technologies and new products we already must/should learn you could easely make a full job out of learning. I think most of us are really selective about what is worth learning.

If a developer waits until they "have" the time and dont "make" or "take" the time to learn another skill, that developer stands absolutely no chance of holding any ground in a field that changes as rapidly as ours. These are the developers that are typically stuck in the proverbial box and are blind to the fact that their relevant experience is dripping like sand in an hourglass. These are the same sort of developers who preach about product or tool they've never used and/or never seen the latest version yet feel they know enough about the product to make informed decisions. The same type of developers that get left in the dust in this dog-eat-dog job market and yet have no clue how sheltered and limited their skill set really is.

>This has never become quite clear to me. What exact things can be done in VB and cannot be done in VFP and is really worth the cost ?

Technical issues aside, one REALLY BIG thing can be accomplished with VB skills and not VFP skills - marketability of a developer's skills and experience to a much larger and faster growing job market. IOW - better job security. Add in the fact that the "B" in VB alone makes it more applicable than VC as one of those extra notches a VFP developer can put in their belt in a shorter period of turn around time as far making that extra tool a billable asset.

>I agree, but if you're a hardcore VFP developer looking for more absolute power, C/C++ might be the tool you're looking for.

I dont know about you but I get so much power in VFP that "power" doesnt count as something I look for when I want to expand my billable skills.