Excel renders separators in CSV files incorrectly

Started by Kari

Hi,

When exporting scan results to CSV, values AND columns are both separated by using comma. This throws off data in Excel tables.

Would it be possible to use a different separator for values and columns? Or at least move the "shared resources" to be last on the report.

Here's my [CSV export]. It could very well be my lack of Excel competence.
I open the file in Excel, select the first column, then go to data-tab -> Convert text to columns, then select Delimited. From there it goes wrong for me.
SoftPerfect Support forum - Ann avatar image
Ann

Excel renders separators in CSV files incorrectly - Solution   27 May 2025, 11:16

It appears there is a mismatch between what Microsoft Excel expects in a CSV file and what it actually encounters. Although CSV stands for "Comma-Separated Values", there are commonly two types of delimiters used: commas and semicolons. In your case, Excel is likely configured to expect semicolons.

To resolve this:
  1. Open Network Scanner and go to Settings - View tab.
  2. In the File Output section, for the CSV file delimiter setting, choose Custom and enter a semicolon (;), as shown below.
  3. Apply the settings and resave your data as a CSV file.
Once done, you should be able to open the file directly in Excel without needing to use the 'Text to Columns' feature.

SoftPerfect support forum


Here is an example using your CSV file. Everything is displayed correctly in Excel:

SoftPerfect support forum

Reply to this topic

Sometimes you can find a solution faster if you try the forum search, have a look at the knowledge base, or check the software user manual to see if your question has already been answered.

Our forum rules are simple:

  • Be polite.
  • Do not spam.
  • Write in English. If possible, check your spelling and grammar.

Author:

Email:

Subject

A brief and informative title for your message, approximately 4–8 words:

     

Spam prevention: please enter the following code in the input field below.

  *******   ********   **     **        **  **     ** 
 **     **  **     **  **     **        **  **     ** 
        **  **     **  **     **        **  **     ** 
  *******   **     **  **     **        **  ********* 
        **  **     **  **     **  **    **  **     ** 
 **     **  **     **  **     **  **    **  **     ** 
  *******   ********    *******    ******   **     ** 

Message: