Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 264 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
WINDOWSLANGUAGE Function broken
rdebath
Member Posts: 383
If I call it in the RTC, NAS or classic client it returns 2057.Retrieves the current Windows language setting.
If I call it from the Web service it returns 1033.
Isn't that broken? How do I change the web service to 2057 like the rest? ie: How do fix it?
In a similar fashion on a webservice on Server A the GLOBALLANGUAGE defaults to 2057 on Server B it defaults to 1033. A real nasty for this is if a web service call changes it the next web service call inherits the SAME CHANGED LANGUAGE! Only a restart defaults it.
For all machines all four specifiers in "Regional Settings" are set to UK (ie 2057).
Robert de Bath
TVision Technology Ltd
TVision Technology Ltd
0