LOST MARKER 1

[designmr]

Thank you in advance.

Not sure if this is the proper way to address this. Don't know if this is a MARKER??? issue, or WHAT it would be called in Solidworks.

I am opening up files and seems 90% of my work is all of a sudden incorrect. It is like Solidworks is pulling files in most of my assembly from the WRONG directories.

Is there a way to remedy this? Maybe my cache needs to be cleaned up or something. I wasn't having a problem before, but ALL of a sudden. Not sure if there is a setting that CLEARS cache EVERY TIME you start Solidworks.

I am working off a Solidworks Workgroup PDM vault, plus my personal Drive, NOW, the Admin has created ANOTHER Vault. Seems 3 different Vaults to work with.

The Administrator very much enjoys us to PACK AND GO assemblies when we need to make a new version or update, then save the new version in a NEW folder. To me, this seems it would disconnect the assemblies. Rather I would feel configurations is the way to go. NOT sure if all this PACK AND GO is my problem.

HELP!!!

 

[drawoh]

designmr,

The best way to create a new assembly based on the old one is to save-as the top assembly, only. Then, you save-as the parts you want changed. The stuff you don't want to change remains copied from the vault. Your final system will call up the existing parts from your warehouse, which is exactly what your manufacturing wants.

If you have in-context stuff attached to the assembly that must remain in-context, it must be saved-as at at the same time as your assembly. Parts in-context to more than one assembly either are impossible or are a horrible mess either in SolidWorks, or out in the Real World.

--
JHG

 

[FACS]

If you are not getting the same parts or assemblies as you expect, and you are using PDM, then most likely:

You need to CHECK IN the part to save it in PDM the first time it is created, to get it out of your local drive and into PDM.

To make changes, you must CHECK OUT the part
You must GET LATEST to be sure the vault version is the same as your local version

You Must SAVE when CHECKED OUT or none of your changes will go into the vault

Create new Part/Assembly
Save
Check in
Check out
Get Latest
Save
Check in

Pack and go is for sending assemblies out of the network. It is a poor management tool because it will disassociate the file structure.

Use COPY TREE in PDM or SAVE AS

 

[Jboggs]

We only use Pack and Go when moving an assembly to an entirely separate outside network. Pack and go creates separate copies of every component, including every fastener. Why would you duplicate identical components within one network? Makes no sense. It just fills your servers up with duplicate copies of identical or similar parts, and leads to confusing path connections - which seems to be what you are seeing.

Follow drawoh's advice. That's the bets way to do it.