FoC Bug: Unquoted Full Filename in Export

DeleteOnClick, EncryptOnClick, FindOnClick, HashOnClick, PatchOnClick, ScrambleOnClick, UndeleteOnClick
fredradford
Enthusiastic
Enthusiastic
Posts: 19
Joined: Thu Apr 10, 2014 7:59 pm

FoC Bug: Unquoted Full Filename in Export

Postby fredradford » Fri Apr 11, 2014 10:36 pm

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
2BrightSparks Staff
Posts: 1879
Joined: Thu Jan 04, 2007 10:02 am

Re: FoC Bug: Unquoted Full Filename in Export

Postby Dave Wilkins » Mon Apr 14, 2014 8:29 am

Yes, verified and passed to development department for a fix due course

Dave Wilkins
2BrightSparks Staff
2BrightSparks Staff
Posts: 1879
Joined: Thu Jan 04, 2007 10:02 am

Re: FoC Bug: Unquoted Full Filename in Export

Postby Dave Wilkins » Tue Apr 15, 2014 9:15 am

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).


Return to “OnClick Utilities”



Who is online

Users browsing this forum: No registered users and 3 guests