Yeah but it'll probably work fine with that.

2011 is the Mac version (which is what I'm using).

It also annoys me that there is no XML import facilities in this 2011 Mac version like there is in the 2010 Windows version.

I know I could just install 2010 in the Windows VM I have installed but that is a bit of a fail really, I want it to work natively on my Mac! :lol:

:| Never seen this with Office 2010

OK done a bit more investigation, it seems the cause is down to one particular CSV file (the other one is fine).

Is there anything in a CSV file that can cause Excel to complain?

Excel is literally the only program on my new MacBook Pro that ever crashes or behaves strangely.

Maybe I should have bought that iWork package or whatever it's called.

I deal with loads of problems with office for mac. 99% of the time the solution is to open it in windows.

Quick update - I created a brand new empty .xlsx file and imported the two CSV files into two separate sheets. Same problem as above, so it must be something to do with one or both of these CSV files?

Really weird that it does it in this current .xlsx format but not the older .xls?

I have a file that I have created in Excel 2011 (Mac), which is a .xlsx file. This file has a couple of data sources - CSV files - which it pulls in whenever the Excel file is opened.

For some reason now, every time I open the Excel file it complains that it needs to be repaired, and although it offers to save a log file of what it's done, it doesn't provide any useful information about what it has repaired.

If I save this file as an old .xls file, it opens up fine. If I then save this file as a .xlsx file again, I get the same problem.

Everything seems to be working as it should, and this problem only affects this file.

Any ideas?