you asked for the client's language, so that's what you get. This is for all client types.
The function WINDOWSLANGUAGE returns the OS language setting (which might of course be different)
I think there is no function available to get the service's language - the service has to serve any (available) language so it its language should not be of any importance.
In the Classic Client ( NAV 2009R2 and earlier ) there also was a LANGUAGE function, that could be set for each form, report or dataport. This function is not available in 3-tier deployments.
Yep that's what I asked for, but that's not what 'GLOBALLANGUAGE' suggests to me and MSDN wasn't clear. Global, to me, suggest some kind of common language (service). I would have called it 'CLIENTLANGUAGE' myself
Thanks.
Answers
See https://msdn.microsoft.com/en-us/library/dd338772(v=nav.90).aspx
Blog - rockwithnav.wordpress.com/
Twitter - https://twitter.com/RockwithNav
Facebook - https://facebook.com/rockwithnav/
MSDN doesn't really explain anything, as is often the case.
Is it the service language, or the actual language in which the user's client is running?
The function WINDOWSLANGUAGE returns the OS language setting (which might of course be different)
I think there is no function available to get the service's language - the service has to serve any (available) language so it its language should not be of any importance.
In the Classic Client ( NAV 2009R2 and earlier ) there also was a LANGUAGE function, that could be set for each form, report or dataport. This function is not available in 3-tier deployments.
Thanks.