BOM causing crash

[jethro511]

We just switched to 2005 about a month ago and this issue started this week, so I'm not sure if this is related or not.

I created an assembly drawing in 2004 and it had a BOM in it, everything was fine. I went to update the assembly, opened up the drawing in 2005 (SP 0.1) and it crashes. Thru fustration, I recreated the drawing inserted the BOM, saved & closed it. When I open it up again, it crashes. As long as I don't insert a BOM, its fine.

I then made another small assembly and the outcome is the same. I've reinstalled SWX, contacted my VAR and our IT dept, yet no one has a solution. Anyone out there have a suggestion

Thanks
Jeff

 

[SBaugh]

When you reinstall it did you clean out the registry?

Regards,

Scott Baugh, CSWP
3DVision Technologies

http://www.3dvisiontech.com

http://www.scottjbaugh.com

faq731-376

 

[CorBlimeyLimey]

Do you have another computer running SW? Does it open assembly drawings with BOMs OK?

 

[jethro511]

Yes, reinstalled and cleaned the reg. The other machines can do this fine.

Other machines can open the drawing with the BOM after I created it.

 

[CorBlimeyLimey]

Does this happen with both Excel & SW style BOMs?
If it's just Excel, try repairing your MS Office installation also.
What software package do you use to clean the registry? A manual search will not always find all that needs to be found!!!

 

[jethro511]

I cleaned it the old fashon manual way. I did not know there was a software one. What is a decent regisrty cleaner?

It only happens with the excel BOM. I will pass the MS Office info onto the IT department and get them to repair it and let you know.

 

[CorBlimeyLimey]

Just type registry cleaner in Google then take your pick!

 

[CorBlimeyLimey]

The one I use most is RegCleaner which can be found at

http://www.jv16.org/

They have 30 day trial downloads of various products, so you can choose the one which best suits you.

A word of caution ... use these tools sparingly & wisely, even though they have a built in "restore" function, you can create quite a mess if not careful.

 

[CorBlimeyLimey]

For a free version go to

http://www.webmasterfree.com/regcleaner.html

http://www.worldstart.com/weekly-download/archives/reg-cleaner4.3.htm

http://www.majorgeeks.com/download460.html

 

[jethro511]

So after SWX & MSO was reinstalled, I finally got an answer back from our VAR. It was one part that had a configuration in it that had a space at the end of the name. All the assemblies I was working on/testing with had this part in it. The extra space messed up excel causing the crash. I just found it strange it only happened on my machine. Maybe there was something wrong with my excel too.

I was assured that this fix is going to be implemented in SP1.0 that is to be released before the end of the year.

Lesson learned: Create a brand new assembly, with brand new parts for some tests!

Thanks eveyone
Jeff