The information in this article applies to:
SYMPTOMSWhen you move or copy a Microsoft Visual Basic Programming System, Applications Edition module from one project (such as a Microsoft Excel workbook or a Microsoft Project project), into another project, the code in the module is translated to the language used in the receiving project. If the receiving project does not already contain a module, the inserted module is translated to the language of the default Language/Country setting in the Module General tab of the Options dialog box. CAUSE
All modules contained in a project must use the Language/Country setting
that is designated for that project. Therefore, when you insert a module
into another project, the code contained in the module is translated to the
language that is used in the project into which the module is inserted.
This is true even when the project into which you insert the module does
not yet contain a module. In this case, the project uses the default
Language/Country setting, and the code contained in the module that you
insert into this project is translated to this language.
WORKAROUND
To work around this behavior, use either of the following methods:
-or- STATUSMicrosoft 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 INFORMATIONFor more information about referencing a foreign language object library in an application that supports Microsoft Visual Basic Programming System, Applications Edition, query on the following in the Microsoft Knowledge Base: visual and basic and foreign and library and error Additional query words: intl
Keywords : |
Last Reviewed: October 19, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |