Virtual Component LIbrary

[#1]

The ability of creating a virtual component library so that I can quickly add frequently used virtual components to my assembly already completed with the desired iProperty information

[#2]

I do love the idea of a quick access library, but did you know you can copy and paste virtual components from other assemblies. I recommend creating an empty assembly with a library of your virtual components.

[#3]

Did you know this can be done using ilogic and a excel spread sheet?

I have over 50 virtual components in my excel now that is ran with ilogic.

If you would like information on how to do this drop me an email.

[#4]

iLogic and Excel is an excellent idea, I will try that out

[#5]

I should have mentioned this first. FYI: I am currently not recommending Virtual Components to a client of mine because iProperties are only pulled from the first assembly used into a Vault "Item". If someone uses the same virtual component in a different assembly then changes the iProps they will not be updated on the Vault "Item". Instead I have them insert and ground an empty part.

However your ilogicspreadsheet idea sounds interesting jletcher, I will consider that.

[#6]

Workarounds? Fine, but there's still a need for a standard content library managed centrally, not this 'load up a template file' business.

[#7]

I have always used a "dummy part" Fill the I-properties in and leave the part blank (no model). This way you can add the part to the library and reuse it in as many places as you like.

Go Old school, long before the marketing driven software was conceived.