One other thing... find your local .NET user group and attend every meeting.

>Guys, I have run into very little FoxPro work since my lay-off back in November of last year, 2008. The jobs are becoming more and more scarce. IT Departments shoot it down. Microsoft kills it too by its decision to not market the Fox.
>
>Visual FoxPro is still an outstanding product. It is probably more popular outside of the United States and Canada than here in north America.
>
>Compared to Microsoft's .NET products, and I did research to prove this, there are few opportunities with the Fox now. When you go to, for example, http://www.indeed.com, and put in FoxPro and a city and state, FoxPro comes up with 0 to 1, or maybe as high as 2 opportunities, but Visual Basic and C# come up with 40, 50 or hundreds of opportunities depending on the city you look at. We can still build good apps in VFP, but if no one offers work in VFP, but only in JAVA, ColdFusion, VB, ASP.NET, or C#, then you have to go with the market, which in my case, means completely retraining.
>
>At age 56, it is very difficult to stop everything going on in my life and retrain mself to some other software development tool and who is going to hire a 56-year old man who just started learning C#?
>
>I guess I need some cheese with my wine, right?
>
>I've even taken California's teacher exam called CBEST in order to qualify me to teach here, but they are not hiring anyhere in the 11 school districts I've called.
>
>For years I've loved using Visual FoxPro and the old FoxPro for all of my development; it made sense.
>
>Any advice is genuinely appreciated. I am feeling kind of lost now.