S
Steve
morning all.
I've been experiencing what strikes me as a problem since we bought office
2007, just over two years ago now, and now a colleague just experienced the
same problem.
Occasionally we'll receive an error message stating that some equation, or
record, etc... was damaged and needed to be removed from the record. The
worksheet/book gets repaired, and we must save the repair.
Typically it's at least two worksheets in the "xml.part" of the file.
"sheetA", and "calcChain."
For me, I just go into the developer tab, open the VBE, locate the actual
worksheet and then check that worksheet to ensure that none of my information
is lost-- specifically because it says that it removed some aspect of the
record-- and if all looks well, I move on. But now that my colleague has
experienced it on the first time she's opened this particular workbook that
was last worked on by another colleague, I think that we need to know more
about this, so we can avoid its occurrence in the future.
Does anyone know what, why, and how to avoid this type of error in the
future?
(While I find it irksome, I can deal with it rather easily. When a far less
experienced tech deals with it, it's time to resolve it.)
Thank you.
I've been experiencing what strikes me as a problem since we bought office
2007, just over two years ago now, and now a colleague just experienced the
same problem.
Occasionally we'll receive an error message stating that some equation, or
record, etc... was damaged and needed to be removed from the record. The
worksheet/book gets repaired, and we must save the repair.
Typically it's at least two worksheets in the "xml.part" of the file.
"sheetA", and "calcChain."
For me, I just go into the developer tab, open the VBE, locate the actual
worksheet and then check that worksheet to ensure that none of my information
is lost-- specifically because it says that it removed some aspect of the
record-- and if all looks well, I move on. But now that my colleague has
experienced it on the first time she's opened this particular workbook that
was last worked on by another colleague, I think that we need to know more
about this, so we can avoid its occurrence in the future.
Does anyone know what, why, and how to avoid this type of error in the
future?
(While I find it irksome, I can deal with it rather easily. When a far less
experienced tech deals with it, it's time to resolve it.)
Thank you.