AnsweredAssumed Answered

ToolBox assimilating bad configurations from assemblies

Question asked by Tim Dexter on Jul 29, 2015
Latest reply on Dec 3, 2015 by Tim Dexter

Like • Show 0 Likes0
Comment • 4

Background: ToolBox is under the control of ePDM, 2015 SP03 for both.

I have learned that an assembly can "force feed" configurations of fasteners into the ToolBox if it cannot find them. I also understand that this is a "safety" measure and is happening by design. However, this is causing real havoc for us.

We've made changes to the ToolBox but they are getting overridden by this process. Does anyone know of a way to keep assemblies from adding back to the ToolBox? I would rather the fasteners error-out and require the Engineer to correct them than to let them into the ToolBox.

-Tim

No one else has this question

Outcomes

Tim Dexter Jul 29, 2015 5:27 PM

Perhaps there's a method to remove all the ToolBox items from existing assemblies using "Update File References"? We've already accepted the fact that we have to swap fasteners in existing assemblies, so removing them outright is not much of a stretch.

Has anyone else been in this position before?

-Tim

Actions

Tim Dexter Aug 3, 2015 11:33 AM

Between my VAR and copious amounts of caffeine, I have formulated this plan:

1) After hours, with all assemblies checked in, and logged in as admin...

2) Remove the ToolBox flags from the current old ToolBox.

3) Update all assemblies.

a) Check out the assemblies, have Task Manager open, save, and close each one.

4) Rename the old ToolBox to ToolBox_x.

5) Copy, paste the new ToolBox into the same location as the old ToolBox.

a) Using the same location to avoid re-mapping everyone.

6) Check in all the assemblies. Done.

My hope is that the old ToolBox items will now be regular SolidWorks part files and no longer be assimilated into the new ToolBox going forward. I understand that all the assemblies will have bad fasteners (technically speaking, they won't match the current ToolBox standard), but when the assembly needs to be changed for some other reason, the fasteners will be changed as well.

I'd like to hear any feedback on this idea before I run with it.

-Tim

Actions

Joe Vinciguerra Aug 10, 2015 11:48 AM

Short answer is that there is no fix. This has been one of many issues with Toolbox since at least 2008. After 5 years of trying to get Toolbox to function correctly (including working closely with our VAR and the folks at SolidWorks, staying current with versions, and countless man hours of trying different recommended "solutions" and redoing work when Toolbox messes up an assembly) we finally did what many other users recommend in the forums and created our own Toolbox.

Our approach: We saved copies of the toolbox hardware files we use into our SW Design Library on a shared server location (first generating all configurations, exporting/re-importing database into excel for custom PNs and descriptions, turning off the Toolbox property flag). It works flawlessly, way better than the SW Toolbox. Still auto-snaps mates, and only loss in functionality is the drag-able arrow to change length. Legacy designs can be quickly updated by using Replace.

Actions

Tim Dexter @ Joe Vinciguerra on Dec 3, 2015 11:38 AM

Joe,

Sorry for the delayed response. I've done some testing in a test vault and so far everything is working well. The next step is applying this method to the production vault. I will respond back with the results.

-Tim

Actions

4 Replies

Tim Dexter Jul 29, 2015 5:27 PM
Mark Correct
Correct Answer
Perhaps there's a method to remove all the ToolBox items from existing assemblies using "Update File References"? We've already accepted the fact that we have to swap fasteners in existing assemblies, so removing them outright is not much of a stretch.

Has anyone else been in this position before?

-Tim
Like • Show 0 Likes0
Actions
Tim Dexter Aug 3, 2015 11:33 AM
Mark Correct
Correct Answer
Between my VAR and copious amounts of caffeine, I have formulated this plan:
1) After hours, with all assemblies checked in, and logged in as admin...
2) Remove the ToolBox flags from the current old ToolBox.
3) Update all assemblies.
a) Check out the assemblies, have Task Manager open, save, and close each one.
4) Rename the old ToolBox to ToolBox_x.
5) Copy, paste the new ToolBox into the same location as the old ToolBox.
a) Using the same location to avoid re-mapping everyone.
6) Check in all the assemblies. Done.

My hope is that the old ToolBox items will now be regular SolidWorks part files and no longer be assimilated into the new ToolBox going forward. I understand that all the assemblies will have bad fasteners (technically speaking, they won't match the current ToolBox standard), but when the assembly needs to be changed for some other reason, the fasteners will be changed as well.

I'd like to hear any feedback on this idea before I run with it.

-Tim
Like • Show 0 Likes0
Actions
Joe Vinciguerra Aug 10, 2015 11:48 AM
Mark Correct
Correct Answer
Short answer is that there is no fix. This has been one of many issues with Toolbox since at least 2008. After 5 years of trying to get Toolbox to function correctly (including working closely with our VAR and the folks at SolidWorks, staying current with versions, and countless man hours of trying different recommended "solutions" and redoing work when Toolbox messes up an assembly) we finally did what many other users recommend in the forums and created our own Toolbox.

Our approach: We saved copies of the toolbox hardware files we use into our SW Design Library on a shared server location (first generating all configurations, exporting/re-importing database into excel for custom PNs and descriptions, turning off the Toolbox property flag). It works flawlessly, way better than the SW Toolbox. Still auto-snaps mates, and only loss in functionality is the drag-able arrow to change length. Legacy designs can be quickly updated by using Replace.
Like • Show 0 Likes0
Actions
- Tim Dexter @ Joe Vinciguerra on Dec 3, 2015 11:38 AM
  Mark Correct
  Correct Answer
  Joe,
  Sorry for the delayed response. I've done some testing in a test vault and so far everything is working well. The next step is applying this method to the production vault. I will respond back with the results.
  -Tim
  Like • Show 0 Likes0
  Actions

ToolBox assimilating bad configurations from assemblies

Outcomes

Related Content

Recommended Content