John,

>One of many reasons. VFP is - in all material respects dead because:

>1. MS is making movements toward phasing it out. It is already marginalized.

VB already is phased out. And instead of spreading FUD, can you show one piece of evidence to your claim?

>2. Because of 1, there are few opportunities

There are lot´s of opportunities, you only have to find them. Many clients don´t care in which language a solution is written. Your claim is irrelevant.

>3. Because of 2, there are few developers

I won´t call 100.000+ developers a few. There are a lot of companies with modern and innovating development tools who would be very jealous.

>4. Because of 2, companies, looking at staffing reasons only, need to adopt
> new technology. There are also technical reasons, but we don't need to
> get there.

Get real. New technology. What if new technology is missing proven old technology? .NET can´t beat a number of very usefull VFP features, but of course technical details never stands in the way of spreading your FUD.

>5. Because of 4, there are few opprotunities

We all know that technical reasons are not the reasons for IT managers to dismiss VFP. It is FUD spread by low life organisms like you spreading FUD abouts VFPs future, and of course MSs lack of advertisement, to protect its investment in SQL server and .NET.

>and on, and on, and on... It is now a problem that is feeding on itself. In programming terms, VFP is in an infinite do..while loop. It will stay in this loop until the condition in 1 changes to .F. ...

Funny, you could draw the same conclusion about your behaviour here.

DO WHILE .T.
     TalkBadAboutVFPWithoutHavingAClueAboutTechnicalDetails()
     PromoteNewCrappyTechnologyInOrderToMovePeople()
     DistractPeopleWithTalkingAboutYourLawyerAdventure()
     IF PositiveReaction()
        InCreaseEgoWithoutCaringAboutOtherPeople()
        CashFromUnknowEntityWhoPaysYouToBehaveThisWay()
     ENDIF
     nInsultLevel = InSultPeopleWithoutKnowingWhatIMTalkingAbout()
     IF InsultLevel > ACCEPTEDINSULTLEVELBYUTMANAGEMENT
        WaitTime=GetBanned()
        SLEEP(WaitTime)
        ReturnToUT
     ENDIF
     LeaveAndSayYouWillNeverReturn()
     SLEEPRandomTime()
     StillSilentlyProgramAVFPApplication()
ENDDO

So you see John, you´re irrelevant, written by some 16 year old schoolkid having attitude problems while reaching maturity.

>VB has evolved. VB is part of .NET. VB is alive and well....

Irrelevant. VB 6 is dead.

>>4. People should abondon the sinking ship and inmediately start in .NET

>People should keep their options open. Whether that is .NET, Java, Python, or whatever, it really does not matter. Even .NET developers - who are flush with work should not be lazy. They shoud keep working - to keep their options open and their skills fresh. That is why people like Markus, Rod, Rick, et al. - will stay relevant. That is also why some other - not named "VFP Gurus" and the like - will continue to be irrelevant.

When do you learn that people are not waiting for your advice. They are a lot smarter than you think (or are). People should not listen to the crappy stories you and your friends are trying to push down our throaTS. They should evaluate themselves, what is best for their future. They don´t need a big mouth like you to make that decision.

>>1. There are still one or a few hundred thousand VFP developers using the tool every day.

>Probably a lot more cobol developers - but I don't think you see people fl*cking to it....

Get me the numbers. And what does this tell. Can´t COBOL programmers support themselves ?

>>2. There is also a major decline in VB developers (because of transition to .NET). So why is VB not dead and VFP is ?

>Still a lot of VB 6 opportuntities. Indeed, VB 6 may be "dead" - but the number of opportunities counter-acts that issue. I don't know if one just starting out - should pick up VB 6 from scratch. But...given the choice between VFP and VB 6 - one could parlay the VB 6 skills a lot more readily than the VFP skills.

Make up your mind. First you say it is not dead, now you say it is. Make up your mind.

>No doubt... So based on this, I guess your theory is that upgrade numbers may be more dismal than 8, more dismal than 7. You know what happens when the upgrade numbers continue to decline....

As will be the case for any development language at some point. The questions is when and at what point. A question nor you nor I can answer. Meanwhile don´t listen to FUD. If MS announces VFP is beeing discontinued, there is plenty of time to evaluate your situation.



>4. you´re spreading FUD, just like you did before .NET in pushing people into VB.

>When you can name one VFP developer that was adversely affected by that advice, get back to me....

So you indeed admit you did (In a previous thread you did deny). And if no-one was affected, then you must have done a pretty poor job. That would mean I and other members up here did a good job in convincing you´re talking crap. That is the best compliment you´ve given me ever.
Thanks.

>To show the fallacy of tw*ts like you...

Yep, here we are again. Ohhh please, please continue with name calling. I´m really hurt now.

>You should be ashamed of yourself. You do a great disserve to the VFP community.

>Actually, I am probably providing more value than people like you realize...

Huh now I´m confuse. First you said that noone was taking your advise, and now you say provide value to people. ......... oh wait ....... I understand. You provide value to people to show people they should not listen to bul*ies like you and evaluate themselves

>You´re only here to seek and destroy.
>Tw*ts like you...yes...

Good luck....

>I really wonder how much you get paid to do this up here.
>I consider it a moral obligation.

ROFLMAO.. JVP, lawyers and moral. Couldn´t the combination be more extreme than that...

>Have one...and unlike you, I don't wax poetic as it it where still 1988.

No you live in total differen dimension of your own s*ck imagination driven by your ego.

Oh, and please close the door on your way out.

Walter,