Tom,

>>Perhaps you're missing the point.
>
>Steven;
>
>For those that think a handfull of jobs scattered through out the country is a sign of high employment for VFP developers, I would suggest that some of us cannot easily take up stakes and move.
>
>How many VFP programmers are doing VB? How many FoxPro programmers were there in 1994 compared to VFP programmers today? How much FoxPro vs VFP work is done today? The reality is there is not as much VFP development work work as there is using other specific tools at this point in time. From what I can see there is much less VFP work today than say four years ago. That does not mean that there is less passion on the part of VFP developers but you have to have some concept of what the market demands and for those that want to put his/her head in the sand, that is not the answer.
>
>Awareness of market trends for developers is something we should all be conscious of - and looking at time lines as well as physical areas allows us to better understand what the "big picture" is for ourselves. We can only assist each other with such dialouge and stir each other to ask some important questions. We can take the data as we wish and some people will take action while others will not.
>
>Some people developing in VFP will feel that "I have a job, so who cares"? Come back in five years and we can discuss where the land of developers and ourselves can be found.
>
>Tom


I think your points are valid but would add that for those who know VFP they have an advantage the others do not. Learn what you need to provide for yourself and your family and take time to learn what you enjoy.

I think that VFP programmers will have work for quite some time and that they should also keep their other skills sharp as well. My problem with sharpening my other skills has always been that I've been far too busy with Fox-related work to take the time.