I have never made a template or macros for that matter, but thanks for all
the info. Im sure this will lead me in the right direction to learn more
about doing what i have to do.
Thanks a lot
"BTBeilke" wrote in message
news:429E3C586219484E45E9863B406B6F11@in.WebX.maYIadrTaRb...
> What I have done is create templates for each different type of steel
shape
> that I use (W, S, C, L, etc.). Each template has an embedded spreadsheet
> containing all of the dimensional info for each different size in which
that
> shape is available. When I place a steel member in my assembly, I click
on
> "Create Component", give the new part a name, and select the appropriate
> template. The part is placed in the drawing using the default size
> specified in the table. I simply go into the table and select the size I
> want from a drop-down list and edit the extrusion length. If I want
several
> columns that are all the same part, I just copy the first instance of the
> part. If I want a new part, I create it from a template. Then, you can
> change on part without effecting the others.
>
> I believe this method has several advantages when compared to the built-in
> library shapes or iParts:
>
> 1. Creating the steel members from templates allows them to be adaptive
if
> needed. iParts cannot be adaptive.
> 2. Some of the cross-sections in the library parts are not even
> dimensionally correct (I-beams/S and channels/C).
> 3. If you use the library parts to create a steel part and later decide
you
> want to change the size of that part, you cannot simply select a different
> size from a list. Using templates, you just select the new size and all
of
> your constraints are maintained.
>
> I went as far as to program a macro into my templates that would read the
> extrusion (cut length) of each steel member, convert the length to feet
and
> inches (metric would be much easier), and place the resulting value in a
> custom parameter that I use in my BOMs. However, more recently, I have
read
> on the IV customization board (see Sean Dotson), that having auto-macros
in
> a lot of parts in a large assembly is not a good idea. (Apparently this a
> Microsoft/VBA issue, not a specific Inventor issue.) A workaround was
> offered by an Autodesk employee but was later retracted pending IV8.
>
> I hope this helps.
>
> Blane
>
>