Unable to edit BOM I created 5 mins ago.

Hello, I'm using SW2010x64 SP4.0.  I just created a BOM for an ass'y, saved it as an excel2007, then I hid the BOM (rt clk... Hide Table) and save the ass'y over the existing file.  A co-worker opened the ass'y (onhis computer) and asked why he couldn't click on the BOM.  I opened the ass'y I just saved(on my computer), rt clk,...Show Table and I can't click on it either.

Wazzupwitdat?lol  Components (and subassemblies) in our ass'y are lightweight (I know, I've just been reading the forum and aparrently it causes issues), I don't know if this is relevant to my problem.  I'm new with working with BOM's; been modeling with SW for over a year.

I assume I'm doing something incorrectly, does anyone have any suggestions?

Also, unrelated to this 'not being able to click on my BOM' issue:  Some cells are blank: no ITEM NO, no PART NO, but QTY is there.  Is this an example of issues with lightweight components?  I can't select anything in the BOM to quickly find what component it is, I'll have to go thru the mile-long assembly tree if anyone needs to know exactly what component(s) are coming up blank.

Thanks for taking time to help me out!

G!

SolidworksBill Of Materials
Answers 5
TP
TP 2011-01-26 Best Answer

Is this in a Drawing, Assembly or Part?

AJ
AJ 2011-01-26

Try this...

If you are unable to pick or select a BOM Table in an .sldasm, goto View and untick ‘Hide All Types’. This should allow selection of the BOM Table.

SF
SF 2011-01-26

Thanks for the quick response. I did what you said, and still can't click on the BOM, dragging a selection window around it doesn't work either.  But you were correct, the Hide All Types did have a tick in front of it, when I selected it, the BOM disappeared, I had to Hide it, then Show it to test your solution.

I appreciated your suggestion!

G!

FV
FV 2011-01-26

Hey Paul,

I had this exact problem today...and not sure why it's happening. This happened on a co-workers computer, and the BOM was hidden as well. He was on SW 2011x64SP0.0, and I'm trying to reproduce the problem on my computer now (SW 2011x86SP2.0), and it's working fine....so, I'm not sure what the problem is.

I've dealt with hidden BOM for over a year now, and never had a problem, until now on my co-workers' 64 bit system.

Maybe it has something to do with that. See if the problem persists on 32bit (if you have available).

Cheers

SF
SF 2011-01-27

This is happening in an assembly.  Because this happened on two different computers and I'm new to using/manipulating a BOM I'm assuming it's a setting I'm not familiar with of somewhere. My co-worker who is checking these said it happened to a few (out of about a dozen) assemblies we're working on.  All of the components (about 220)are lightweight (customer's request).  I'm sorry, I don't have SW 32bit.