So Craig in your opinion a developer should use VFP for building client-server applications.
>Jenny's correct in saying that .Net is designed for web-based apps. It does NOT mean that you should not be using VFP for them.
>
>
>>Start Quote Jenny Brown "What's VFP's role in this changing development world?
>>While .NET is geared primarily for distributed, Web-based applications, VFP will continue to be geared toward robust client-server applications." End Quote.
>>
>>>Would you mind quoting the part of the article that leads you to this conclusion?
>>>
>>>Thanks...
>>>
>>>
>>>>>>>
>>>>>if you want to build web based applications or n-tier applications you shouldn't use VFP
>>>>><<
>>>>>
>>>>>Who said this? I would like to see this statement defended on the technical merits. VFP is a great tool for building traditional desktop apps with local data/remote data, multi-tier C/S apps, and web-based apps. It can fit into a .Net environment via web services. It can fit into an existing environment via COM.
>>>>>
>>>>>There are scores of people who have built web-based applications, and as somebody who does A LOT of n-tier C/S work with the product, the statement above is void of any technical merit.
>>>>
>>>>Hi John.
>>>>The above statement is my interpretation to what Jenny Brown says in VFP in a .NET World article in October FoxPro Advisor .
>>>>Also I don't agree with this statement but is what I think that a non VFP developer will interpretate from Jenny Brown statement.