The project that got me thinking about the issue required meto dig up an illustration which was given to a printer to printsticky labels for us. There were about 15 different versions of thefile. I imagine they were created to to give the printer variousoptions to see what imported best for him. However, I was uncertainabout which of them was the original file, and if they all werereally the same.
A similar issue may arise internally as well. Our machinistnormally takes a DXF file we've exported from a SW drawing and usesthis for their work on BobCAD. There are also other file types(DWG, PDF, and JPG) we will export for a vendor or customer.
The question is how to deal with these files in regards to versioncontrol. Most of our work is one-of-a-kind, so it is rare to toucha project after a year. While he project is active, then people canhandle the version control on their own. And for older projects, itis rare enough that we can just assume any exported files arepotentially out of date.
I suggested that we always name an exported version with the prefix"Exported Jun30-08 nnnnn.zzz" This way the original doesn't getburied in a bunch of exported files, and the version date isapparent.
An alternative is to place any exported files in a sub directory,with the directory spelling out the fact that the files inside areall exported from the original file. This way, the machinist canhave their own fenced-in area to play with files.
Any other approaches?
Joe DunfeeSolidworksGeneral
A similar issue may arise internally as well. Our machinistnormally takes a DXF file we've exported from a SW drawing and usesthis for their work on BobCAD. There are also other file types(DWG, PDF, and JPG) we will export for a vendor or customer.
The question is how to deal with these files in regards to versioncontrol. Most of our work is one-of-a-kind, so it is rare to toucha project after a year. While he project is active, then people canhandle the version control on their own. And for older projects, itis rare enough that we can just assume any exported files arepotentially out of date.
I suggested that we always name an exported version with the prefix"Exported Jun30-08 nnnnn.zzz" This way the original doesn't getburied in a bunch of exported files, and the version date isapparent.
An alternative is to place any exported files in a sub directory,with the directory spelling out the fact that the files inside areall exported from the original file. This way, the machinist canhave their own fenced-in area to play with files.
Any other approaches?
Joe DunfeeSolidworksGeneral
