Microsoft KB Archive/173261: Difference between revisions
m (Text replacement - ">" to ">") |
m (Text replacement - "&" to "&") |
||
Line 142: | Line 142: | ||
<div class="indent"> | <div class="indent"> | ||
[[../172336|172336]] PRB: Assertion Launching Program with Tip of Day & | [[../172336|172336]] PRB: Assertion Launching Program with Tip of Day & Splash Screen | ||
Latest revision as of 11:29, 21 July 2020
Article ID: 173261
Article Last Modified on 11/21/2006
APPLIES TO
- Microsoft Foundation Class Library 4.2, when used with:
- Microsoft Visual C++ 2.0 Professional Edition
- Microsoft Visual C++ 2.1
- Microsoft Visual C++ 2.2
- Microsoft Visual C++ 4.0 Standard Edition
- Microsoft Visual C++ 4.1 Subscription
- Microsoft Visual C++ 4.2 Enterprise Edition
- Microsoft Visual C++ 4.2 Professional Edition
- Microsoft Visual C++ 5.0 Enterprise Edition
- Microsoft Visual C++ 5.0 Professional Edition
This article was previously published under Q173261
SYMPTOMS
When you try to start an application that contains a modal dialog function, such as CDialog::DoModal, AfxMessageBox, or MessageBox, that is called from the CWinApp derived class' InitInstance function by double-clicking on the application from the Windows 95 Explorer, selecting the saved document from the Start Menu or double-clicking on it from File Manager, one of the following may happen:
- It may work fine if built with Visual C 2.x running under Windows NT 3.5x and later. -or-
- The dialog or message box may come up, but the application's main window may not come up, and the process is now hung, and can only be terminated by PVIEW. -or-
- The following error message box may be displayed: And, symptom number 2 may also occur.
CAUSE
When you launch an application in File Manager or Windows Explorer, a WM_DDE_INITIATE is supposed to be handled by the CWinApp and CFrameWnd OnDDEIntitiate handlers. A call to CDialog::DoModal, AfxMessageBox, or MessageBox interferes with the ability for the MFC framework to handle these messages correctly.
RESOLUTION
It has been determined that this behavior is by design and that it is not recommended to place any of these calls within the CWinApp::InitInstance. Any password dialogs or dialog based components which need to be displayed in the InitInstance should be of the modeless type. This does not apply to a dialog based application or an SDI application.
STATUS
This problem was corrected in Visual C++ version 6.0.
MORE INFORMATION
Steps to Reproduce Behavior
- Create an AppWizard Multiple Document Application, specifying a file extension to associate with the application.
- Call a modal dialog function such as CDialog::DoModal, AfxMessageBox, or MessageBox from the CWinApp derived class' InitInstance function.
- Run the application, dismiss the dialog or message box, and save the document.
- Start the application by:
- Double-clicking the application from the Windows 95 Explorer. -or-
- Double-clicking the application from the Windows 95 Explorer. -or-
- Selecting the saved document from the Start Menu -or-
- Selecting the saved document from the Start Menu -or-
- Double-clicking the application from File Manager.
REFERENCES
For related information, please see the following article in the Microsoft Knowledge Base:
172336 PRB: Assertion Launching Program with Tip of Day & Splash Screen
Additional query words: explorer start file manager
Keywords: kbbug kbfix kbnoupdate kbvc600fix KB173261