I'll try explain it again as I'm not sure if your suggestion is applicable. There is a program called MainMenu which is basically the launching point for all the other sub systems like Accounting, Address Book, etc. There is now a need to be able to launch a dialog in Address Book that is in Accounting. Eg. for a person in the address book we might like to add a bank account to them so we want to the launch the "Add Account" dialog contained in the Accounting program. I can see two ways of doing this. 1. Putting common dialogs/code from each sub program into its own DLL so it can be used in other programs 2. Sending a message to main menu which then opens Accounting if its not open already, and then opens the required dialog then messages the result back. Option one I'm not entirely sure if it a good solution and option two would work but it would require a custom messaging system to be able to make it scalable I think. Are there other options out there that help with this sort of Inter-Program-Communication/Modularizing problem?

Yep, that translation is correct. The code that is moved from MainFrame into a class in the DLL is responsible for setting itself up. The dependencies are mostly just basic variables, enums, etc so I think it will work by moving them into a DLL. What's an IPC?

I was told I should probably ask this here, even though it relates to MFC, it is probably more a design question. So, At my workplace we have a number of programs (sub systems) which make up our software. Some of these programs need functionality from other programs and I'm trying to find a good way to perhaps modularize each program so that common code/resources can be used "globally". The current example forcing me to find a solution is the need to launch a dialog from our Accounting package from another sub system. The big problem is that this is quite a large dialog and depends a lot on things from the Accountings MainFrame. I was thinking that for each sub system I could create a DLL which contained common dialogs, etc that could be used by other programs. The problem I face is that a lot of the dialogs have dependencies on their parent programs MainFrame and I'm not sure how to get around it. I guess one solution might be to take everything out of the MainFrame and put it into its own class which can then be passed to the DLL.. but I don't even know if that would work as I still need to Initialise this new class the same way it would be done in the parents program, but now in the other sub system.. though in saying that the DLL should probably be responsible for setting itself up. Your thoughts? Cheers

Hi, At my workplace we have a number of programs (sub systems) which make up our software. Some of these programs need functionality from other programs and I'm trying to find a good way to perhaps modularize each program so that common code/resources can be used "globally". The current example forcing me to find a solution is the need to launch a dialog from our Accounting package from another sub system. The big problem is that this is quite a large dialog and depends a lot on things from the Accountings MainFrame. I was thinking that for each sub system I could create a DLL which contained common dialogs, etc that could be used by other programs. The problem I face is that a lot of the dialogs have dependencies on their parent programs MainFrame and I'm not sure how to get around it. I guess one solution might be to take everything out of the MainFrame and put it into its own class which can then be passed to the DLL.. but I don't even know if that would work as I still need to Initialise this new class the same way it would be done in the parents program, but now in the other sub system.. though in saying that the DLL should probably be responsible for setting itself up. Your thoughts? Cheers