If you are using Excel to manipulate the .CSV file, you may want to try changing the extension to .txt and then opening it in Excel using the Text Import Wizard.That may alleviate some of Excel's auto-formatting of the file. Double quotes can cause problems with importing even when they're supposedly in the right place on the .CSV file. If you can live without them, I suggest stripping them out before importing.

Thanks, but that is not an answer to my question.

What I meant to say, the exported CSV file, generated by Sage, is incorrect.

Incorrect in what way?

the double quote chars in Sage db are not escaped in the CSV file.

In other words, Sage produced incorrect CSV files.

What to do to tell Sage to produce correct CSV files?

This has nothing to do with Excel or any other software.

I deleted an earlier post after I did some research. The exported .csv file for any string out of the available exports puts double quotes around the string, and that's it. You can see this when you open any CSV file export in Notepad. The export does not supply any escaping function for internal double quotes in strings.

Sage should fix this problem, no?

It would be easy fix the source code,

to escape the double quote chars when exporting.

8 years, no solution? I am having this export problem as well. Our database is too big to be opened in notepad...

Time to purge and if you have the " marks in your Sage 50 inventory items, remove them.  They tell Excel to skip to the next column.

Shirley

Too big to open in notepad... Open in a Browser.

As to the file Type CSV. It is a poor choice. Using comma as a delimiter is always problematic. Using commas in descriptions, memos and other data fields is not unheard of. The double quotes can also be an issue as they have multiple uses. Abbreviation/symbol for inches.
It would be far better to do three things.

First, enable a method of excluding such characters in descriptions as an option.

Second, for the Export, enable the option to select/define the delimiter. Experience for me has led me to prefer the | symbol. The ~ could be workable. Unfortunately using a TXT export uses the TAB character, which can be as troublesome as the comma.

Third, for any data field defined as a Text field, allow the use of double quotes to begin and end the string as an Option.