I have a question concerning the DateTime formatting of columns in Excel documents created with Aspose (v184.108.40.206 & v220.127.116.11).
We have an ASP.NET web application with which users can download a generated Excel document, containing, amongst other data, columns with DateTime fields.
The application runs on a Windows 2003 Server production machine (English/US OS install), but with Dutch regional settings. In the application the columns that contain datetime fields are explicitly set to display format 22 (m/d/yy h:mm).
The Excel is filled from a dataset, that has datetime columns with the dd/mm/yyyy hh:mm datetime format, we also want the Excel columns to have this datetime format.
1.) We want the datetime fields to be formatted in the dd/mm/yyyy hh:mm style. Is there a display format that forces this style?
2.) With the current display format (22), on our development machines (which have Dutch OS and regional settings), we get the desired dd/mm/yyyy hh:mm output in our Excel documents.
When we run it on the production machine however, the formatting is different; as long as the 'days' segment of the datetime in the source dataset is lower than 13, the format is mm/dd/yyyy hh:mm. When it is 13 or higher
the datetime formatting switches to the dd/mm/yyyy hh:mm format. My guess is that Aspose detects an overflow and switches formatting. Example:
8-10-2007 9:40 -> mm/dd/yyyy format
13-08-2007 11:35 -> dd/mm/yyyy format
My question is, how does Aspose decide which formatting to use? The explicit formatting style 'm/d/yyyy hh:mm' doesn't seem to force itself on the Dutch OS development machine (it gives us the desired dd/mm/yyyy hh:mm format), and behaves
strangely on the English/US production machine (switching formatting when there is an overflow, and apparantly not adhering to the regional settings, which are set to Dutch).
If anyone can help us find a solution we would be very grateful.
Thanks in advance.