From investigation it appears as long as I create any 2nd views that are derived from CView (or one of it's derivated classes) using the mfc IMPLEMENT_DYNCREATE then I don't have to worry about any updates etc to the CCreateContext. (? correct).
Of course I realize upon switching and activating a view there are code ramifications but I seem to have all those covered and working without any calls involving the context struct.
And further ever if I did generically create another view with "new" then for any pertinant framework function calls that require the Context as an Argument, I would only have to create a temp CCreateContext struct and fill it NULLs except for the members I'm interested in updating. (? correct).
I.e. when looking at the declarations of the CCreateContext structs in the various MFC classes they are protected and one doesn't just read them to check, one can only use access functions to overwrite with any updates (? correct).
Thanks for any input, apologize if this has been covered since I could not find this specifically answered in this context. (<-no pun intended)
JW