BUG: OLE Type Emulation for Previously Loaded Objects (111608)
The information in this article applies to:
- Microsoft OLE Libraries for Windows and Win32s 2.01
- Microsoft OLE Libraries, when used with:
- the operating system: Microsoft Windows NT 3.5
- the operating system: Microsoft Windows NT 3.51
- the operating system: Microsoft Windows 95
This article was previously published under Q111608 SYMPTOMS
OLE type emulation is the process that allows the application user to
specify that all objects of some particular type are henceforth to be
activated as objects of some alternate, emulating type. When objects of the
original type are subsequently run, the server for the emulating type is
launched to serve them.
However, this emulation does not occur for objects of the original type
that were already in the loaded state when the type emulation occurred.
When such objects are subsequently run, they are run as the original type,
not the emulating type. The original server is launched, not the server for
the emulating type.
CAUSE
When an object is in the loaded state, its object handler is running. The
handler is, in general, particular to the original type for that object,
and therefore cannot emulate another object type.
STATUS
Microsoft has confirmed this to be a problem with the Microsoft products
listed at the beginning of this article.
MORE INFORMATION
If a container application has previously loaded instances of the original
type, it should reload each such object as the alternative, emulating type
the next time that object is run.
For more information on OLE type emulation, see "Emulating Different Object
Types" in the Object Linking and Embedding Software Development Kit (SDK)
version 2.01 "Programmer's Reference" help file.
| Modification Type: | Major | Last Reviewed: | 12/3/2003 |
|---|
| Keywords: | kbBug KB111608 |
|---|
|