I've run into this bug too and it was mystifying and (iirc) not overridden by manually loading the file using the Text Import wizard. But this... "If the file'

I've run into this bug too and it was mystifying and (iirc) not overridden by manually loading the file using the Text Import wizard. But this... "If the file's suffix is .csv, then maybe you should just treat it as a CSV file" doesn't make me any happier, because there are a lot of slight variations on CSV files or a lot of different ways you might want to load a CSV file (perhaps you'd like to specify the character set, or set columns to be text or date format, or not have leading zeroes stripped or numbers in brackets turned into negative values), and if I absentmindedly name them .csv then again I can't use the full loader, because Excel knows best. And if you want to read a CSV file with a VB macro it's even worse, because you can specify all the parameters but it just silently overrides them all with the CSV defaults just because the file extension is CSV. Hours of debugging spent on that...