There are some cases where I export data from SQL server to a text file and want to open it with Excel. I do this because some of my columns have text that has newlines [ char(13) + char(10) ], which will not correctly import into Excel, when importing from SQL Server to Excel directly. There should be other cases where a user can't choose a pre-determined text qualifier from some proprietary software.

This is where Excel should allow the user to choose the text qualifier instead of only having the pre-defined choices.

LibreOffice Calc allows this functionality, and I sometimes open the text file in LibreOffice, since it does allow me to choose the text qualifier, and then the file will import correctly. Once in LibreOffice, I save the file to Excel format, and then I have my data.

I shouldn't have to use LibreOffice to do something that Excel could easily do if I could choose a text qualifier.

Using my attached sample file in Excel, when a user opens a new text file in the following way starting with Data tab on the ribbon:

DATA>Get External Data>From Text> then choose your text file

On the popup window Text Import Wizard - Step 1 of 3 choose Delimited, and check the box My data has headers

Then on Text Import Wizard - Step 2 of 3

Choose comma as a delimiter, but I can't choose a text qualifier, which in this case, is the tilde. But unfortunately in Excel, I can't choose my text qualifier, and thus my data doesn't import correctly.

When I try in LibreOffice Calc, I just open the csv file, and under Text Import, choose the following Separator Options: Comma, Merge Delimiters, and String Delimiter (set to in this case) Tilde. Then I get the data importing correctly.

Thus, unfortunately or fortunately, I save in Excel format, and now can use properly in Excel.

Please allow a user to choose a TEXT QUALIFIER of their liking!

I have attached my sample file for testing... you can see that the tilde is the text qualifier, and is delimited by commas, like a standard csv file.

Thanks for your consideration, and please don't make us use LibreOffice Calc any longer!

Many businesses use programs like Peachtree, or even very large platforms like Meditech and Epic in Hospitals. They do not always have good implementations, and as a way to salvage poor operations we use data dumps into excel. The way the vast majority of power users have used this in the past is to use VISUAL BASIC to automate TONS of data manipulation. I have found, very clearly, that Office 2010 64 bit can be rolled out to several people and shared excel files with visual basic in them work fine. If one person has office 2013, or 2016 or 365 64 bit and they use the same file, it corrupts the file. It does something wrong to the visual basic inside it. I can then open the file into a 32 bit version of excel and re-save it, but then the code does not work. Certain commands confuse excel and visual basic and it does not recognize it as a VB command. So you then have to insert in front of certain lines of VB code. To see your issues, you need 4 PC's, two with office 2010 64 bit (which works, so WHY are you taking it away! ) and one with Office 2016 64 bit and one with office 2013 64 bit. Make a file using VB code, variables etc. Edit it on one 2010 PC. Run the file on both 2010 PC's to see it works. Then open the file and run it on the 2016 PC.

Some stocks are not easy to search, it would be easier if we could just enter the ticker and market, as there is just one ticker for stock and market.

Other option could be integrating somehow all the predictive results that Morningstar offers when you start typing. Besides I find somehow difficult to pick the right stock, as sometimes you are not able to select from which market you want to get it.
For example CVR Partners is not listed when searched and if you search by UAN, which is the NYSE ticker it just finds Yorbeau at German market, which is another company.