Thanks Kevin. Turns out it was a weird bug which went away after I restarted MoneyDance.
However, I'm having a problem importing the file now having selected it. I have two columns, with the headings Date and Close. I am using the date format DD/MM/YYYY which is the same as MoneyDance is setup to use. Example below:
Turns out loading into a text editor showed nothing untoward, but in response to your reply I checked some more using the command line. The command 'more vwrl.csv' showed there was a special character at the beginning U<+FEFF>. Really surprising! Here's the explanation, I'm using Excel on the Mac and Excel loves messing with the first byte of CSV files:
Thanks for passing along your findings. I'll have to keep that one in mind.
I've seem some strange behavior before when importing csv files. One odd resolution that comes to mind is simply entering a dummy line in the first data row. e.g. 00/00/0000, 00.00 coinciding with Date, Amount. Doing so allowed the file to be imported into Moneydance. That was going to be my next suggestion. : )
One final observation. In Excel for Mac Office 365 there are now TWO csv options when doing a 'save as'.
1. Under 'Common Formats' there is CSV UTF-8 (Comma-delimited) (.csv)
2. Under 'Speciality Formats' there is Comma-separated Values (.csv)
The first is the type that has the bad character that Moneydance can't process. The second is what the whole world considers a 'common' .csv file to be, except Microsoft it seems - saving using this 'speciality' option gives a standard CSV file that Moneydance can read.
Thanks for the additional information.
I was weaned on Windows so this might be a Mac-Excel-specific issue. I haven't seen this particular issue in Excel for Windows but then again I'm still using Excel 2000. Microsoft may have 'improved' upon Excel to where it may now have such an issue. :\