Recent content by SuperMPG

Yes, it seems that the parts themselves need to be opened with write access as well as the assy and sub-assys. I was leaving the parts as read-only and opening the assys with write access but that wasn't working. Thanks for the help, everyone. Brian-

@CorBlimeyLimey: That would be a rather expensive fix, considering all seats would need to be upgraded from the current SW2007. @ctopher: I tried that, but when I open the Component Properties flyout it already lists the correct config name, so there's nothing to change it to. The parts...

I renamed configurations in several parts and now whenever I open an assembly that refers to these part, I get a warning message complaining that it can't find the configs with the previous names so it will just use the defaults. Does anyone know how I can tell SW to stop bugging me and just...

How does dbWorks compare with PDMWorks?

Ouch! That would be totally out of the question.. we have thousands of parts and assemblies, some of which have 8 or 9 revisions. If what you say is true, I'll definitely need to come up with a plan B. However, I can see (by doing a little file system snooping) that PDM stores each revision...

We have discrete files for revision history, but when we slide into the PDMWE domain, we'll need to convert that scheme to the internal revision history in the database. NOW-- part_A.sldprt part_B.sldprt part_C.sldprt part_D.sldprt IN PDMWE-- part.sldprt with rev history stored internally...

I guess it's configs that need to be avoided!! :D B-

The idea that using DTs may be necessary to avoid data corruption in configurations seems deeply troubling to me. Perhaps a red flag for avoiding 2009 until further SPs... Brian-

Thanks to all who posted suggestions. After looking at the options I can see that the best solution would be to open all referenced files as read only by default. This would essentially nullify the problem - as long as I can get my engineers to agree :D Brian-

That was WAAAAY too easy! I was expecting something far less obvious! Thanks for pointing me in the right direction. Brian-

Hard to explain this properly in the subject line.. We often find that we are needing to insert a complex assembly of a product into another assembly (such as fixturing) in order to ensure that it will fit and connect correctly. The problem is that doing this causes the product assembly, all...