>1. DON'T embed SQL into your program anywhere. (Of course, this is what we do with Views or SPT.

Where would they go? Don't they have to go into code at some point?

>
>2. Don't use Joins... they are slow and kludgey... use multiple Select statements using a value from one as a parameter for the next, is basically what he is saying... This is almost everything old is new again, in 2.6 we would open two tables and relate them... well, he is basically advacting the same thing, the only difference is the two tables are resultsets (cursors.)

Interesting - this is exactly the approach I took when I needed to get information from a SQL Anywhere database. The information was spreadout over 7 different tables (and I only needed a few fields from each table). The SQL command was horrendous and confusing so I just broke it up into 7 different SQL statements.

>********
>Actually, this summer I am going to be building an entierly new VFP framework which will be different than anything else we have in VFP now. It is going to be based heavily on Amblers ideas and whitepapers on OOP and Persistence.
>

Are you going to try to incorporate a "stateless" design? Or something closer to your suggestions for WebConnect a while back? Or something completely different?