can someone provide insight what con/pro between the copy tree vs packGo
I use packNgo to pack files from Vault into a thumbdrive for working at home. While doing packNgo, I put all files into a thumb drive folder and it's working fine
The issue I have is when I save these files from thumb drive back to different folders in the Vault
Jonathan Albert wrote:
Hi Jake,
What are your issues when you add parts back into the vault?
This help blog from Javelin Tech may be helpful:-
https://www.javelin-tech.com/blog/2016/05/pack-go-vs-copy-tree-solidworks-pdm/
Time issue to find the correct folder from Vault to save the files back
It sounds like you may want remote access to your vault, to work from home. You will be able to modify parts from the database.
This is an alternative to modifying a copy from home, and replacing parts at work.
I understand remote access is an option while working from home but I travel to the filed or oversea where there is no internet connection
Before you go on your trips.
Check out the files you need and get latest on all the files you need.
Go to tools --> options --> work offline
Work off of the laptop you have them check out on.
Then when you return to work, tools -> options --> work online Check in all the files you checked out.
Thank you but I believe my question is not clear
Say I have an assembly in the Vault with its components in different Vault folders
I want to pack this assembly (using packNgo or copy tree) to a thumb drive - The assembly and its component will be packed in one folder on the thumb drive. It's fine as I can work from the thumb drive from a different computer with all files in the same folder
My question is there an easy and quick way to save back files in the same folder in the thumb drive to different folders in the Vault
Why is there a thumb drive being used? If the laptop has SW on it, it should have PDM on it, which would make the working offline a viable solution. Do a get latest on the top level assembly and all of the children. It doesn't matter what folder they're in.
If you are using a completely different computer off-site/overseas, that might require some additional back flips. Move tree into a new folder, check out, save to thumb, drive, work on them, transfer back to your main computer, check them in, then move them all back into the original folders. Being that the parts were originally in the vault, they should keep all their references.
Edit - I don't know if you could set up the files to share into another folder. Then you could share to the "dump" folder of all the components in that assembly so it's one location for copying to/from the vault.
To make it short
I got emergency call from a client who is also using SW without PDM - I don't have a laptop with me so all I can do is to pack the files into a thumbdrive and run
Now back to my question
I want to pack this assembly (using packNgo or copy tree) to a thumb drive - The assembly and its component will be packed in one folder on the thumb drive. It's fine as I can work from the thumb drive from a different computer with all files in the same folder
My question is there an easy and quick way to save back files in the same folder in the thumb drive to different folders in the Vault
Look into branch/merge then. We tried it, but under different circumstances. It might be alright for your situation.
Otherwise, I'd go in this order of preference:
#1 "Edit - I don't know if you could set up the files to share into another folder. Then you could share to the "dump" folder of all the components in that assembly so it's one location for copying to/from the vault."
Test it out, see if it works with a small assembly.
#2 "Move tree into a new folder, check out, save to thumb, drive, work on them, transfer back to your main computer, check them in, then move them all back into the original folders. Being that the parts were originally in the vault, they should keep all their references."
a) I don't know how big the assembly is. b) I don't know how scattered your files are in the vault. c) there is no easy button. File management uses the SI/SO theory. "stuff" in/"stuff" out, you can translate that into whatever words you want. It's either time in the front end, or time in the back end.
Jon,
Copy tree is not 100% better than packNgo since it's not included folders structure
What Jeremy said is what I thought I explained. These are 2 completely different methods for copying files. Depending on what you are trying to accomplish speaks to which one you use.
https://www.javelin-tech.com/blog/2014/07/solidworks-pdm-copy-tree/
I take work home all the time. If all you are doing is transferring the same files to work on to a different location, use pack-n-go. If you are making copies of an existing assembly package that you need to change the files names of and keep them all linked together, use copy tree.
That is my 2 cents.
Scott McFadden wrote:
I take work home all the time. If all you are doing is transferring the same files to work on to a different location, use pack-n-go. If you are making copies of an existing assembly package that you need to change the files names of and keep them all linked together, use copy tree.
That is my 2 cents.
Whatever tool to use (packNgo or Copy tree), I want to have the same folders structure in the thumb drive as in the Vault
have you tried either of these options in pack n go?
pasted snips do not seem to be displaying, so i will try inserting the image and attaching it...
"Keep full folder structure" works - I don't see this option with "copy tree" ?
Understand, Copy Tree makes a copy of the assembly changing the Assembly file name and what other part models you need copies of as well. Keeps the same folder structure as the original being copied. Unless you change the pathing of the copies being made.
Then once you have your copies, I guess depending on what the end result is you need, you can check out of the PDM and do a pack n go of that to your thumb drive.
Hope that makes sense.
Scott McFadden wrote:
Understand, Copy Tree makes a copy of the assembly changing the Assembly file name and what other part models you need copies of as well. Keeps the same folder structure as the original being copied. Unless you change the pathing of the copies being made.
Then once you have your copies, I guess depending on what the end result is you need, you can check out of the PDM and do a pack n go of that to your thumb drive.
Hope that makes sense.
I tried "copy tree" and don't see any option for folders structure
unless I'm missing some here - "copy tree" puts all files form different folders in Vault to a single destination folder?
it DEFAULTS to a single folder, but you can manually set the path individually for each file in the table in the lower portion of the dialog.
you are correct that it does not have the option to automatically copy the existing structure.
Understood. There are options while doing the pack-n go to keep the folder structure as shown in Jeremy's screen shot.
Hi Jake,
What are your issues when you add parts back into the vault?
This help blog from Javelin Tech may be helpful:-
https://www.javelin-tech.com/blog/2016/05/pack-go-vs-copy-tree-solidworks-pdm/