Before posting, and to avoid disappointment, please read the following:
- This forum is not for 2BrightSparks to provide technical support. It's primarily for users to help other users. Do not expect 2BrightSparks to answer any question posted to this forum.
- If you find a bug in any of our software, please submit a support ticket. It does not matter if it is freeware or you haven't yet purchased the software. We want to know about any and all bugs so we can fix them as soon as possible. We usually need lots of information and details from you to reproduce bugs and that is better done via a support ticket and not this forum.
- If you are entitled to technical support then please submit a support ticket. Please do not post the same question to the forum and also via a support ticket. Once again, 2BrightSparks does not provide technical support via this forum.
FoC Bug: Unquoted Full Filename in Export
-
fredradford
- Enthusiastic
- Posts: 19
- Joined: Thu Apr 10, 2014 7:59 pm
FoC Bug: Unquoted Full Filename in Export
In FoC 2.5.0.0 when you export to CSV the Full Filename is not enclosed in quotes, so rows with filenames with commas in them are not imported into Excel correctly.
-
Dave Wilkins
- 2BrightSparks Staff
- Posts: 1024
- Joined: Thu Jan 04, 2007 10:02 am
Re: FoC Bug: Unquoted Full Filename in Export
Yes, verified and passed to development department for a fix due course
-
Dave Wilkins
- 2BrightSparks Staff
- Posts: 1024
- Joined: Thu Jan 04, 2007 10:02 am
Re: FoC Bug: Unquoted Full Filename in Export
Actually, if you check the exported CSV file with a text editor, you should see the Full Filename (both header and values) is/are wrapped in quotes. There appears to be a bug in Excel so that if you right-click the CSV file > Open (in Excel - or, accept the FOC prompt to open it, which does the same thing), Excel will strip the quotes from field-1. Go figure...
If you open Excel 'empty' and Import the data (CSV file) into a blank worksheet, and jump though the hoops of telling it what wrapping character (") and delimiters (,) are used, it Imports perfectly fine for me. I even tested it by adding a comma (with a text editor) to a filename of an EXE, and it Imported fine using the manual method (comma present, but no field/column-break occurred).
If you open Excel 'empty' and Import the data (CSV file) into a blank worksheet, and jump though the hoops of telling it what wrapping character (") and delimiters (,) are used, it Imports perfectly fine for me. I even tested it by adding a comma (with a text editor) to a filename of an EXE, and it Imported fine using the manual method (comma present, but no field/column-break occurred).