The larger the iParts table the slower the performance. This is due to the
number of nodes generated in the browser. Once you get above 1000 nodes the
browser will not display any of them. There has been some thought that if
your iParts are over 1000 nodes (not rows) that they may be faster than
those with 999 nodes.
That's why you'll see UNF and UNC split in many of the iPart collections.
--
Sean Dotson, PE
http://www.sdotson.com
Check the Inventor FAQ for most common questions
www.sdotson.com/faq.html
----------------------------------------------------------------------------
------
"AnthonyFettig"
wrote in message
news:34CC0490042ADB1D35713144ADD46150@in.WebX.maYIadrTaRb...
> Is there a significant performance drop with larger iPart tables?
>
> For example, when setting up a cap screw iPartfactory, I would prefer to
> have UNC and UNF together in one file so if I decide to change pitch, I
> don't lose constraints. This would double the size of the table, how much
> slower would it be?
>
> Anthony.
>
>
>