Thanks for the help, that Macro looks neat! I closed the EG file and reran it and the problem vanished, so although I've no idea what the problem was, it seems to be sorted now. I was importing into Excel using a Data Connection that loaded the data into the Data Model, which is nothing like any of the other methods and should be far more immune to artifacts like this, as I said in my first post the issue appears to have been with EG as I could test the .csv files and see the blank row was there. Excel was doing as I'd have expected. It just doesn't have much control over the import, it would be helpful if there were a few more options for tidying up the files as they come in, because it's not immediately obvious how to edit the data once it's into the Data Model, at least on my version of Excel. The most frustrating thing about this sort of thing is that I have PowerBI Pro, which is by far the best solution for what I'm doing and can correct dodgy input data. But I have to deliver in Excel. Oh well, it's sorted now. Thanks again!
... View more