>Hiya John ---
>
>>
>>I don't think it's a really bad idea but wouldn't this be too restrictive? I think one of the advantages of n-tier is the separation of each layer to function w/o too much regards to changes in the other layers. If you don't separate the middle-tier in to separate EXEs or DLLs, you would "corner yourself" in to VFP-only solution. Just my simply opinion.
>
>This is true....you would be creating a bit of a stovepipe but I was thinking in line of the latency issue and minimizing messaging and instancing time between different tiers, which seems to be an issue according to that case study at MSDN.

I guess it would depend upon how much of "overhead" we are talking about. Like many here, I'm also just starting to "actually" experiment with this n-tier stuff (so far all I've done is read and think about it). One thing's for sure: my first few experimental n-tier designs will not be very "pretty", that's if I get it to work at all :).

We need to hear more from those brave individuals who have ventured in to these uncharted territories. I hear bits 'n pieces of information here at the UT from those who have actually done it but not nearly enough to make great use of it.

IMHO, n-tier design is one area where VBers are well-ahead of the race than we (VFPers) are as an enterprise-level developers. To me, n-tier is not new anymore. It is now. We need more VFP n-tier "mentors" to step up and lead us.

Sorry John for rambling on.