Sharing common dialogs across applications
-
We have several exes that need access to common dialogs for database administration on common tables. Dialogs need access to a database via ADO/ODBC and user interface. We have in the past recreated the same dialog repeatively. Getting tired of doing that. Would like to create for each dialog an EXE/DLL or something that we can link at runtime in case of changes. A DLL looks like the best way. Any BOOKS or PUBLICATIONS out there to exactly guide us from creating , calling from current EXEs, and distribution? Really need step by step not just a reference document. Would just creating an EXE for each dialog and shell execute would work? Pros / cons. thank you
-
We have several exes that need access to common dialogs for database administration on common tables. Dialogs need access to a database via ADO/ODBC and user interface. We have in the past recreated the same dialog repeatively. Getting tired of doing that. Would like to create for each dialog an EXE/DLL or something that we can link at runtime in case of changes. A DLL looks like the best way. Any BOOKS or PUBLICATIONS out there to exactly guide us from creating , calling from current EXEs, and distribution? Really need step by step not just a reference document. Would just creating an EXE for each dialog and shell execute would work? Pros / cons. thank you
-
We have several exes that need access to common dialogs for database administration on common tables. Dialogs need access to a database via ADO/ODBC and user interface. We have in the past recreated the same dialog repeatively. Getting tired of doing that. Would like to create for each dialog an EXE/DLL or something that we can link at runtime in case of changes. A DLL looks like the best way. Any BOOKS or PUBLICATIONS out there to exactly guide us from creating , calling from current EXEs, and distribution? Really need step by step not just a reference document. Would just creating an EXE for each dialog and shell execute would work? Pros / cons. thank you
(If you're using MFC) We had a similar problem, and eventually, after lots and lots of deliberation, we opted for a non-portable solution, where the DLL with the dialogs export the entire
CDialogclasses, using the__dllexportkeyword in the class declaration. Code won't be reusable by any other platform or compiler, but it works... You could pass in aCDatabaseor what have you to the dialog constructor.