Perry,

>You are one of the more knowledgeable folks who is still here after several years.

Thanks for the kind words.

> If you really want to discuss what helps the VFP community, I really think we need to discuss helping VFP developers to learn other tools.

I've always said that developers should have multiple tools at their disposal. I've had the current Microsoft "C" compiler installed on every machine I've had for the last 20 years.

>There are a group of developers who develop apps for small shops or develop off the shelf apps for verticle markets. Developers who fall into these groups can select whatever development tool they desire. They are free to find another client if that client has stated that they will not consider software written with a tool such as VFP.

VFP is not just relegated to small shops/apps it is still used in large corporate systems as well. Perhaps not as much but it hasn't been pushed out the door of every corporation yet.

>However there are many of us whose career depends on filling specific needs as corporate type developers. 6 or 7 years ago I could depend on being able to easily leave one VFP gig for another. This is no longer the case. There are some who seem to want to deny that the use of VFP has dramatically declined over the last several years.

Market demand is what it is. I'm sorry to say that far too many corporate decisions are based on some "Gartner Group" (or some other pundit that think they have "the answer") study of the day, instead on a real hard technical merit of comparing the alternatives. In 20 years when I'm getting ready to retire I'm pretty sure I won't be using either VFP or .Net they will each have been replaced by something better.

What I mostly disagree with are the "change now or die" sorts of messages being thrown out. Most everyone here is an adult capable of making a decision about what their current tool of primary choice will be. Different people are at different stages of their careers and messages that declare "you have your heads in the sand" don't accomplish anything but causing threads to degenerate.

>I appreciate the fact that others who have felt the need to use other tools want to share their experiences. Unfortunately, others want to keep the UT pure of discussions of alternatives to VFP. Whenever the subject is brought up that you can accomplish you goal with another tool, they are shot down. Especially when the recommendation is to design your app in a way other then "THE VFP" way.

Neither you nor I have any control over what gets posted beyond our own messages. You don't see arguments ensuing in actual technical question threads in either the VFP or .Net forums. Sharing experiences is good, unfortunately that sort of constructive discussion rarely happens. There is no one way to ever do anything.

>I agree with John B. that the level of technical discourse on this forum has decreased substantially in the last several years. Unfortunately, I don't see anything causing a change in the horizon.

It's threads like these that greatly contribute to that. Name calling and Language X is better han Language Y arguments are in a word: childish.