>>>No matter that VFP was a part of Visual Studio. Decision makers still would not use VFP.
>
>Hi Tom,
>
>I have to disagree here with you. My experience may have been unique, but during the 7 years I worked for the govt, Visual Studio was specified as the tool to use for govt apps. Since VFP was a part of it, we did all of our data development in VFP. In my case, it was a blessing--it allowed me to use my tool of choice. The govt is now revisiting its development requirements. They are BIG on standards.
>
>Tracy

Tracy;

I must admit that my experience is limited to Northern California and Nevada and cannot speak for any other area of the world. I am glad that there are those areas where VFP is popular.

We have a huge Microsoft office in Mt. View. During the period from 1994-until the present the staff at Microsoft has done everything it could to not mention VFP. VB was the product and it is .NET that Microsoft pushes today.

I have talked to over 100 decision makers of companies at different companies during the last 8 years and not one would allow VFP to be used. Why? Microsoft!

I have said specific things that occured at different events I went to where VFP was not mentioned. In fact I recall the 1997 DB Expo in San Francisco, where Microsoft pulled out at the last moment. No amount of discussion has changed the mind of any decision maker I have met. Microsoft said use VB or today .NET, and that is it!

It is evident that the number of jobs available in IT is down from 2 years ago. When the job fairs were being held in Silicon Valley (daily until April 17th of last year) you would see about 2000 jobs posted for Java and one for VB. This was the daily norm. Never was VFP mentioned. You heard about VFP positions from "back alleys", your network, user group or by blind luck.

Silicon Valley may be different in too many ways.

Tom