Module Language Translated on Move or Copy into New Project

Last reviewed: July 29, 1997
Article ID: Q117135
The information in this article applies to:
  • Microsoft Visual Basic Programming System, Applications Edition, version 1.0
  • Microsoft Excel for Windows, version 5.0
  • Microsoft Project for Windows, version 4.0

SYMPTOMS

When 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.

The referenced languages must correspond to the Language/Country setting for the project. You can, however, reference a project using one language from a project written in another language.

Note that objects and text strings are not translated when you copy or move a module into another project.

WORKAROUND

To work around this behavior, use either of the following methods:

  • Move or copy the module back to the original project to translate the code in the module back to the original language.

    -or-

  • Change the default Language/Country setting to the language that is used in your module, create a new project using this default, and then move or copy the module to the new project.

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

For 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 : kberrmsg kbprg kbusage
Version : 1.00
Platform : WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: July 29, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.