Must Convert to 2010?
Must Convert to 2010?
(OP)
Across the organization, we have created hundreds of parts, Assemblies & Drawings. All of them are in Workgroup PDM.
I have lernt about the solidworks Task scheduler's file conversion.
Now, Is it a MUST to convert all the files to 2010? Whats the best practice?
I have lernt about the solidworks Task scheduler's file conversion.
Now, Is it a MUST to convert all the files to 2010? Whats the best practice?
~ BT






RE: Must Convert to 2010?
However, I strongly advise you to make a backup of your vault before proceeding. There's no telling what kind of issues you might run into after the update, and once it's done it can't be undone (unless you have a backup).
RE: Must Convert to 2010?
Also, while the vault can be a newer version (ie 2010) than the files in it, you can't put newer version files in an older version vault. At least that's how I remember it.
Jeff Mirisola, CSWP, Certified DriveWorks AE
CAD Administrator, Ultimate Survival Technologies
My Blog
RE: Must Convert to 2010?
Hundreds of parts, Assemblies & Drawings will not take long at all. Set solidworks Task scheduler's to start when the last one leaves for the night plus 1 hour. Then you come in before anyone else starts the following morning. Reason I say this is because upgrade locks the vault for short bits of time. Which makes people think PDM is not working.
Standing
SolidWorks Pro 2009 x64, SP3.0, PDMWorks Workgroup, SolidWorks BOM,
HP xw8600, 64-bit Windows Vista Business, Service Pack 1
Intel Xeon CPU, 3.00 GHz, 16 GB RAM, Virtual memory 166682 MB, nVidia Quadro FX 4600
RE: Must Convert to 2010?
RE: Must Convert to 2010?
Matt Lorono
Lorono's SolidWorks Resources & SolidWorks Legion
&
RE: Must Convert to 2010?
My reason for this is that sometimes changes can be made to the files that cause them to blow up. Maybe a bug in the new version does something weird to your mates. Maybe a series of features that where barely stable in your down version blow up when saved in the new version. Maybe you are in an FDA regulated environment, and any unvalided changes (regardless to how slight) put you at audit risk.
These are just a few of the points that you may wish to consider. However, many companies do the wholesale convertion without issues.
Matt Lorono
Lorono's SolidWorks Resources & SolidWorks Legion
&
RE: Must Convert to 2010?
Chris
SolidWorks 09 SP4.1
ctopher's home
SolidWorks Legion
RE: Must Convert to 2010?
Our case is the opposite. We could not upgrade, because the plant works 7/24/365 days a year. I could not stop the PDM for 22,000+ updates. I was doing it in small batches and the stock room complained the PDM was not working.
Now for the problem, we needed a drawing that was 5 years old and never updated. I could not open the drawing do to errors. I had to redraw from hard copy.
Standing
SolidWorks Pro 2009 x64, SP3.0, PDMWorks Workgroup, SolidWorks BOM,
HP xw8600, 64-bit Windows Vista Business, Service Pack 1
Intel Xeon CPU, 3.00 GHz, 16 GB RAM, Virtual memory 166682 MB, nVidia Quadro FX 4600
RE: Must Convert to 2010?
This year SW will be 15 years old and has undergone many changes. Consider how much more the software will have changed in the next 15, 20 or 50 years. Every year files are not converted, the risk of corruption will increase. Unless specific conversion software existed, attempting to convert a 50 year old set of files would almost certainly not produce good results.
Backups should always exist before converting files, so even if some files were corrupted, the originals still exist.