
#Outlook error 998 windows
To change your list separator value in Windows However, as I said, you can configure the delimiter in your Regional Settings in Windows which would make it a feature again and will enable to WLM, OE and WM to create a proper csv-file again. In this format the choice of the delimiter is not restricted to a comma. 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 -) 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
