Breaking link to toolbox parts or better way to manage them?

[maxh3]

When I use the toolbox to create a fastener, I'll "save as" and check "copy", then insert that copy in my assembly. I've been doing this because I thought it would break the link to the toolbox part but it seems like it doesn't.

The reason I wanted to break the link is recently when I migrated to a new computer with a fresh installation of solidworks, whenever I'd open an assembly with parts created from the toolbox, they wouldn't be found and I'd have to re-create them.

Clearly there's gotta be a better way to manage toolbox parts. What would you suggest?

 

[maxh3]

This is getting really frustrating. Every time I close then open an assembly with fasteners that I've done this with, the fasteners have been replaced with the toolbox part file, and the BOM on my drawing shows the wrong part number and a blank description!

 

[CorBlimeyLimey]

See if this helps;
thread559-297460

 

[maxh3]

Thanks, I went ahead this time and edited the toolbox configuration to display my part number and description. I was hoping for a little discussion on how other people/businesses use toolbox parts. My worry is that if I pack and go an assembly with them, then someone on another computer opens the assembly the fasteners won't show up. Or next time I migrate to another computer/fresh solidworks installation, they won't show up.

 

[hititfaster]

I'm very interested in this subject. I work for a bureau, and on completion we deliver EVERYTHING relating to a project (SW parts, assemblies, drawings plus pdf's and sometimes dxf's of drawings as well, depending on client needs!).

Our biggest client has a lot of fasteners (generated in the past by someone else) which are table driven and have part numbers attached to them so generally if I want one, I pinch it from the previous project, save in the current folder and pick the config of it I want. Spiffing.

Trouble starts when I want a 'one-off' or something they don't have drawn - I would like to be able to use the toolbox but I don't trust the generated parts to 'travel' as I've been told there have been issues with them in the past.

If anyone can tell me what the best/correct way to deal with fasteners is, I would be very grateful!

 

[pdelnet]

We use toolbox without many issues, the parts are created by tool box but you need to configure the directory you store the parts in for every job.
The perviously created parts can also be named the way you like them but you need to add the by clicking on the favorites button, the star with the green plus in it - see attached files.

This will keep a record of all the tool box parts in your working directory and keep a record of what you have done in the actual toolbox history.

You just need to remember that for each new job you have to go into the the tool box coniguration and reset the working directory.

SW 2011 SP 3.0 x64
16 Meg, Quadro 4000
DUAL DISPLAY
Windows 7 PRO x64

 

[pdelnet]

Sorry only 1 file attached here is the other

SW 2011 SP 3.0 x64
16 Meg, Quadro 4000
DUAL DISPLAY
Windows 7 PRO x64

 

[CorBlimeyLimey]

Fasteners could be created as Virtual Components in the top level assy and sub-assys. Separate fastener files and folders would be eliminated.

 

[hititfaster]

CBL - That sounds attractive; I'll look into it!

 

[maxh3]

This issue is still leading to premature hair loss for me! I checked out that other thread and went to

system options > Hole Wizard/Toolbox > Make this folder the default location for Toolbox components

and turned that off.

Then it seemed like things were going to work, but I opened an old assembly and its drawing with BOM, replaced two of the toolbox components with my saved elsewhere components, went back to the drawing, rebuilt, and the BOM is not updating. Furthermore, when I expand the tree at the left for any of the drawing views and expand the assembly tree, the toolbox components are still showed there! Even though I can switch to the assembly file and in the tree the new components are there!

I really just want to manage our part files the best way. In quickbooks we're assigning a company part number to each part we use in an assembly, and I want to have a part file named with that part number used in each assembly, including hardware. What's the best way?

 

[jassco]

Hi, maxh3:

There is really no need to break the link to Toolbox.

If you set (configure) your Toolbox properly at a network folder where every user can share, you should be able to open any assemblies that reference your Toolbox with any SW work stations.

SW Toolbox does have its issue due to how it manages its security. If fastners are critical to business of your company, you may want to consider assign individual part no. and file for each and every toolbox item. Of course, I assume that you have a PDM or PLM in place.

Good luck!

Alex

 

[hititfaster]

That's fine as long as you don't want to send all files to a client, for example, as I need to at the end of every project!

I advise going down the 'make virtual' route. I've been using it since CBL gave me a nudge in that direction (read higher up thread) to fine effect. All created components stored within the assembly and you wave goodbye to link issues. Simples.

 

[jassco]

Hi,

If you send all 3D math data to your client, you send whatever your client asked for, or whatever you agree to send. You have full control.

Virtual parts in assemblies are more computer resource intensive.

Best regards,

Alex

 

[maxh3]

I have the perfect use for converting a toolbox file into a virtual component of an assembly, but it's not working. There's this swivel mount we buy from mcmaster which I have modeled as an assembly, and I created a nut from the toolbox, saved a copy of it elsewhere, inserted this copy into the assembly, and right clicked it in the tree to save it as a virtual component, just like I did with the other components, but this one doesn't have the option; it's just not there! What's the deal!?

 

[jassco]

Hi, maxh3:

Please search the following keywords in your SW help menu:

"Search Routine for Referenced Documents"

If you fully understand this, you will know why you have this issue.

Best regards,

Alex