Thanks for that - it's a shame we don't have the case studies

Microsoft must be laughing - they have a ready made trojan horse called UT which is helping MS to destroy VFP by all the negative talk

Colin

>Hi Colin,
>
>I wish I could give the name of the Bank. In fact, there is a Sr. VP (who was once a VFP contractor here) who would love to make it a case study.
>
>The fact is that it is against company policy. That is the reason why no one hears of the large VFP projects. There are many of them - particularly with larger financial firms. Also, you never hear about the programmers working on these projects. These teams solve their own problems and have no use for user groups like the UT, DevCons, etc.
>
>Futhermore, it's interesting to note that many of the new (you heard me right, "NEW") VFP programmers are here on H1Bs. And I have to say that, for the most part, they are superior in every way to their American counterparts. This is also true with the .NET guys.
>
>>Jeff
>>
>>Can you say who the bank is? Guess it would be an interesting case history to try and fight off the general ignorance around - I have 1 client who wants to move the app away from VFP simply because it's VFP he talk about open source, Access - sad thing about it he doesn't even have a good handle on what the app does
>>
>>What a wonderful hatchet job MS have done!!!
>>
>>
>>>Really!!!
>>>
>>>Well, I'm here to tell you all that the UT is NOT the center of the VFP Universe and that most of you have zero idea of the big companies that maintain and enhance very large VFP apps.
>>>
>>>I work at one of the largest banks in the world with over thirty VFP developers (some are now managers, VPs) on, arguably, one of the largest VFP SAR apps in existence:
>>>
>>>(1) 1400+ screens
>>>(2) Over 700 branch offices
>>>(3) Dozens of .NET web services supporting the core VFP product.
>>>(4) QA teams in India
>>>(5) etc., etc., etc.
>>>
>>>All told, there are over 1,000 employees and contractors that support the project in one way or another. The Bank has NO plans (let me repeat, NO plans) to migrate the core VFP product to .NET. or any other platform - they have been unsuccessful numerous times over the years. There is one person on this thread who knows about this project.
>>>
>>>The funny thing is that of all the VFP developers we have, only two or three have ever HEARD of the UT. In fact, of the many dozens of VFP programmers I have worked with over the years, I estimate that roughly 10% have heard of the UT and maybe 2% are actually members. Can you blame them? Who wants to read these stupid "VFP Dead Threads". I have been in and out (out mostly) of the UT for many years and nothing has changed.
>>>
>>>>The ones that don't use FoxPro in house anymore. :)
>>>>
>>>>>What is your defintion of "Big Customers"
>>>>>
>>>>>>Big customers care. They want to make sure they have expertise in house to support the app.
>>>>>>
>>>>>>>BINGO! Besides no customer needs to know what the platform is.