SNIP

They celebrated when VFP became part of Visual Studio then they celebrated when it came out again. Other leaders splashed FUD about. Some leaders became smug and "elite", losing touch with the community they purport to serve.
>

Without going into the many reasons that BOTH of those milestones were reported to be 'the best thing for fox,' we benefited when VFP was included in Visual Studio. It was a much easier sell as our tool of choice when it appeared to be part of an accepted and standardized package.

Now the reverse has happened. Simply because VFP is NOT a part of .NET (whether or not it is still the best tool for the job does not matter to some managers) -- business managers are worried about using it. They are afraid that either it will not be around in 2-3 years and they will have to invest in another tool or developers will not be available in 2-3 years and the same will hold true. It's amazing how easily FUD spreads panic...

Tracy

.·*´¨)
.·`TCH
(..·*

010000110101001101101000011000010111001001110000010011110111001001000010011101010111001101110100
"When the debate is lost, slander becomes the tool of the loser." - Socrates
Vita contingit, Vive cum eo. (Life Happens, Live With it.)
"Life is not measured by the number of breaths we take, but by the moments that take our breath away." -- author unknown
"De omnibus dubitandum"