re: doing it all on the server. Any web app is done "on the server," although we are capable of running the same app that is used against local views against the web service also, which puts the UI processing back onto the client. It all depends on your needs.

As for the "backend" -- the data engine itself can run against VFP tables using local views, or against a client-server backend. The former is faster (nothing runs like a Fox <s>); the latter has transactional security and scalability.

Hank

>> Your colleague's: do it all in one SELECT.
>
>Aha
>
>
>
>> < self-promotion >
>
>VERY nice, Hank! And I really like it that you get everything right the first time ;)
>
>You know, I'm going to have to take a closer look at that ProMatrix someday.
>
>
>
>> 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.
>
>Oops, I got lost again. How is that not doing all the processing on the server?
>
>
>
>> 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.
>
>OK, got it now. BTW, is this idea of nested views truly Data Shaping, or is it just our own self-customized version? I kind of suspect the latter, to tell you the truth.