Delfinus25
Board Regular
- Joined
- Feb 27, 2016
- Messages
- 80
My users build product spreadsheets in Excel to track items carried in their area. Columns for Vendor, Product, price, etc. Included in this, they also insert images into a column so they have a visual representation of their selection.
We have an ongoing issue when they open these workbooks that they get an error saying:
"We found a problem with some content in 'Example.xlsx'. Do you want us to try to recover as much as we can? If you trust the source of this workbook, click Yes."
When it tries to recover, we get all the data back EXCEPT pictures. The repair log shows the following:
I think I finally nailed down the CAUSE of the error:
If there is a single image that is not set with the property to "Move and Size with Cells," and then the data is filtered and saved that way, we get this error when we open the book the next time.
(Note: I KNOW this causes the error, because I can easily duplicate it. I don't know if it's the ONLY thing that causes the error, as I just started tracking the issue.)
At this point, I have obviously instructed my users to make sure ALL pictures are set accordingly, and NOT to save filtered data to be safe.
The problem we have is that sometimes during additions to the workbook, something will cause a crash, AutoRecovery will try to help and will save the file. That saves the workbook in this state, and so we get the error. (We also have the issue sometimes that users DON'T FOLLOW DIRECTIONS <shocking>, but that's a different issue....)
Most of the time, we have been able to restore a previous version of the file and work from that, although we lose any work done since that point. And the few that couldn't be restored, we at least had the SMALL benefit that the images were still stored inside of the file - so we could retrieve them, we just had to build the book again.
What I want to know if there is a way to CORRECT this error and make the workbook usable again, without losing the time that was spent to update the file.</shocking>
We have an ongoing issue when they open these workbooks that they get an error saying:
"We found a problem with some content in 'Example.xlsx'. Do you want us to try to recover as much as we can? If you trust the source of this workbook, click Yes."
When it tries to recover, we get all the data back EXCEPT pictures. The repair log shows the following:
Rich (BB code):
{?xml version="1.0" encoding="UTF-8" standalone="true"?}
-{recoveryLog xmlns="http://schemas.openxmlformats.org/spreadsheetml/2006/main"}
{logFileName}error083240_01.xml{/logFileName}
{summary}Errors were detected in file 'G:\FilePath.xlsx'{/summary}
{repairedRecords summary="Following is a list of repairs:"}
{repairedRecord}Repaired Records: Drawing from /xl/drawings/drawing1.xml part (Drawing shape)
{/repairedRecord}
{/repairedRecords}
{/recoveryLog}
I think I finally nailed down the CAUSE of the error:
If there is a single image that is not set with the property to "Move and Size with Cells," and then the data is filtered and saved that way, we get this error when we open the book the next time.
(Note: I KNOW this causes the error, because I can easily duplicate it. I don't know if it's the ONLY thing that causes the error, as I just started tracking the issue.)
At this point, I have obviously instructed my users to make sure ALL pictures are set accordingly, and NOT to save filtered data to be safe.
The problem we have is that sometimes during additions to the workbook, something will cause a crash, AutoRecovery will try to help and will save the file. That saves the workbook in this state, and so we get the error. (We also have the issue sometimes that users DON'T FOLLOW DIRECTIONS <shocking>, but that's a different issue....)
Most of the time, we have been able to restore a previous version of the file and work from that, although we lose any work done since that point. And the few that couldn't be restored, we at least had the SMALL benefit that the images were still stored inside of the file - so we could retrieve them, we just had to build the book again.
What I want to know if there is a way to CORRECT this error and make the workbook usable again, without losing the time that was spent to update the file.</shocking>