I've been using FileSeek for a few years now, but today was the first time I ever had the need to export results to a CSV file! However, when I tried to open the resulting file in Excel, every line was loaded into column A.
Why?
My OS is English (Windows 8.1 Enterprise), but my
locale (currency, keyboard etc.) is set to Portugal/Portuguese. The CSV files generated by FileSeek use a comma "," as the record separator, but most European countries use the semicolon ";" because the comma is actually the
decimal separator.
In my case the solution was simple - since every record was also wrapped in double quotes, I just replaced "," with ";" and the file opened fine. But it would be great if FileSeek could use the system defined record separator, instead of assuming US (like) regional settings
.
Thanks for listening!
