Community Tip - You can Bookmark boards, posts or articles that you'd like to access again easily! X
Olaf,
Thanks for providing some insight into why this happens with drawings. We've had to occasionally use the method you describe to clean up dependencies between a drawing and models that have been removed from the drawing's driving assembly model.Sometimes in our case the tie is revealed when a user will try to do a "remove from workspace" on the part(s) removed from the assembly that shouldn't be referenced by anything in the workspace anymore.The action fails because the assembly drawing still has a tie to the component.
Erik
We also use the method described to clear up dependencies from dwgs but have never found what on the dwg stored the dependencies. It very well could be the repeat region for us too, though we only rarely use the finicky “fix index” feature.
However, to avoid this problem I tell users to always have the dwg and the model open simultaneously (especially when replacing components) and make sure to save the dwg before erasing from session. Since I have started doing this, I no longer get ghost objects tied to dwgs.
Although this does not prove this is the solution, it seems to be true and is good enough for me. I would be interested in knowing if anyone else has experience with this and if it helps avoid having ghost objects and other check-in problems?
Lawrence