Are WLM, OE and WM to blame here for not respecting the meaning of csv? In essence, WLM, OE and WM export to the dsv-format delimiter separated value. Should WLM, OE or WM look at your configured list separator instead and use that? Should Outlook? It would break interoperability between systems if the format of a file is depended on end-user configuration. Outlook however expects a comma as a separator in a csv-file as that is what the file format stands for comma separated value. If this was set to a comma, you probably wouldn’t have been reading this -)
#Import csv contacts into outlook headers windows
The reason why Windows Live Mail (WLM), and also Outlook Express (OE) and Windows Mail (WM), used a semi-colon as a separator instead of a comma is because that is what is specified in your Region Settings in Windows to be used as the list separator. Separated file can be done easily via Notepad. Turning a semi-colon separated file into a proper comma Go back to Outlook and import the file.
So replace the semi-colons for commas and you’re done.
The issue is that instead of commas (, ) being used as a separator, you probably see semi-colons ( ) being used instead. I’m not sure whether I should call this a bug or a feature but luckily the solution is quite easy.įor a change, let’s start with the solution and then I’ll explain my dilemma of whether to call this a bug or a feature. How can I import my contacts into Outlook? The file is in csv-format but when I try to import it into Outlook, I'm being prompted to Map Custom Fields but everything is just on a single line. I’ve exported my contacts from Windows Live Mail on my old computer and now I want to import them into Outlook on my new computer.
0 kommentar(er)
