>Hi Scott --
>
>>I just wanted to toss in some experiences I have just run into. I'm switching divisions in my company. The new group I'm going to has people with FoxPro/VFP experience, but we are not being allowed to use the tool. We can write our own utilities for personal use, but anything going to an end user has to be written in Access and VB. Demos have been put together showing that VFP outperforms Access for the types of applications that they are writing, but these have been ignored. The mindset of management is that VB is the way to go because MS does not stand by the VFP product. The lack of any real advertising in comparison fuels this argument. Finally, because VB is promoted so heavily, we can no longer find any experienced VFP programmers for full time work, or graduates who are willing to work with the language. The lack of bodies willing to work with VFP is another driving force to eliminate it as a viable tool in my workplace.
>>
>>Do you see this trend out in your area? I'm in CT.
>>
>
>I see this exact same thing and this is what is driving the frustration everytime there is a perception that VFP is being slighted. I live in North Florida.

John, you could live in any part of country to say this. For years, Foxpro is like besieged fortress: not the best situation, but defenders are extremely busy (working in this case on VFP projects). Will this fortress fall? Of course, yes, because resistance is futile..., but in this situation it just means that we will move to another fortress (i don't know the name), and not so soon, and there are so many good things beyond the software world. It seems to me that these "live or die" threads are getting too long :).