John,

>Nor do I accept that VFP is doomed. Even if MS dropped it completely, I would argue that VFP6 or VFP7 would allow people to create cost-effective solutions for years to come.

>Exactly, but you also need to look at the market place. You need to look at the overall demand relative to other things. As I have said on many occasions, the viewpoint tends to get myopic.

I don't buy this stuff. Sure it is wise to know something about other development environments, but it surely does not justify to spend a whole lot of time in it. You've been preaching to look at VB 6 for a long time because VFP jobs might dry out. The fact: VB 6 is dead. You've got a nasty habit of trowing arround real bad advice. Advice that no serious self respecting VFP developer needs. Anyone knows that he/she has to have an alternative when jobs dry out. In meanwhile do the things you're best at: Developping VFP applications. It makes no sense to be a midstream programmer in various languages. Pick one and specialize yourself.

You're virtually saying, if the demand for VFP jobs shrink just jump the boat. Hmmmm, how would this apply to the good old COBOL programmers making an awfull money ?

Walter,