Are you opeing in the same version of ID? Has it always been in this version?
No, I'm opening it in CS6 and the last version was in CS6, but the version before that was probably in CS5.
1 person found this helpful
There are enough reports of problems with legacy files opened directly in newer versions since the release of CS5 that I now as a matter of course suggest you never do it, but instead export from the original version to .inx or .idml (depending on how old the file is) and open that for conversion. Many of the mysterious problems that get reported, like sudden failures after weeks or months of working with a file, seem to have as at least one possible cause the direct converison of a legacy file.
I'm not saying that's what happened -- and constant "recycling" of files by doing a Save As and deleting old stuff, then adding new, is another path to file corruption -- but since you seem to be at the point where you are starting again, I would advise expprting your CS5 version to .idml and work from that (see Remove minor corruption by exporting). You should also set up a template for this job that has all of the styles and so forth along with the things that don't change, if that's at all possible with a calendar, and use that to start each new edition.
Thanks, Peter. I imagine you are correct. This is a big file with a very complex table, so it's hard to imagine a way to set up a template that wouldn't involve a huge amount of reformatting each time, but I'll try exporting to IDML next time before I start making revisions.