Setting the locale in Enterprise Guide

[Ian_A]

Hi,

Does anyone know if its possible to change the default locale at the point when Enterprise Guide is initialised? This appears to be easy to do when connecting to a 'Local' server is it can be controlled by the main SAS Foundation config/autoexec file. This setting does not appear to be honoured however when connecting through a metadata server. I have tried adding the LOCALE option to the SASApp and Workspace server autoexec/config files to no avail (bouncing the object spawner in the process). Each time Enterprise Guide is initialised it defaults to EN_US regardless of any other settings. I know this can be configured on the client side as an option set whenever EG connects to a server. The preference would be to control this from the server if possible.

Thanks

[ChrisHemedinger]

Ian,

You can try setting up a different shortcut for EG that specifies a specific locale/culture code.  For example:

  SEGuide.exe /culture:it

Will launch EG with Italian culture settings.  When you connect to SAS, the LOCALE option should be set to Italian unless there is an initialization statement in the SAS autoexec to change that.

Note that you don't actually need the language-specific content to be installed for EG to use this option.  If you specify a culture code for a language that you don't have installed, the EG user interface will show in English.  But culture-specific behaviors (such as date style) will still be used.

Chris

[Ian_A]

Thanks for the solution Chris, much appreciated.

The only issue we have is that with EG being deployed across a reasonable sized user base, we would have to implement this solution for each client. Is there anything we can do from the server tier which would force EG to open with a locale other than EN_US? If there is a way of doing this then that would be the preference here, otherwise we will look at using culture settings or even setting the locale as an option submitted whenever EG connects to a server.

Thanks,

Ian

[ChrisHemedinger · Accepted solution]

Ian,

I can't think of an easy way to force the EG locale behavior from the client, other than use of the shortcut method I described.

But you can use OPTIONS LOCALE= in a startup set of statements, as you mentioned.

Chris

[Ian_A]

Thanks Chris, will give one of those options a go.

Ian