nope,
this occurs in dwgs which have been worked on with no problem for months
when using multiple xrefs and making various changes in xrefs, this occurs
maybe if i did a purge on an xref, and that purge deleted a block def, then
in the parent dwg, maybe the xref|blockdef became undefined?
Though it doesn't seem to be related...
In other words, maybe I just changed some lines in an xref, then later in
the parent dwgs I get this msg.
I also get a lot of Error on save recommend recover this dwg after doing
anything with an xref...
This isn't every time of course, very intermittent, but it definitely is a
bug in acad 2008 when dealing with xrefs
for example ever since 2007 you occasionally end up with duplicate layer
names in dwgs that use xrefs
of course that's *impossible* right??? but in fact it does happen with some
frequency
So I do claim it's a bug. I wrote a vba just to detect duplcate layer names
and delete the dups because eventually they would end up corrupting the dwgs
to some extent...
2008 appears to be more sensitive to the crap that acad bugs leave in the
dwgs with xrefs and so I get a lot more of those Error on save Recommend
recover dialogs in 08 than I do in 07
wrote in message news:[email protected]...
do you have any .shx files missing?
