Hullo community,
This is my first post - and I hope that someone can help.
I have a folder full of auto-generated (from a process tool) *.csv files - these have comma delimiters when viewed notepad, are recognised as Microsoft Excel Comma Separated Values File in windows and open in Excel (2010) with all the columns and rows where you would expect them.
My problems is that when I opened a few to make some edits, then CTRL+S the files saved - it took me a while to realise the "Saving as CSV-formatting will be lost" dialogue never appeared - when I checked the files (still called *.csv, still reporting to be a comma separated file) they opened in Excel as one column of text. A check in notepad showed that the file was flat text with no delimiters.
When I opened another (unedited) *.csv from this folder and chose "Save As" the default option (which should be the original file type) it was wanting to save as UNICODE text.
No other *.csv files exhibit this strange behaviour - only the ones in this folder - created by this tool - The danger is that others will open and save these files and break the delimiters.
Any ideas?
This is my first post - and I hope that someone can help.
I have a folder full of auto-generated (from a process tool) *.csv files - these have comma delimiters when viewed notepad, are recognised as Microsoft Excel Comma Separated Values File in windows and open in Excel (2010) with all the columns and rows where you would expect them.
My problems is that when I opened a few to make some edits, then CTRL+S the files saved - it took me a while to realise the "Saving as CSV-formatting will be lost" dialogue never appeared - when I checked the files (still called *.csv, still reporting to be a comma separated file) they opened in Excel as one column of text. A check in notepad showed that the file was flat text with no delimiters.
When I opened another (unedited) *.csv from this folder and chose "Save As" the default option (which should be the original file type) it was wanting to save as UNICODE text.
No other *.csv files exhibit this strange behaviour - only the ones in this folder - created by this tool - The danger is that others will open and save these files and break the delimiters.
Any ideas?