It does not modify the files in terms of the model. The only portion that is modified by pack and go is the file reference. It will adjust the file references based on how you choose to do the pack and go (whethere you flatten to a single folder or not) I don't see where pack and go increases error. In my opinion it actually decreases error because it includes everything, but to a certain degree I agree with you that in these cases, it may be a waste of time to use pack and go.
Welcome to the forum.
First I find it strange that the network drive is not communicating woth the PDM vault.
Unless the network location is not the folder setup to be checkout into from the vault.
Rohit is right in that the pack and go does not modify the files. If you are creating brand new
assembly packages different from the originals in the vault then I would think you would want to get this
new package and rename it through SW Explorer and then only provide the changed files like you said and check just
those into the vault leaving the pack and go out of the equation.
Thanks Scott and Rohit for your answers. They confirm that there is no advantage in using pack and go to return a few files to the customer's PDM vault where reference changes are not desired.
I find it interesting that I could not find this clearly stated anywhere in the help documents or online!
That is because it takes users to describe some of these things instead of technical writers