The information in this article applies to:
SYPTOMSWhen a type library with more that 256 typeinfos is generated by using mktyplib or ICreateTypeLib/ICreateTypeInfo, a corrupt type library may be produced. This will usually happen on a fast computer like a Pentium when the type library is being saved to a fast storage medium like a local hard drive. It may not happen on a slower computer like a 486 or when the type library is saved to a slower storage medium like a floppy disk drive or a network drive.CAUSE
A byte counter is used by OLE as part of a timestamp for each typeinfo that
is written into the type library. If the type library generator is running
on a fast computer and there are more than 256 typeinfos in the type
library, more than 256 typeinfos could be written per second. This causes
the counter to repeat itself, which causes the corruption. WORKAROUND
A workaround to this problem is to limit the number of typeinfos in each
type library to 256 or less. If a type library requires more typeinfos, it
can create those typeinfos in other type libraries and reference those type
libraries using the importlib directive. STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed
at the beginning of this article. Additional query words: 2.0 4.0 4.00 kbbuglist
Keywords : kbole kbNTOS351bug kbNTOS400fix kbWinOS95bug kbGrpCom kbDSupport LeTwoAto |
Last Reviewed: October 26, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |