>I am not contesting or disputing, (I have never written a large C/S app, so I am in no position to contest or dispute :-)) but would you explain what C/S has to do with how much "munging" an application needs to do?
>

Most VFP folk make a big deal out of VFP's ability to munge data locally. The fact is, in most C/S apps, there is no need for that type of data processing. If there is a need, that work is ceded to stored procs, or some other set of server-side components. The components are usually written using the tool they know best. If they know VB, they will use VB, and do an effective job. If they know VC or VFP, that is what they use.

It is a classic case of a VFP strength being perceived by other development communities as not being significant since they can do the same thing. Most folks in our community fall into the trap of 'Our tool does the best job for that type of work. Why don't they use it?' Fact is, nobody outside the VFP world cares, and they will never be convinced to incorporate VFP into their efforts. Oh sure, there are some sporadic victories reported, but in the final analysis, it is still nothing significant.

Not trying to open up the VFP vs VB can of worms again. Rather, I am trying to shed some light on how these different issues fit together..