>MFC will handle this fine, the only problem I could see is from a user(s) point of view is MDI the best choice?
>
>From what I can understand you have data that is related, for example the dialog data and its notes; however in a MDI application this relationship is not that easy to portray without a modal state and can easily become confusing to the user.
>
>I would consider the validity of the MDI approach over a SDI version that swaps the views in or out either by a selection view/menu option or tabs. Microsoft Outlook is a good example of this technique and can be easily implemented through the MFC doc/view architecture.
>
>HTH
>Neil

Yes I do, but the notes are not stored in the tables. There are references to the documents in the data, but the documents are separate text files.

Here's the scenario, the user launches the application and the data dialog is presented. The user navigates or searches to find the catalog entry they are looking for. Linked buttons on the toolbar and matching menu items load document views of the associated documents.

I've chosen to do it this way so that the people who wrote the documents don't have to do so in the application. All they need is a reference.

Regards,

Jason