ACC: Using English Keywords in International Applications

Last reviewed: May 21, 1997
Article ID: Q142044
The information in this article applies to:
  • Microsoft Access versions 2.0, 7.0

SUMMARY

Advanced: Requires expert coding, interoperability, and multiuser skills.

When you develop an international application, you should use English keywords in all object references and Visual Basic for Applications code to maximize compatibility with different language editions of Microsoft Access. If you use non-English, localized keywords, they may not work properly when you run the database in a different language edition.

MORE INFORMATION

Here are specific cases when you should use English keywords in international applications:

  • Use the English keyword "Forms" when referencing form objects. For example, use:

          Forms![Form Name]![Control Name]
    

    Instead of:

          <Localized word for Forms>![Form Name]![Control Name]
    
  • Use the English keyword "Reports" when referencing report objects. For example, use:

          Reports![Report Name]![Control Name]
    

    Instead of:

          <localized word for Reports>![Report Name]![Control Name]
    
  • Pass English, not localized, arguments to the GetOption() and SetOption() functions.

NOTE: If you use non-English keywords, you may have to manually correct any errors they cause when the database is run using a different language edition of Microsoft Access.


Additional query words: globalization international int'l localization
localisation
Keywords : kbusage SynGnrl
Version : 2.0 7.0
Platform : WINDOWS
Hardware : X86
Issue type : kbinfo


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: May 21, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.