>Thanks for your reply.
>
>> there are two points of view in the SQL world. One of the upcoming ones is that you should use Data Shaping: which amounts to using successive views
>
>This is good to hear, especially since I thought of and started using this technique just recently. Ideas seem to pop up at the same time all over the place, don't they? <g>
>
>What is the other point of view, may I ask?

Your colleague's: do it all in one SELECT.
>
>
>
>> xCase
>
>This looks very interesting. I went to their website and viewed the demo. I like what I see, but it seems to be for SQL Server and not for FoxPro. Or did I miss something?

Very definitely for FoxPro:

<self-promotion>

Take a look at www.prosysplus.com/csdemo.htm to see one way of doing it.

</self-promotion>

>
>
>
>> there is the debate about where the work should be done: on the Server (run Stored Procedures) or on the client
>
>Oops, I must've definitely missed something here. I thought the only way to build a web app is to do processing on the server (aside from minor browser scripting stuff, that is). It seems to me that whether code is executing in a SP or in a .NET code block, it'll still consume the same amount of resources on the server, no?

In a web app we are current creating, we are using Web Connection, which instantiates a modified Visual ProMatrix data engine, which can run against VFP tables, or client-server.

>
>
>
>> Related to that: read a real-life case study
>
>Ouch, that had to hurt. Is the study publicly available?
It was in one of those trade mags; I forgot which one, and I've tossed it already.
>
>
>
>> So, your colleague is correct; but probably wrong. <s>
>
>I hate to admit it, but you lost me on that one. Say again, please?

He is correct: VFP can't do it his way. He is wrong because Data Shaping is considered a better way to go now, and VFP works very well with that.