FIX: Applications that are statically linked to MFC do not run on Windows NT 4.0 SP5 and earlier (330208)

SYMPTOMS

When a .NET-connected Microsoft Foundation Classes (MFC) application is statically linked to MFC, and you run this application on a computer running Microsoft Windows NT 4.0 that has Service Pack 5 or earlier installed, you may receive the following error message:

The dynamic link library OLEACC.dll could not be found in the specified path

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft Visual Studio .NET. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

837234 List of bugs that are fixed in Visual Studio .NET 2002 Service Pack 1

Hotfix information

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

   Date         Time   Size  File name
   -------------------------------------------
   06-Nov-2002  01:43  320   Mfcstatic.vcstyle

WORKAROUND

To work around this problem, use the delayload linker option when you build the application. For example,

/delayload:oleacc.dll

You must also add Delayimp.lib to the Additional Dependencies linker option. If you do not do this, you may receive an "unresolved external" error message when you link your application.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Visual Studio .NET 2002 Service Pack 1.