>How about developers beeing force to use a certain tool because it is demanded by their management or client for no technical reason ??

As a consultant the customer is usualy right ;) In terms of "I want it done in this tool." I long ago gave up the single tool toolbox. It's their nickle, and I'll accept as many as I can get if they want to keep pushing them out.

>>I can tell you from experience that you will not get a VB6 developer to use VFP except in very rare circumstances even when demonstrating how much more productive you can be with VFP than VB6.

Much like you won't find a VFP develper picking up java, for any reason. It's a comfort factor.

>I'm still waiting on Microsoft to announce a new development platform where RAD and Database integration has the foremost priority. From my idealogical standpoint this is the wave of the future. I'd like to promote the sentence: "Every application wants to be a database application when it grow" to "Every development tool wants to be a database tool when it grows up". .NET in any way you put it does not fit the bill. I'd rather wait for the announcement of the tool (Microsoft has some research projects going on that are more data centric), than hastly jump the wrong ship. I'd rather jump once into the right ship.

hahahaha. Not ever tool plays well with others. .NET does a great job in attempting to deliver on that line. VFP can't, wont and that will be it's final pox.

You seem to be comparing a 20 year old product xBase to a three year old single version product .NET. Version 2005 has allot of improvements. More so then VFP6 did over 3.

.NET is great at the little stuff. Like making a picker dialouge that will showcase images instead of details or plain file names. When you get to the nitty gritty VFP won't ever do it and you only have to roll your own each and every time.