The performance issue has been essentially eliminated in R8. In pre R8
releases iParts would create all of the "nodes' in the browser. This is
what took the most time. In R8 the nodes are not created in the browser and
therefore the performance should be greatly increased.
A it would be simple enough to put them all in one table and try it out. If
it's too slow then just break them into 2 iParts.
AFAIK you cannot have 2 tables in one iPart.
--
Sean Dotson, PE
Autodesk Inventor Certified Expert
http://www.sdotson.com
Check the Inventor FAQ for most common questions
www.sdotson.com/faq.html
-----------------------------------------------------------------------
"Duncan Anderson" wrote
in message news:4044ae5a_3@newsprd01...
> I think it is the performance issue that kicks in big time.
>
> I think there are some iParts on Charles' site where this has been done to
> improve performance.
>
> Charles, are you out there ?
>
> Duncan
>
>
> "Rory" wrote in message
> news:4044acf8_2@newsprd01...
> > Why not have the first key field set to either "Imperial" or "metric"
for
> > each part and use a great big table..
> >
> > Then when you insert the iPart the first thing you get to choose from is
> > metric or imperial.
> >
> > Performance might be an issue but it would give you a nice neat
solution.
> >
> > Regards
> >
> > Rory
> >
> >
> >
> >
> > "Duncan Anderson"
wrote
> > in message news:4044a791$1_3@newsprd01...
> > > I think I've read somewhere about having two tables for an iPart, one
for
> > > imperial and one for metric.
> > >
> > > But how ?
> > >
> > > I don't think I've read anything about do this and getting it to work.
> > After
> > > today's experience of non-appearing bitmap for custom threads.
> > >
> > > Any help welcome.
> > >
> > > yours
> > > Duncan Anderson
> > >
> > >
> >
> >
>
>
