Oh, I'm setting myself up for a fall here...
What happens if you first save the file as a conventional xls (or xlsx) file (seeing as you presumably won't be using the macros in the export)?
Am hoping [but not expecting] to avoid that.
Already have to do a runaround because someone *has* to be able to do something in Excel that cannot be done the way they want to do it in FM.
So I'm using vba code to turn the relevant sheet into a table on another sheet.
Saving that file to yet another file [xlsx] is a further complication for the end user.
But perhaps a complication you can mitigate by using an Excel Macro to auomate that process.
Another thought: Can the file be set up as an ODBC source for FileMaker?
Or, what is the runaround that can't be done in FM?