Dustin,

>1. I'd like to show these in a few, small, read-only grids on page 2. It would be nice if a user could click on one of these records, and bring up its own edit page.

Sounds like you need to look at CListObjEdit

>Question 1: In which object's PostInitHook do I put code that allows me to get the iCustomerID that I need to satisfy my parameter-driven views on page 2?

I'm not sure without mocking up an example of your scenario...

>Question 2: Where is the interesting code in cBizObjMaintenanceForm? I'm having a tough time finding it, I'm guessing it's in one of the superclasses somewhere. Methods I'm interested in, is what happens when you double click on a grid-row, or what happens when you click on Tab2. I'm even interested in seeing SOME code attached to the New, Delete, and Close buttons (no code that i can see!)

From the Standard Menu pad you get after running StartMM(), you'll see the SuperClass Utility listed. Get used to the Superclass Toolbar & every time you go looking for code and find an empty method, use the 1st button to surf up the inheritance tree... there's lots of in there, sometimes on several layers.

>2. In the example above, I placed the CustomerObj on page 1. Should I place CustomerHardwareObj, CustomerVisitsObj, CustomerProductsObj on Page 2? Which should be the primary object? I guess it doesn't matter too much, since these will be read only. But why am I so limited to only editing one object per screen?

Your not really, you can more than one BizObj on a screen but that usually makes for a sloppy screen unless your purposedly trying to avoid pageframes here. But you can have only one primary/auto-primary BizObj at a time, so usually you want either the main parent table bizobj or page1 bizobj set to primary, then your child table objects set to auto-primary.

>3. I notice that when I drag CustomerObj onto another form, that the same dataEnvironment is attached in the builder. Should i keep it that way? I noticed I could easily attach a different dataEnvironment and different Views within, but is that normal practice?

This is a great flexibility in MMF, but not for the weak at heart. You need a really solid design to effectively swap dataenvironments in your bizobj's. Read the developers guide, it explains most of what your reaching for here.