>>But this is a VFP only thread!
>
>Okay. Then I guess discussions regarding Automation, Using OCX's, etc is forbidden as well? Those topics are not VFP either. Rather, VFP hosts those abilities. Cmon.. That is pretty weak.
>
>
>>Sorry for interrupting, I'm not going to argue against your points. They might be right but in real situation, the discussion ususally going another way like:
>>- VFP is dead.
>>- Why?
>>- I saw one guy who said this, and it was even on VFP forum.
>
>If you read my entire response, you would have seen that I clearly do not think VFP is dead. That is also a tired and weak argument. It seems today that when discussing other tools - it is immediately a death rattle for VFP. That is either crazy or paranoid. I am not sure which is the case.
>
>
>>I hope you see the point. VB is better in market sense
>
>From a Client/Server sense, VB is better tecnically. In a stand-alone situation - or a moderately sized app - VFP is better. In both cases - either C/S or stand alone - VFP plays a role. The role just changes. I don't know why this is to difficult to digest.
>
>>I bet that good VFP programmer will make C/S system the same quality as VB-person, and assuming that generally VFP-people have better qualification (i don't want to extend on this topic here) it's very probable that VFP front-end will be better. BTW, last year I converted VB-SQL system to VFP-SQL and got really 10-times better speed, but mostly because of 'high' qualification of VB programmer worked before me there. BTW, I know VB.
>
>I agree that on average - a VFP developer writes better quality code than a VB developer. In regards to your VB conversion - what version of VB was it? If you say 3.0 or 4.0 - I am not surprised. Those version where dog slow. The same cannot be said for VB 5.0 however. If the version was 5.0 - my guess is that the weak performance was due to poor quality code. I don't hold that against VB.
>
>Look, I am not trying to start a war here. Rather, I am attempting to bring a different perspective. I am a VFP developer primarily - and will be for some time to come. If you or anybody else is writing stand alone applications and are using VFP - thats great. However, in the context of C/S and VB's ability to work with ADO in regards to ActiveX data binding - and the fact that VB is 4 x lighter than VFP - and the fact that you have a compiled EXE - VB is a better C/S front end than VFP. That statement should not be confused with something like VB makes better database apps than VFP. That statement is too broad and in this case - would be incorrect. My points are only limited to the C/S arena.

I appreciate that you thoroughly preparated my reply, but doing this you omitted (intentionally or not) one sentence: i don't mean particularly you,
nothing personal. Also, you made few more changes and then make conclusion that I am crazy or paranoid. This is nice way to make discussions.
Well, I want to repeat my point of view. There are many VB programmers who think that VB is the only and ultimate tool. There are few VFP programmers who promote their product in this not very friendly environment. And then these fews get offer to play honestly, i.e. admit that VB is very good tool, doesn't matter how other players play. You see, the actual discussion is not on technical side (we are all professionals and know things).
I will appreciate your reply on this message, but don't evaluate my personal or professional skills, please.