Okay, I've got a problem here that I just don't understand. Maybe this is just the assumed behaviour, because I can't find thing one about it in any of Apple's documentation or on the web, but I'm baffled as to why this would happen, or why anyone would choose this as the default behaviour. I have two data objects in my app's controller class, folderList and dataStore. They're initialized and deserialized from disk in the class' init function. I'm also implementing awakeFromNib in this class. Now, as soon as control exits awakeFromNib, both folderList and dataStore become invalid. They're not nil, but it's like they haven't been initialized at all. DURING execution of awakeFromNib, they're valid and populated. But as soon as control passes out of awakeFromNib, they're empty and uninitialized. Can anyone shed some light on this? It seems to me that using awakeFromNib shouldn't be blasting the other data in my class, but like I said, maybe I'm not understanding how all the different initializations that go on in an app work.