>You are obviously working on large corporate systems which will almost certainly be yelling for .Net/SQL because the business magazine acticles tell them to do so.
Bob, I can't believe what you have said above. Do you really think that big business spend on .NET/SQL because "the business magazine acticles tell them to do so" ??? The company I am currently working for are very shrewd indeed. I am a long standing FOX/VFP developer (since 1989) and I can tell you that the tools I am using right now are totally right for the job and VFP has been usurped because the company have simply outgrown it, and its capabilities. To suggest that they have been "tricked" by business magazine articles is Fox-oriented wishfull thinking on your part.
>In this case your skillset is determined/demanded by your employer/customers.
Isn't yours? I can work for a VFP customer or a .NET customer or a SQL server customer. I have no axe to grind, irrespective of the tool or platform any customer would require. If the customer had no preference about the technology and just wanted a system that did the job, then I would choose the correct tool for the job. It wouldn't automatically be VFP because the customer didn't have a preference (or a clue).
>We have not found anything we set out to do that we havn't been able to accomplish with VFP.
As Fox developers, we look(ed) towards not only MS but talented Fox Gurus to help us find ways to make VFP do things it was never designed to do correctly or efficiently. So, your statement above doesn't surprise me - however, this doesn't mean that forcing a square peg into a round hole makes for the best solution - a solution maybe, but not necessarily the best one.
>I personally think .Net is still one or two versions away from where I want to invest my time/energy to get involved with it
Like the thread originator who invested a whole three months into C# before scurrying back to Fox, it would appear that unless you have spent sufficient time with .NET, you are not really in a position to make the above conclusion. I can tell you for certain, that with .NET 2 / VS2005, there are few cases where I could see any advantage to using VFP, even for the smallest applications. I can say that on the basis of my experience with both tools.
>and I forsee no problem keeping busy and earning a GREAT living using VFP.
Kudos to you and power to the Fox - I am sure there are many people making a good living using Fox. It just dried up in these parts many years ago so you either change skills or change occupation.
-=Gary