I have a problem with my .csv file coming from ODK aggregate indeed with Excel 2010 I cannor important properly value with comma (,) in the filed on excel file 2010. However when I use Excel 2013 this issue doesn't occur.
The XLSForm for my questionnaire have been generated by using Excel 2013 do you think this can impact on the final setting of the .cvs file exported from ODK aggregate and explain why this problem only occurs on excel 2010 but not on excel 2013?
I haven't looked at how robust the csv import library code is in ODK
Collect.
Microsoft Excel has many quirks around the csv export. It is not surprising
that different versions fail to produce valid csv files in different ways.
If at all possible, avoid the use of double-quotes, new-lines, and commas
within your data values. These are all special characters in CVS files.
It is likely that Excel does not detect and wrap these characters in a
manner that conforms to this standard.
···
On Thu, Sep 10, 2015 at 12:56 AM, wrote:
Hi All,
I have a problem with my .csv file coming from ODK aggregate indeed with
Excel 2010 I cannor important properly value with comma (,) in the filed on
excel file 2010. However when I use Excel 2013 this issue doesn't occur.
The XLSForm for my questionnaire have been generated by using Excel
2013 do you think this can impact on the final setting of the .cvs file
exported from ODK aggregate and explain why this problem only occurs on
excel 2010 but not on excel 2013?