the3rdParty
New Member
- Joined
- Jun 15, 2015
- Messages
- 1
I have a file that links from Excel Mac 2011 to a local filemaker 12 source via ODBC. The link produces a table in excel of some 7000 rows, 50 columns. This data is then summarized via a pivot tables in the same workbook.
The excel file is consistently becoming corrupted. It will work fine for a while, including data refresh, saving, closing & opening. I am always careful to allow plenty of time for both data refreshes and saves. However, after closing the file once or twice it will become damaged and on opening I get a message that "some content is unreadable, do you want to repair". On repairing, the file seems to work OK, and the log file will read:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<recoveryLog xmlns="http://schemas.openxmlformats.org/spreadsheetml/2006/main"><logFileName>Repair Result to data8 07855.xml</logFileName><summary>Errors were detected in file 'Macintosh HD:Users:jw:Desktop:ODBC test:data8.xlsx'</summary><repairedRecords summary="Following is a list of repairs:"><repairedRecord>Repaired Records: Table from /xl/tables/table1.xml (List)</repairedRecord></repairedRecords></recoveryLog>
This doesn't really tell me that much, apart from the fact that Table1 (the table produced by the ODBC import) was damaged.
Further closing and opening of the same file will then always come up with the warning the "some content is unreadable" on opening. If I start from scratch again (new file, new ODBC table) the result repeats itself and the new file will become damaged after a couple of close / opens.
Anyone else experienced this? Any workaround?
The excel file is consistently becoming corrupted. It will work fine for a while, including data refresh, saving, closing & opening. I am always careful to allow plenty of time for both data refreshes and saves. However, after closing the file once or twice it will become damaged and on opening I get a message that "some content is unreadable, do you want to repair". On repairing, the file seems to work OK, and the log file will read:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<recoveryLog xmlns="http://schemas.openxmlformats.org/spreadsheetml/2006/main"><logFileName>Repair Result to data8 07855.xml</logFileName><summary>Errors were detected in file 'Macintosh HD:Users:jw:Desktop:ODBC test:data8.xlsx'</summary><repairedRecords summary="Following is a list of repairs:"><repairedRecord>Repaired Records: Table from /xl/tables/table1.xml (List)</repairedRecord></repairedRecords></recoveryLog>
This doesn't really tell me that much, apart from the fact that Table1 (the table produced by the ODBC import) was damaged.
Further closing and opening of the same file will then always come up with the warning the "some content is unreadable" on opening. If I start from scratch again (new file, new ODBC table) the result repeats itself and the new file will become damaged after a couple of close / opens.
Anyone else experienced this? Any workaround?
