Add to Technorati Favorites

Subscribe by Email

Your email:

Browse By tag

Alignex Mechanical Engineering & Manufacturing Blog

Current Articles | RSS Feed RSS Feed

Technical Alert: SolidWorks 2012 Toolbox

  
  

SWtoolboxWe would like to bring your attention to two problems with SolidWorks 2012 SP0.0 Toolbox. These issues can potentially cause a major disruption during the upgrade process from a previous major version of SolidWorks toolbox. The issues are explained below.

The development team at SolidWorks HQ is currently testing and developing possible solutions to the toolbox issues. Both issues are slated for correction in 2012 SP1.0 which is currently targeted for late November.

Please contact the Alignex Technical Support Team at
(866) 378-6829 Ext. 6 or email support@alignex.com if you have any questions or need any support in regards to these issues. 


SPR 627126 (Toolbox data upgraded on an operating system that uses commas as the decimal symbol will result in unusable Toolbox parts.)

KB Solution: S-056855

If the operating system decimal symbol for the computer performing a Toolbox upgrade is a comma instead of a period, then during the Toolbox upgrade the decimal symbols are removed from the numerical data that drives the creation of Toolbox part geometry.  For example, the number 1,75mm would become 175mm due to this issue.

This problem is evident when inserting new fastener instances into an assembly OR when editing the definition of an existing instance.  During either of those action the parameter values for the fastener presented in the PropertyManager will be missing the decimals.  In most cases this would make the values presented unacceptable for the fastener creation.  Proceeding to complete the component insertion or edit definition on existing instance would result in rebuild errors or unexpected geometry results.

For Toolbox installations already impacted by this issue there is not an immediately workaround with SP0 that is available.

If you use Toolbox, use commas for the decimal symbol, and have not yet upgraded to 2012 SP0.0; then it is recommended that you do not upgrade to 2012 until a solution for this problem is available.

The issue will be corrected for 2012 SP1.0 which is currently targeted for late November.  The SP1.0 solution will prevent the problem for customers that have not yet upgraded and will also correct the issue for customers who have already upgraded to SP0.0. A short-term fix is being pursued to correct SP0.0 installations impacted by this issue.


SPR 627178 (Toolbox customized part numbers and descriptions are no longer displayed after upgrading to SolidWorks 2012.)

KB Solution: S-056856

When adding custom part numbers or descriptions to Toolbox components in SolidWorks 2010 or 2011, then upon upgrading to SolidWorks 2012 SP0.0, the part number and description information is no longer accessible via SolidWorks user interfaces and will appear missing.

The problem will be evident when inserting a new instance of a Toolbox part into an assembly OR if editing he Toolbox definition of an existing component instance already in the assembly.  During either of those actions the upper area of the PropertyManager will show an empty "Part Numbers" list field even if part numbers/descriptions had been assigned to that component in past versions of SolidWorks.  Completing those actions will result in the part number and description being removed from the properties for that Toolbox component size.

The part number and description information assigned in a previous version is still present in the file, but just not accessible.

If you used your Toolbox dataset previously with SolidWorks 2010 or 2011, assigned part numbers or descriptions in 2010 or 2011, and have not yet upgraded to 2012 SP0.0; then it is recommended that you do not upgrade to 2012 until a solution for this problem is available.

The issue will be corrected for 2012 SP1.0 which is currently targeted for late November.  The SP1.0 solution will prevent the problem for customers that have not yet upgraded and will also correct the issue for customers who have already upgraded to SP0.0. A short-term fix is being pursued to correct SP0.0 installations impacted by this issue.


Comments

Currently, there are no comments. Be the first to post one!
Post Comment
Name
 *
Email
 *
Website (optional)
Comment
 *

Allowed tags: <a> link, <b> bold, <i> italics