Perry,

>>yet folks, including yourself, contend that these data intensive apps can only be accomplished with VFP.

That is simply untrue. My anecdote is that VFP's automatic disk/memory spanning makes it trivial to perform functions that require significant extra effort in dotNET which is an unnecessary technical distraction from the business issues that occupy me. I see no useful business reason to waste time on memory resource management when VFP takes care of it automatically. This is an issue that MS says it wants to resolve in dotNET as a priority, so I assume there is a bit of a groundswell here. Difficult to say in the absence of proper data, isn't it.

re proof: the nature of data is that 2000 positive cases are not necessarily a proof but one negative case is a disproof. Of course to be sure one has to assess the cases in a structured fashion rather than relying on voluntary reporting that may simply reflect motivation of one particular group. That is the nature of data.

There is nothing wrong with anecdote as long as we see it for what it is. This discussion was initiated because somebody observed that it takes 4X as long to do a C/S app in dotNET. I asked for details of the app so that people can quantify this anecdote in terms of their own occupation. That's it. I'm not disagreeing with him or trashing dotNET.

Regards

j.R