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 :).

John,
Have you read about M$ 3-2-1 project methodology? In a nutshell, it's a recommended approach for getting up to N-tier speed. 3 Tier, 2 Developers, 1 month. You take a small business process that both developers understand, use tools your familiar with. Then take 1 week to study the N-tier approach, 1 week for analysis/design/planning, 2 weeks for coding & testing. If I had the available resources, I would love to try this approach myself.

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.

I agree!

IMHO, n-tier design is one area where VBers are well-ahead of the race than we (VFPers) are as an enterprise-level developers.

I don't completely buy that. VBers are accustomed to not having local database engine, so yeah maybe they can think in terms of separation of tiers a little easier at first. But I think VFPers are a few steps ahead because we have practical experience we can apply to analysis & design of all 3 tiers - it's just that we need to learn to adjust the methodology we use in our development practices.

P.S. - when are you planning on taking 71-100? Interested in doing an ICQ/chat study session outside of work one of these days before Feb 1st?