>>>>>>VFP does data best ...
>>
>>>>>How's that? How does a product "do" data?
>
>>What exactly do you intend to accomplish by picking apart informal discussions like this?
>
>Hi, Mike. I'm sure that JVP can answer your question himself, although I think the answer could be as simple as "because I would like to hear the response." I would like to say that I think *his* question is quite legitimate. If VFP "does data better than anything," as many of us probably has quipped over the years, should we not be able to quickly and easily enumerate the ways in which this is true?

It was the the question 'how does a product "do" data?' that I was asking about. That doesn't strike you as unnecessary nitpicking?

As far as can VFP do data the best, if that was the only question asked I wouldn't have said anything. Its a subjective answer, unless objective criteria can be provided; Craig seems to think it is. Personally, I agree. That there is concern over this opinion being expressed in a VFP forum is comical, don't you think?

Anyways, to answer your question, why do I think VFP does data best?

Because its very simple to create a large database application and very simple to create a small database application. The syntax doesn't require a prohibitive object model, and deployment issues are a snap since you're just copying files and metadata. No server software or hardware. For my data uses, I think VFP's the best.