Hey, Thanks for taking the time to respond, and sorry for not responding fast enough.
The Model doesn't really know about the view in this case. It just keeps certain boolean varialbes that switch on and off, and dispatches events when they are changed to anybody who has wants to listen. For example, when I want certain elements to disable, I'll change a variable in the model.
In reality, this is my answer to not using pipes, because for some reason, even after I 'removedCore' something remained in memory. Causing the application to give me an error when I sent a message through pipe and then tried to grab an instance of it again next time I loaded my module. ( Don't know if this is a bug ).
Anyway, I think Joshua Ostrom ran into the same thing and narrowed it down to having to close the 'Tsplit' connection. But I don't think I can refactor the code at this stage. The code is in his Mortgage App pipe demo http://www.joshuaostrom.com/2008/06/17/pipe-demo-mortgage-app/
So that's where I'm at, and was hoping I could get some advice from the pros. If you think this is a oop no no, I'll refactor next time to implements Joshua's techniques or use Fabrications? Thanks again for responding to this.