One way to work around it might be to filter the data that is in the summary, so that, for example, all key values beginning with 0-5, or A-M, appear in one filtered view, and the rest in another.
Then define two project exports from the summary, each using one filter, both exporting on unique key values. As the filters will ensure distinct key values, there's no danger of the exports over-writing each other.
I agree it's odd that Monarch stops to check the row limit for the format like this, but I can see the sense in it, as what would happen if one day you had only one key value and that file contained over 65,000 records? Perhaps it would be better to check the record count for every key value, but that might take a lot of time.
Good luck, and schönes Wochenende...
..thanks, for the workaround suggestion. But this is very strange - to solve the export by creating filters only for exporting the rows.
Perhaps it would be a better if Monarch fails to export (only) this sheet, which is not compliant to the file/format extension...
Schöne Grüße von Ingolstadt nach München !
It does seem to be a bit of a contradiction of sorts, but perhaps Oli is distributing .xls files to those without Excel 2007.
I'd originally thought that Oli could export directly to .xlsx and then open the file with Excel 2007 and save as .xls. But with 400 files to process, even with a macro to handle a batch conversion, at 15 seconds per file he'd probably be looking at well over an hour just for the file conversions. :eek: