IF its any consolation, upgrading from 3.0 to 4.0 was pretty painless. We aren't using virtual parts much so I can't vouch for the fix.
My understanding is some issues with virtual components are known in SW and have been fixed in SP5.
check out Solution Id: S-026503 in the knowledge base.
yes, we are having your problem, too. We have an assmebly with virtual parts. Check in and out the assembly then modify the assembly. check in and out and now when you are clicking on a virtual part, SolidWorks freezes.
We have installed SW SP5.0 and PDMWE SP4.0 and the problem isn't away.
I have a workaround:
Check out the assembly and go PDMWE --> offline. Now you can work with your assembly. When you are finish, go PDMWE --> online and check in your assembly.
Sorry, for my bad english and I hope you understand it.
Buss SMS Canzler GmbH
Is this still an issue in SW2010 and PDMWE 2010???
I recently talked about this on the CAPUniversity blog, which has a posting to a video: http://blog.capinc.com/2010/08/virtual-components-in-the-land-of-pdm/
Here is the summary:
In the land of SolidWorks Assemblies exists a funny creature called the “Virtual Component”. Virtual components are typically used in top-down design when you need to create a new part in the context of an existing assembly. During the conceptual design process, when you frequently experiment with and make changes to the assembly structure and components, using virtual components has several advantages over the bottom-up design method as explained by the SolidWorks help system online:
- You can rename these virtual components in the FeatureManager design tree, avoiding the need to open, save as a copy, and use the Replace Componentscommand.
- You can make one instance of a virtual component independent of other instances in a single step.
- The folder where you store the assembly is not cluttered with unused part and assembly files resulting from iterations of component designs.
Workgroup PDM will certainly let you add an assembly with a Virtual Part, but it has no means for really tracking it beyond the where used report. There is a setting to turn this on in the User Options, but selecting this option has significant performance impact. and since a virtual part is usually only used relative to one design, this setting may have a low return on investment.
Enterprise PDM actually handles these quite nicely and if a virtual component is being used, it is shown in the check in dialog box in reports as well as the BOM tab, which is really where you want it displayed.
This is relatively new stuff for PDM to track and I think you need EPDM 2009 or higher for this to work...
I don't mean to hyjack the topic, but in this mothodology, are the virtual parts replaced with real parts once the design is finalized? I find it difficult to see the benifit of having parts that only exist in the parent assembly, cannot be reused elsewhere, and provide a method to get around best practices.
usually the virtual parts would get saved to an external file once they (or the assembly) is finalized. though there can be exceptions for things that don't get part numbers or whose geometry are intrinsically not re-usable. for us that covers part makings, epoxies, and wires that get bent to custom shapes for that assembly.