Introduction
The
LCID property uses the location identifier number to access information on display format issues, such as currency, date, and time, that are specific to a location or region. The location identifier number uniquely defines a geographic location or region. For example, the location identifier number for France is 1036.
Example demonstrates setting the locale to British English and using the VBScript
FormatCurrency method to display the value 125 as currency with the � symbol:
Syntax:
Session.LCID(= LocaleID)
Example
<%
Session.LCID = 2057
Dim curNumb
curNumb = FormatCurrency(125)
Response.Write (curNumb)
%>
Setting Session.LCID explicitly affects all responses in a session.
If Session.LCID is not explicitly set in a page, it is implicitly set by the AspLCID metabase property. If the AspLCID metabase property is not set, or set to 0, Session.LCID is set by the default system locale.
Session.LCID can be set multiple times in one Web page and used to format data each time. Some locales need the matching codepage to be set to display characters properly. For example, to display dates and times in several locales on one page, the codepage must be set to UTF-8 (65001) to show all the characters.
If you set Response.LCID or Session.LCID explicitly, do so before displaying formatted output. Setting
Session.LCID changes the locale for both the ASP application and the scripting engine. Using the VBScript function
setLocale only changes the locale for the scripting engine.
If the locale of your Web page matches the system defaults of the Web client, you do not need to set a locale in your Web page. However, setting the value is recommended.
