Sorry Jim, what you say is what I meant to say. The author suggests to the reader that VFP was incapable but I do not see any hard reasons for this suggestion. Web enable? Web services? 1 Gig database? SQL data store? So what :)


>Thanks Jos.
>
>I, too, am bewildered as to WHY MS sees fit to promote one of its own products at the expense of another of its own products. It's one thing to have someone else doing that dirty work for you but a whole other thing to do it yourself (and this is a MS article desite whoever wrote it).
>
>Below you say "There is nothing in the article that suggests VFP was incapable of performing the job at hand.". One of my central points is that there is plenty suggesting that VFP is incapable to the reader who is not familiar with VFP! My point of view is that if the article simply stated something like 'Visual FoxPro could have been used to modernize the application but the company WANTED a good reason to adopt the .NET framework and so took the initiative to do so with this product.' and left out ANY other mention of VFP then I would have no complaints.
>I still would wonder about many of the statements in the article (a case study on a project that is "mid-way through" is dubious to me AND amazement at how fast things can be done with .NET followed by a schedule taking 72 man-months is basically laughable) but that's the writer's and the .NET marketing groups' problem.
>
>cheers
>
> >Hi Jim. I just wanted to says thanks for taking the time to do this analysis and write this and your other post on this topic. I agree with your comments and MS should remove or re-write the article.
>>
>>What irritates me the most is why the article (MS?) appears to posit .Net against VFP at all. Why? Its stupid and I would say embrassing to MS. They are not competing technologies and have different strengths and weakness' and application.
>>
>>The article is simply inaccurate and misleading. There is nothing in the article that suggests VFP was incapable of performing the job at hand. The article clearly demonstrates that the developers will be just as ignorant in .Net as they obviously were in VFP. One Gigabyte database? Surely they jest. Its a joke.
>>
>>I think its a desperate attempt to "show-off" .Net. MS should be careful as I suspect that if they irritate enough VFP developers like this they may well end up driving us all over to Delphi. (No smiley at the end of this). If we have to learn something new we can also learn something new somewhere else.