Project Gone (Going) Bad

[Anonymous]

I know this is a little vague but...
Recently we have started experiencing more frequent crashes on one particular Teamwork project. Unfortunately I don't have any idea what has happened to the file that may be causing this instability.
Are there any measures (other than saving often) I can take to re-stabilize the file? For example, in AutoCAD, if I suspected some file corruption, I would wblock the whole file to a new file. Similarly in MS Word I would copy-paste all the text to a new file. With ArchiCAD this is not as easy with all the different sections, details etc. I was hoping there were some basic steps I could take to verify and possible restore the integrity of the file's database.

Thanks in advance.

[Anonymous]

You could try a "Save as" and save out a pln (solo project). Then open the solo project and reshare (you have to move or rename the original teamwork file to share a new one using the same name to keep the links).

Not sure if this will work but it is a process that has helped us in the past.

[Anonymous]

We've expericced the same problem on at least one teamwork file as well. Even after saving as a pln and re-sharing, the same problems occurred. File size did not appear to be the problem, since the problem file was about 1/3 the sizze of a larger job I've been working on for months now without problem <knock, knock on wood...>

My own suspicion is a corrupt library part, but we didn't have time to mess with it... If GS has any ideas what the problem is from reading this forum, any info would be appreciated.

The team split the file into 3 files - one for the plans, one for the elevations, and one for the details (none of the elevs or details needed to remain linked, as the modelling is remaining unchanged this late in the game). One week later, no problems have returned...

Wes