Corrupt BOM

[Anonymous]

Good morning,
I'm using MDT 2009 sp2 on windows xp professional 2002 sp3.

I have an assembly file which is made up of both local and external sub-assemblies.
I start a new file in which I want to make drawings of the assembly with scenes etc.
I catalog in the file, make a new bom and expand it as I like. My problem is when I re-open my new file the bom is corrupt, as in does not remain the same as when I left it, will not collapse or expand as it should etc... making it impossible to balloon my drawings correctly.

I have tried to reproduce the problem with subs within the assembly and cannot. it is isolated to the one assembly file. I have audit set to always, and have tried recover and audit on all files involved.

My goal is to keep file sizes down by not having too many layouts/drawing views in one file, but all drawings driven from the same assembly.

Has anyone had similar issues?

Thank you.

[Anonymous]

Use AMRECOVER on the assembly and all its
external files until no more errors are reported in the text window and
delete all BOMS. Purge all files. Make a  BOM only in the drawing
file. Note that the structure of the databases in all files need to lign up to
get the wanted result in the partlist/balloon option.

style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">

<erich@occimofab.com>
wrote in message
href="news:6070628@discussion.autodesk.com">news:6070628@discussion.autodesk.com...

Good
morning, I'm using MDT 2009 sp2 on windows xp professional 2002 sp3. I have an
assembly file which is made up of both local and external sub-assemblies. I
start a new file in which I want to make drawings of the assembly with scenes
etc. I catalog in the file, make a new bom and expand it as I like. My problem
is when I re-open my new file the bom is corrupt, as in does not remain the
same as when I left it, will not collapse or expand as it should etc... making
it impossible to balloon my drawings correctly. I have tried to reproduce the
problem with subs within the assembly and cannot. it is isolated to the one
assembly file. I have audit set to always, and have tried recover and audit on
all files involved. My goal is to keep file sizes down by not having too many
layouts/drawing views in one file, but all drawings driven from the same
assembly. Has anyone had similar issues? Thank you.