Migrating files

Oct 09, 2003 3 Replies

Has anyone had any problems migrating older version solidworks files to



2004? What if you skip a release and are upgrading from 2001+ to 2004? We can't wait until the end of a project, because all of our project intermingle. We are a mass production facility, so even after a product is launched into production, it still follows us around for years. All that to say, we thought that I could load 2004 on my PC and copy a heap of files on to my local drive, and make damn sure nothing is being opened that's on the network, (I'd unplug my network cable) and test it there because it really does have to be an all or nothing install here. And there are only 3 of us designers here.

Thanks.


I have successfully opened SW2003 models & drawings with no problems. As far as your opening some files from the network, it's ok as long as you don't save them. A way to prevent that is to make them read-only. Obviously, that won't work if the shared network files you would open do, in fact, need to be modified and saved. However, if they are just reference, such as hardware, purchased parts, etc. just set the attribute so you can't write to them. Then all you have to do is put up with the "conversion" message whenever you open them.

WT

Sooner or later all such would need to be migrated I'd expect. Quite often only one release level is supported for such conversion .. the last one.

Make a total backup of the filesets (not the disks) and set up a machine to do migrations .... try to migrate *everything* on the test machine (using a test copy of the files) to look for errors, problems & issues.

I'd expect that the release notes for each main version would contain notes of such *known* problems. I'd also ask your VAR & SW about any known problems in advance.

Once you know you will have no problems (by doing test migrations of the full set of files) (or have fixed any problems found in the original files) you can probably migrate the entire set safely for live use.

But keep those backups for a few years and the old versions(s) of the CAD software as well.

BTW, You may be amazed by the number of part files you have that you find you don't need ...

Don't forget to also migrate any projects that exist now only on archived tapes or disks .... backups are useless if you later find that you cannot use them.

HTH

I have no experience with 2004, but making sure that old parts, assemblies and drawings translate OK is a real pain. It's not enough to just open the files and look for cherries. You have to do a ctrl-q on each part to force a complete rebuild. If you don't do this, you'll think the parts are OK until you try and edit them, only to find the cherries showing up. Then comes the detective game of figuring out what caused the problems and how to fix them. This can take a long time!

Jerry Steiger Tripod Data Systems

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required