Thanks Tim,
I trust the Swamp crew but cleaning up the file to be comfortable with my work not raising a red flag over posting client files may remove the cause of the problem that generated it in the first place.
I think some of the bugs I was having are errors generated in the drawing database.
Audits and purges seemed to have cleared them up.
Most of it seems to stem from the order I process the client files for background use internally.
Quite a few of the routines I run are meant to affect items directly in the drawing.
When they are aec based in XREF's it gets a bit funky for the routines to have any effect.
I was just thinking out of the box to consider a routine that generates an scr file of the XREF's in the drawing.
ExportToAutoCAD and bind the references with a prefix on the filename.
Write that filename to the scr file, then close the file I was in, and open the file that was created to explode the blocks named from the XREF's. Audit, purge, then run my routines on the files.
I'm likely reaching pretty far out to beleive it would work in most cases without writing a fairly involved arx application though.
I'm going to look through the ExportToAutoCAD feature and see if there is an explode blocks option.
