I'm now beginning a project with 20 different databases that all integrate into one application. My WinForm startup page has IsMdiContainer set to true and the first child window is written as a separate csharp code page that contains the class necessary to display the child window and all the code necessary for interaction with only the database appropriate for the menu selection that calls that page. Is this a good design? With the concept of disconnected databases being prevalent in .NET I am questioning the best approach to large scale design. I contemplated loading up several databases in the parent window and then chose to load just the appropriate database for each child window as I opened that child window. Can anyone offer some insight into what has worked well for them?
Kyle
Kyle
