>>Actually I just repeated your words here.
>
>
>Which was in response to your words:
>
>"IMO, the honest answer should be based on developer's own qualifications, i.e. if someone is good VFP person then VFP-SQL will be better and otherwise good VB person will proceed to VB-SQL. The final result would be essentially the same."
>
>Ed, you are basically saying here that regardless of the circumstances - if you know VFP - use VFP. IMHO - thats bad advise - especially since it in no way answers the original question - which is the better tool for C/S.
>
>How do you know the results are - or would be essentially the same. What if full ActiveX support was required? What if the footprint on the client needed to be smaller? What if performance with the VFP solution was too sluggish as compared to VB or someother tool?
>
>Bottom line is you or I don't know - until you have either experience with the other tools or have run a comparison.
>
>>It depends on size of box :). You know everybody is flexible enough until s/he is back to the wall.
>
>Thats fine, and I addressed that issue in which I said if you are in a crunch - and all you have is VFP - then the choice is made. But, that was not the question. The question was what the better tool is. The question was not what should be used. This is the problem with this community and many others is that most solutions are always from a specific product standpoint - instead of from a tools collaboration standpoint.
>
>IMO, to just say the results would be essentially the same - in the absence of really knowing the situation - or how things would be - is giving bad advice in IMHO.

Strictly IMHO!
John, I'm happy to tell you that besides VFP I also do VB, SQL-server, HTML, Java etc. That's just for your personal knowledge.
Another point is more important. I hate to get advices how I should behave personally, and specifically how I should reply on UT (surely I strictly adhere to Michel's standards). I don't understand why you are trying to shift the thread to discussing of my or someone else personal weaknesses (even if I have some). Basically, you gave the answer and I gave the answer, you can dislike my answer but it shouldn't go personal.