Tweet
We just became aware of a Microsoft bug with how date or time functions in VBScript behaves, depending on parameters related to the user that is logged in at the server, and the version of the OS.
This means that even with the correct "Regional Options" setting on the Windows server, you may still get the wrong regional formatting for the dates in the search results. Note that this only affects the ASP version of the script ("search.asp").
Here are the Microsoft Help & Support articles related to this issue:
"VBScript Date and Time Functions May not be Formatted Properly in Non-English (US) Locales":
http://support.microsoft.com/default...;EN-US;Q264063
"INFO: Behavior of Date/Time Format Differs When Accessed from Active Server Pages":
http://support.microsoft.com/default...;EN-US;Q306044
A number of solutions and workarounds are provided on the above pages. With the first article, it specifically says that the problem is with Windows 2000 - and that the problem will not occur when no user is logged in to the server interactively (at the console), ie: it will use the system default regional options date correctly.
Most of the other solutions (on the second page) rely on registry changes. We have not tested these and would advise consulting with your server administrator before making these changes.
Hope that helps anyone out there who may be coming across these problems.
This means that even with the correct "Regional Options" setting on the Windows server, you may still get the wrong regional formatting for the dates in the search results. Note that this only affects the ASP version of the script ("search.asp").
Here are the Microsoft Help & Support articles related to this issue:
"VBScript Date and Time Functions May not be Formatted Properly in Non-English (US) Locales":
http://support.microsoft.com/default...;EN-US;Q264063
"INFO: Behavior of Date/Time Format Differs When Accessed from Active Server Pages":
http://support.microsoft.com/default...;EN-US;Q306044
A number of solutions and workarounds are provided on the above pages. With the first article, it specifically says that the problem is with Windows 2000 - and that the problem will not occur when no user is logged in to the server interactively (at the console), ie: it will use the system default regional options date correctly.
Most of the other solutions (on the second page) rely on registry changes. We have not tested these and would advise consulting with your server administrator before making these changes.
Hope that helps anyone out there who may be coming across these problems.