☰
Current Page
Main Menu
Home
Home
Editing My-date-formats-are-broken-in-Excel-when-I-open-a-file-in-a-computer-with-a-different-culture-setting
Edit
Preview
H1
H2
H3
default
Set your preferred keybinding
default
vim
emacs
markdown
Set this page's format to
AsciiDoc
Creole
Markdown
MediaWiki
Org-mode
Plain Text
RDoc
Textile
Rendering unavailable for
BibTeX
Pod
reStructuredText
Help 1
Help 1
Help 1
Help 2
Help 3
Help 4
Help 5
Help 6
Help 7
Help 8
Autosaved text is available. Click the button to restore it.
Restore Text
#My date formats are broken in Excel when I open a file in a computer with a different culture setting. [[_TOC_]] #Question 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? #Answer 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. ##Workarounds 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. ###Use Uniform Culture Make sure to set the proper culture setting for the izenda.comer so that the export file is exported with the correct placement of periods and commas: [[AdHocSettings.Language|http://wiki.izenda.com/API/CodeSamples/Language]] = AdHocLanguage.German; ###Excel Settings In Excel's Advanced system settings, it is possible to change the characters used as system separators. ###Expression 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: convert(varchar, [DateField], 101) ###Custom Format It is possible to use a [[custom format|/API/CodeSamples/Formats]] to handle date conversion as well.
Uploading file...
Header
 **This documentation is for the legacy Izenda 6 product. Documentation for the new Izenda 7 product can be found at [[https://www.izenda.com/docs/|https://www.izenda.com/docs/]]**
Sidebar
 --- * [[Izenda 7 Series Documentation|https://www.izenda.com/docs/]] * [[Release Notes]] * [[Upgrade Best Practices|FAQ/Izenda-Update-Best-Practices]] * [[FAQ]] * [[Tutorials]] * [[The Izenda API|/API/AdHocConfig]] * [[The AdHocSettings class|/API/AdHocSettings]] * [Developer Links and Guides](/Guides/Developer-Links-and-Guides) * [[Known Issues]] --- * <a href="http://www.izenda.com" rel="nofollow" target="_blank">Izenda Website</a> * [Product Video](https://www.youtube.com/watch?v=X3-yWFq0w5A) * <a href="http://www.izenda.com/blog" rel="nofollow" target="_blank">Izenda Blog</a> * <a href="http://www.izenda.com/company/" rel="nofollow" target="_blank">About Us</a> * <a href="http://www.izenda.com/contact-us/" rel="nofollow" target="_blank">Contact Us</a> --- * [Guide To Report Design](/Guides/ReportDesign) * [Making Custom Forms Video](http://www.youtube.com/watch?v=5b2axJlgdFs) --- * [[Acknowledgements]]
Edit message:
Cancel