FAQ/My-date-formats-are-broken-in-Excel-when-I-open-a-file-in-a-computer-with-a-different-culture-setting.md
... ...
@@ -0,0 +1,35 @@
1
+#My date formats are broken in Excel when I open a file in a computer with a different culture setting.
2
+
3
+[[_TOC_]]
4
+
5
+#Question
6
+
7
+My date formats are broken in Excel when I open a file in a computer with a different culture setting. Instead of a date, I just get numbers. I exported this file in an environment set to one culture setting, and opened it in an environment with a different culture setting. Why is this happening?
8
+
9
+#Answer
10
+
11
+This is a known issue, caused by a difference between how different cultures signify numbers with decimals. The American standard for large numbers is 123,456.789. Some European countries have a different standard, as in 123.456,789. That is, there is a difference of opinion on when to use periods and when to use commas. A file exported with the numerical date value of 44444.44 will be interpreted either as a proper date or as a number, depending on which culture setting is being used to interpret this value.
12
+
13
+##Workarounds
14
+
15
+This issue cannot be fixed in Izenda as it is not a bug. Some alternate method of handling the issue is necessary in your environment.
16
+
17
+###Use Uniform Culture
18
+
19
+Make sure to set the proper culture setting for the Izenda user so that the export file is exported with the correct placement of periods and commas:
20
+
21
+[[AdHocSettings.Language|http://wiki.izenda.us/API/CodeSamples/Language]] = AdHocLanguage.German;
22
+
23
+###Excel Settings
24
+
25
+In Excel's Advanced system settings, it is possible to change the characters used as system separators.
26
+
27
+###Expression
28
+
29
+Instead of exporting a file with a numeric date value and an attached date format which is open to interpretation, it is possible to write an [[Expression|/Guides/ReportDesign/15.0-Expressions-in-Izenda]] which converts the numeric date value to a fixed string. One example would be something like:
30
+
31
+convert(varchar, [DateField], 101)
32
+
33
+###Custom Format
34
+
35
+It is possible to use a [[custom format|/API/CodeSamples/Formats]] to handle date conversion as well.