>For those that currently use VFP, this definitely applies. But what if the work has dried up or they want to expand to clients that do not currently use Fox because of higher paying work??? I see dotNET providing the first feasible alternative for VFP developers, this accelerating the pace at which VFP loses developers.

I have to agree. I have said for the past few years, if VB or a product with the marketing behind it simmilar to VB and Windows comes out of MS, I will make every effort to learn it, and get it on my resume.

Well, here is C#, what I was waiting for. So I am following through. Is it a fall back for me or my primary focus, I don't know? I do know that the developers on my team, one that just delivered a VFP/SQL re-write of a Fox2.6 Payroll/HR product, we have decided to develop or first add-on module, a web based Employee Self-Service piece, with C#/Asp.Net.

We all love Fox and its capabilites. But, we also always hear the questions about why isn't it in VB, blah blah. Even from internal folks. This is a company that has thier Enterprise C/S ERP suite written in Power Builder... although I think they are migrating some of it to Java.

Anyway, all that said, I don't understand the doom and gloom thread. Is VFP declining, maybe. Is the IT job market 1/10 of what it was 4 years ago during the .Com boom? Absolutely. Are there less VFP jobs than VB, yep. Well, there are less VFP developers too. I just think if everyone put as much effort into learning .Net (insert any other language here) as you do in arguing (hopping) about how VFP will live forever, you would do yourself a service.

Look, everyone thought COBOL would be dead now too. But it goes on.

So lets agree to disagree, and move on. No one is changing anyones minds.

BOb