BUG: IROT::Register() and IOL::SetDisplayName() Inconsistency

• Microsoft OLE Libraries for Windows and Win32s, version 2.01
• Microsoft OLE Libraries, included with:

      - Microsoft Windows NT, versions 3.5 and 3.51
      - Microsoft Windows 95
  

SYMPTOMS

IRunningObjectTable::Register() allows monikers that are not valid filenames to be registered as file monikers. However, if the display name string passed to IOleLink::SetSourceDisplayName() is not a valid filename, SetSourceDisplayName() returns STG_E_FILENOTFOUND.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

This inconsistency may become apparent when an OLE application is calling IOleLink::SetSourceDisplayName() to change the source of a link object. It is possible that a new file moniker that is not a valid source name will be registered on the running object table--for example, a moniker of "New 1" for a new, as yet unsaved document. It will not be possible to use SetSourceDisplayName() to link to this object, however, because "New 1" is not a valid filename, and therefore it will be rejected by SetSourceDisplayName().