No. The design table only uses model document's units. You'll
have to do the unit conversions in Excel formulas if you need to
see or work with other units.
While it is true that dual dimensions cannot be put into a design
table (Chad, that can be set on a document basis). You can use
mixed units in a design table. For example, say you have an inch
model and you want to put some millimeter values into the design
table, simply append mm to the end of the value (20mm) and
SolidWorks will do the conversion for you. If this is not want you
meant, then I apologize.
I would like to have a separate columns for the inch and
metric. I could use the $comment for the column, but I need several
metric columns. Design tables only allow one $comment
column.
I would like to have a separate columns for the inch and metric.
I could use the $comment for the column, but I need several metric
columns. Design tables only allow one $comment column.
You can create your own Configuration Specific Properties and
use them in your Design Table, each with its own column, in place
of the $comment property.
Use the heading $USER_NOTES instead of $COMMENT. $Comment
adds the value to the comment field in each configuration.
$User_Notes just tells it to ignore that column.
I have never had a problem with multiple column headers using
"$COMMENT".
Also, Jason is correect, you should just use "$USER_NOTES". The
difference is that "$COMMENT" can only be used as a column header,
while "$USER_NOTES" can be used as a column header and a row
header.
A little background:
"$COMMENT" came along first, and was always limited as a column
header.
"$USER_NOTES" was introduced in a later version and came with the
ability to be both a column & a row header. Therefore, $COMMENT
has been kept for legacy data.
I find that if you use more than one $COMMENT column, that SW will
assign the value from the Comment field in the Configurations
Property window to all the $COMMENT columns the table. That would
defeat the purpose.
Chad
I think this all depends on what you want to use this for. If you
just want to have the values show up in the design table and no
where else, then you can just type it all in (use formulas as
needed) and it will show up if you insert the design table in the
drawing. You don't need to assign a column variable. Otherwise, if
you want to link to the value so you can apply it to a note, then I
think you're better off using a Custom Configuration Specific
Property with your own title that makes sense to you, such as
"LengthMM" or whatever.
While it is true that dual dimensions cannot be put into a design table (Chad, that can be set on a document basis). You can use mixed units in a design table. For example, say you have an inch model and you want to put some millimeter values into the design table, simply append mm to the end of the value (20mm) and SolidWorks will do the conversion for you. If this is not want you meant, then I apologize.
SA
I have never had a problem with multiple column headers using "$COMMENT".
Also, Jason is correect, you should just use "$USER_NOTES". The difference is that "$COMMENT" can only be used as a column header, while "$USER_NOTES" can be used as a column header and a row header.
A little background:
"$COMMENT" came along first, and was always limited as a column header.
"$USER_NOTES" was introduced in a later version and came with the ability to be both a column & a row header. Therefore, $COMMENT has been kept for legacy data.
I find that if you use more than one $COMMENT column, that SW will assign the value from the Comment field in the Configurations Property window to all the $COMMENT columns the table. That would defeat the purpose.
Chad
I think this all depends on what you want to use this for. If you just want to have the values show up in the design table and no where else, then you can just type it all in (use formulas as needed) and it will show up if you insert the design table in the drawing. You don't need to assign a column variable. Otherwise, if you want to link to the value so you can apply it to a note, then I think you're better off using a Custom Configuration Specific Property with your own title that makes sense to you, such as "LengthMM" or whatever.
We do not use the Comment Field, so I'm not seeing the issue.
Anyway, I'll stick to what I said, use "USER_NOTES" exclusively and you will not run into any problems.