Off the top of my head, I’ve no idea. But I’m fairly sure I’ve read of a way to trick xcelsius into talking to excel again. Something to do with renaming the file extension? Can’t remember if it was on this forum or via google.
If I find it again, I’ll post a link, but do some searching…
someone has already put a solution for this, but what I would do to prevent it is the following.
1-save as diferent versions as you progress with your dashboard.
2-before you close your dashboard, an easy way to detect if there is a corruption is looking at the last save file size, its half of what it supposed to be, e.g., if the file was 1203kb, the file would probably have 700kb.
3-if you find this has happend, do not close the file.
4-export the existing excel by selecting Data, export and save it on your c drive.
5-Select Data and this time import the excel file again, it will advise you that all data will be overwritten and previous data will be lost, click ok.
once you have re-imported the file, it should have its original file size.
note when exporting to excel, the excel file is conciderably bigger. for a xlf of 1200kb, the excel is around 5000kb
If you have an XLF with a corrupted data model, you can replace it.
Rename the .XLF file to a .ZIP file
Open the .ZIP with something like WinZip or 7-Zip (the regular Windows function won’t work)
The xldoc file is your data model
Find another copy of your data model (hopefully you have one that has all the same sheets, and is at least reasonably current)
Rename that copy to “xldoc” (no extension)
Overwrite the xldoc in the .ZIP with this xldoc
Close the .ZIP
Rename the .ZIP back to .XLF
When you re-open the XLF, it will use this data model. If you changed any of the sheet names, or are missing any sheets, then components or connections that reference those sheets will need to be remapped. Also hopefully you remember all the changes that need to be made to the data model since you took that backup.
I just had the same thing happen to me. What I usually do is publish the XLF to my dev server once I finish my work and then check the XLF into TFS. This morning when I wen to open the XLF on my local machine (the one I had just worked on and checked into TFS) I got this error. I was able to work the file though by opening the published version from the server. I realize that this isn’t going to work for everyone but for us it saved today.
(BOB member since 2005-03-01)
(BOB member since 2009-08-21)