Walter

>The problem with this example is that it does not do much of datamunging. The only real data munging going on here is to fill the age column, which hardly gets significant in the overall picture. After all in your .NET example the data retrieval which takes up the most time is not written in C#, but in VFP.

That is true, I would equally be interested in how C# stacks up in that area.

>My challenge posted in Thread #918302 Message #919635, is much more representative to the data munging argument. You get data from the server in various tables in more or less normalized form and the task it to create an overview for displaying or reporting.
>
>The challenge does not provide full VFP code, but rather global directions how you would do it in VFP. If you look at the code carefully, you'll see that there quite a number of VFPs data centric features used, like SET ORDER, INDEX ON, SET NEAR, SET CARRY, INSERT INTO, etc. If these kind of data munging operations can be done in simular performance, with simular programming effort (thus bug risks and maintenance), you'll have gained a believer.
>
>Now, I do not expect you to write a full example, but hopefully you'll see what I mean here with data munging and why VFP is particular strong here. Maybe you can launch some ideas (no, no preprocessing on the databaseserver), constructive comments to get a better picture.

The only problem I can foresee here is getting a good example to fit in with my current example, another again is that the app was designed as a fox app, and if designed as a C# app the structure of the DB would likely be massively different.

That's where I'm struggling at the moment, what I will try to do is see what else is in my DB structure that could present an opportunity to get some real data-crunching going on...I'll have a look.

Kev