>>>>>>Make sure that all of the masters are inherited from mmMasterPage and not from the standard master page. You would need to add some Mm using statements but they need to all be subclassed from mmMasterPage the same.
>>>>>
>>>>>The IASLeftNav was just a MasterPage, not mmMasterPage, but that still hasn't worked and I've tested it by setting a breakpoint in all three page_loads. The debugger then jumps straight from the content page's page_load to the OuterMaster, skipping over tha IASLeftNav completely.
>>>>
>>>>All three page loads run on mine and in the expected order. Default, then nested master, then the outer master.
>>>>
>>>>I think you may have AutoEventWireup set to false. Check in the aspx source of your nested master page at the top where the page directive is and the master page is indicated. See if you have a directive - AutoEventWireup=false. Change that to true.
>>>>Tim
>>>
>>>It was set to false, but changing it to true hasn't made any difference. :(
>>
>>At this point the answer is - Yes they will all fire if you have AutoEventWireup set to true. In your case there is something out of place which is breaking this. Again, you could send me those pages and I will look at the masters to see what looks wrong.
>>Tim
>
>Tim,
>
>everything was looking good, based on how you said things should be set up, but it wasn't working, so I decided to restart my machine. Guess what, with a restart it all works properly now!
>
>I guess VS or the ASP server was doing some caching and not running the new code.
>
>Thanks for your time!

Your welcome. And you had AutoEventWireup set to false, or I did it for you :-) Glad it is working.
Tim