I wonder if our implementation of MVC is faulty? Was it described to us incorrectly and therefore we used it wrong? Why'd we use it? I saw in one of the earlier sentences that "many user interface frameworks implement the [view and controller] roles as one object." I think that would have been a lot more natural in our environment since we were writing a Windows Forms application. But then too, because we already have the View and Controller already separated, maybe it will make the application easier to port to a web app.