This is what you get when right clicking on a code node and choosing Properties:
My OS locale is British English, in which dates are written as dd/mm/yyyy but the date being displayed here is in US locale (mm/dd/yyyy).
EG's git History window is correctly displaying dates in dd/mm/yyyy format.
What should I be doing to get the dates in the screenshot above to be in dd/mm/yyyy format?
I am using EG 7.13 on Windows 7.
Change your shortcut to launch EG to add the "/culture:en-GB" option.
Example:
"C:\Program Files (x86)\SASHome\x86\SASEnterpriseGuide\7.1\SEGuide.exe" /culture:en-GB
Result:
Change your shortcut to launch EG to add the "/culture:en-GB" option.
Example:
"C:\Program Files (x86)\SASHome\x86\SASEnterpriseGuide\7.1\SEGuide.exe" /culture:en-GB
Result:
Thanks Chris!
Thanks @jtlbg for asking the question! It leads to better software...
Just for completeness, this is a bug. For the formatting of those specific datetimes (on the Summary page of the element properties), EG is incorrectly using the UI culture (corresponds with the EG display language) rather than the Windows Regional settings. As a direct result of you bringing this to our attention (thanks!), it will be fixed in the next release. Until then, I second using Chris' workaround.
Casey
Register today and join us virtually on June 16!
sasglobalforum.com | #SASGF
View now: on-demand content for SAS users
Hello All,
FYI - We are seeing a kind of opposite behaviour to this that the /culture:en-GB corrects.
A user has identified that in EGV7.11 in Query Builder they had to input date in the MMDD (EN_US) format but in Query Builder EGV7.13 the date is being picked up as DDMM (EN_GB).
(As you probably already know) Testing has shown that specifying "C:\Program Files (x86)\SASHome\x86\SASEnterpriseGuide\7.1\SEGuide.e
Thanks,
Yes, changes were made to the Query Builder so that it now honors the user's Windows Regional settings when entering date values.
Here is a longer-winded explanation of how cultures are used in EG:
There are two cultures in play... a (non-UI) culture and a UI culture.
1) The (non-UI) culture controls how dates, times, currency, etc. are formatted and displayed. By default, this culture is automatically picked up from the user's Windows Regional settings. So, dates, times, currency, etc. will appear according to your Windows Regional settings (unless there is a bug, like above!). However, this can be overridden by specifying the /culture command-line option.
2) The UI culture controls the language resources that are loaded (the language in which translated strings are displayed in EG). We refer to this as the EG display language. You can change this in EG's Tools->Options->General->Enterprise Guide language settings->Display language. Or, you can override the display language by specifying the /uiculture command-line option.
Having separate cultures allows you to independently control the EG display language and how dates, times, currency, etc. are formatted.
Note: If you specify the /culture command-line option without also specifying the /uiculture option, the value specified in the /culture option is used for both cultures (formatting of date, time, currency values AND EG display language).
Casey
Register today and join us virtually on June 16!
sasglobalforum.com | #SASGF
View now: on-demand content for SAS users
Are you ready for the spotlight? We're accepting content ideas for SAS Innovate 2025 to be held May 6-9 in Orlando, FL. The call is open until September 16. Read more here about why you should contribute and what is in it for you!
What’s the difference between SAS Enterprise Guide and SAS Studio? How are they similar? Just ask SAS’ Danny Modlin.
Find more tutorials on the SAS Users YouTube channel.
Select SAS Training centers are offering in-person courses. View upcoming courses for: