>If I was re-trained I would be sitting back and be relaxed, but that might not be the case.
>
>As for getting a new job, that's impossible without moving 300 miles away.
>

Hey Kev,

This, IMHO, is *the* issue. Whether MS supports/defends/promotes VFP, or that VFP can do this-or-that, or that VFP8 thru VFP29 are "in the works", or that managers make poor tech choices doesn't matter. Neither does it matter that anyone here responds like "Dead? Schmead? I just wrote a VFP app...doesn't look too dead to me!!" (It seems independents cling to this.)

If *you* can't find employement with VFP in any practical and vital way -- it's dead for *you*! If you are an employer, "to FoxPro or not to FoxPro" is NOT the question. Rather "in 5 years where will we find a VFP developer?" is the question. Hiring for VFP will continue to become more difficult -- i.e. it's not a practical business plan to build on VFP today AND expect VFP tomorrow. This trend for the Fox began in the 90's and will place VFP into the more arcane. And anecdotal old f***s on UT talking about Cobol, etc offer nothing toward your mortage payment, do they? :-)

By analogy, species extinction may result from a breeding population too low to remain viable. The last surviving groups may linger for a considerable time. But perhaps we don't want to feed our families by relying too heavily on Fox hunting?

Regardless, best of luck to you man. You're not alone with all of this.

Steven-