From my experience 6.5 Enterprise Server date format dependencies are as follows:
DATE FORMAT OF USER PROMPTS
The date format set for the entry USER_INPUT_DATE_FORMAT in the .prm file under the type of DB being connected to in the location :\Business Objects\BusinessObjects Enterprise 6\dataAccess\
DATE FORMAT OF WEB SERVER
Date format settings in the Regional Options on the web server
The date format set for the entry ID_DATEFORMAT in the following resource & locale files (This is what is displayed on your infoview report list):
a. resource_en.msg
b. locale_en.msg
c. locale_en_XX.msg
I have customised these files for my installation to YYYY/MM/DD HH:MM:SS since my requirement is for date in this format & the web server locale setting is US.
I have modified the input date format in my prm file.
I have passed it to dd/mm/yyyy.
and in my infoview I had date in prompt in french.
I haven’t do like you suggest.
All was perfect.
But yesterday, i have upgrade my server to 6.5.2. and now my problem is come back!!!
I’m lost !
Could you help me to find a way to fixed my problem ?
Seems to me that this is becomming a bit of a common issue with Bobblers!
I have also changed the .prm’s, and checked the OS date settings, but to no avail, …but not the admin console yet - could anyone let me know how to do this? (Dummy steps please - as I am not very familar with the console yet!!)
I have tried that, and it still hasnt worked… I checked the Console as well once the server had restarted to check that the changes had taken effect, and they had…
any other ideas?
(the way that I am checking is by parsing a predefined condition that has the input date set to DD/MM/YY ie it Arrival date between CAST(‘27.12.2003’ as DATETIME) and CAST(‘31.12.2004’ as DATETIME)), this returns the error message…
Hmm - I have also searched for the .msg files on my local pc, and found nothing… Is this to be expected?
…on the server I found them, but I dont know how to change them - as they are not normal network files - any advice on changing the following files? - Anything is worth a try!!!
Ahhhhhhh - Have found the problem - in Data Source (ODBC) settings, config options the ‘Language of SQL Server system messages to:’ option was set to English… I thought that this was correct, until I found out that there is actually a “British English” option - which is dd/mm/yyy format, whilst ‘English’ is actually mm/dd/yyy format…
Never would have noticed that!
Changed it on my local pc, the server and the DB; All sorted now.