Convert from 2004 back to 2003
Convert from 2004 back to 2003
(OP)
One component of a large assembly was converted to SW2004 sp01. I need to get it back to 2003 sp3.1 rather than recreate from scratch. Is there any way to do this?
When was the last time you drove down the highway without seeing a commercial truck hauling goods?
Download nowINTELLIGENT WORK FORUMS
FOR ENGINEERING PROFESSIONALS Come Join Us!Are you an
Engineering professional? Join Eng-Tips Forums!
*Eng-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting GuidelinesJobs |
Convert from 2004 back to 2003
|
RE: Convert from 2004 back to 2003
Parasolid Export or STEP will give uou a dumb solid that 2003 can open.
"Wildfires are dangerous, hard to control, and economically catastrophic."
Ben Loosli
CAD/CAM System Analyst
Ingersoll-Rand
RE: Convert from 2004 back to 2003
You're best bet is to export it as a Parasolid (or whichever translation you choose) though 2003, after you import the file, run it through featureworks to regain as much of the sketches & features back. (if you got the addin)
RE: Convert from 2004 back to 2003
The other thing to try is talk to you administator and see if there is a backup file of the data that you could have them restore for you. At my place we can go back for one year and get old data files.
Just some thoughts that may help.
RE: Convert from 2004 back to 2003
RE: Convert from 2004 back to 2003
Like you, and probably many others, I learned the hard way that you should always, always, always make backups of your part & assembly models.... especially before upgrading to a newer version of SW. Actually the same goes for any program files.
CorBlimeyLimey
Barrie, Ontario
FAQ559-863
RE: Convert from 2004 back to 2003
RE: Convert from 2004 back to 2003
To add to CorBlimeyLimey response you should also and ALWAYS, ALWAYS test the new version before converting to the newest version. I have seen many people eat the carpeting to keep from screaming, because they wish they wouldn't have switched because it caused this or that problem... So always test it before switching over fully. You can run more than 2 different versions of SW on one station. you just have to install into different folders. I usually use Solidworks03, or Solidworks04, etc...
Regards,
Scott Baugh, CSWP


http://www.3dvisiontech.com
http://www.scottjbaugh.com
FAQ731-376
RE: Convert from 2004 back to 2003
As a marketing tool - I think the Solidworks people have shot the bull on this one.
All that it is is aggrevating.
RE: Convert from 2004 back to 2003
At the risk of sounding offensive
You state that SW has “shot the bull on this one”. In my opinion, they have found the Bullseye and are zeroing-in on dead centre faster than any of the so-called competition.
On a more positive note, it has been stated in this and other threads, that you can install different versions of SW on one computer, which would allow the use of whichever version a particular client needs. I realise that newer is not always better, but an alternative would be to convince your clients that they should update their software to take advantage of the latest offerings (which you and your other clients have done) and thereby remain competitive.
You could use eDrawings (the viewer is free to download) if your clients need to view & mark up drawings or PDF files (if you have the conversion module) or simple hardcopies for manufacture if that’s all that is needed.
Sorry to rant on my
CorBlimeyLimey
Barrie, Ontario
FAQ559-863
RE: Convert from 2004 back to 2003
Yes - the backwards compatibility is aggrevating.
I am not provoking anything accept hopefully some future improvment in this regard.
I have told SW of this aggrevation over 2 years ago. Hopefully by seeing it here again, there will be a meaningful resolution. So take that in a positive spirit with which it is intended.
Heck - Im even willing to spend extra money on a backwards conversion utility if thats what it takes!
RE: Convert from 2004 back to 2003
Regards,
Scott Baugh, CSWP


http://www.3dvisiontech.com
http://www.scottjbaugh.com
FAQ731-376
RE: Convert from 2004 back to 2003
A lack of backwards compatibility is not a bug, it is a feature.
--
Crashj
RE: Convert from 2004 back to 2003
Since I run a business, backing up all files is mandatory--especially before doing something risky like jumping into a new version of SolidWorks or even a new version of the part/assembly. Doing this and knowing what version my client needs before performing the work eliminates backward compatibility problems altogether. (Prevention is better than cure.)
Jeff Mowry
Industrial Designhaus, LLC
http://www.industrialdesignhaus.com
RE: Convert from 2004 back to 2003
It IS NOT POSSIBLE to provide backward compatibility with any complex software that continues (THANK GOODNESS) to be enhanced and provide new features. Even to attempt to do so would require a massive software programming effort. Then you have to do all combinations of all software versions otherwise some whiner would bleat because they left out SW2003 SP4 to SW2001 SP10 or some such wierd combination. The approximations and lost data that would result even if they they were partially succesful would just frustrate you even more - then you would realy be complaining.
As a business decision it is also a no-brainer, because the percentage of total users who would actually use this is SO small.
I for one do not want any sane business to be rat-holing prescious software resources into this kind of dead end unfunctionallity. Gimme new stuff!!!
Be naughty - save Santa a trip.
RE: Convert from 2004 back to 2003
I don't think the group of users who would like to have a converter for 2004-2-2003 would be too small. I work with 2004 but my supliers still work with 2003 and they don't intend to go to 2004. So now we are having trouble with the feedback.
Kind Regards,
Bouke Brouwers.
RE: Convert from 2004 back to 2003
However, in my case, we do all the design and really don't need parametric editing ability with our vendors--if they can read it, that's good enough.
So we export assemblies into parasolids, which will open in whatever version of SW and maintain the relative positions of each part in the assembly well enough to get the point across. Annotations and feedback can be done with E-Drawings.
Ideally, you find out what version your suppliers (or clients, etc.) need before you take off on the project. It's always handy to keep a few older versions of SW on your system for those reasons--or for viewing/editing files that need to remain in older versions. We have this come up frequently as well.
Jeff Mowry
Industrial Designhaus, LLC
http://www.industrialdesignhaus.com
RE: Convert from 2004 back to 2003
It's flogging a dead horse.
I was - and he did. So at least I didn't get coal.....
RE: Convert from 2004 back to 2003
What up with that? Them bums get something right?
-----------
Mr. Pickles
RE: Convert from 2004 back to 2003
3D modeling software is a lot more complex.
Personally, I would not mind the option to save back, but I believe the programming effort involved would be too great and would take away from putting in more useful functions.
Can anyone else think of a 3d cad program that allows saving back.
Jason Capriotti
ThyssenKrupp Elevator
RE: Convert from 2004 back to 2003
Thanks for the steady voice of reason, Gildashard. We are all getting a bit punchy on this one. I do, believe it or not, agree that personally I would not mind the option to save back. Very occasionally it could make life a little easier, but it is not going to happen so I'm not holding my breath.
The only thing you can really do is Parasolid out and back in. Now they are talking about getting some sort of feature compatibility in STEP, so maybe we could eventually get a partial solution. A "solid body feature"
might allow for some of the incompatibilities? Dunno about cuts though. Anyone ever done a save as part on an assembly containing some imported Parasolids? - might give an idea of what it would look like.
I was - and he did. So at least I didn't get coal.....
OK, OK, It's a reference to my holiday sig. "Be naughty - Save Santa a trip..."
RE: Convert from 2004 back to 2003
I think your 1.5% figure on those who wish to backsave is out to lunch.
The problem is not when you keep the information inside your own company. The problem is when you have to transmit data to the outside world who usually run different versions of the software.
In Autocad for example, when you backsave, you may loose some functionality, but usually 90% + is there and you can work with the information.
If solidworks would allow you to backsave and give 75% functionality, I dont think that we would have such a heated discussion. I dont buy the notion that no one wants it or no one would use it, or that its too difficult. On a backsaving issue, I wouldnt expect perfection, just something thats usable.
RE: Convert from 2004 back to 2003
Hi Guys,
visit us in booth #17 in Boston for the following demos:
ShapeWorks - nurb surfacing inside SolidWorks
ExChangeWorks - saves SW files from newer versions to older with design tree
3D File Converter - saves SW files into 3DS Max, Lightwave and *.obj
Picture Converter - converts *.bmp pictures into SW sketch
See you there,
Baren-Boym Company
www.Baren-Boym.com
I'll be going to the Conference this weekend and I will be checking this out!
Regards,
Scott Baugh, CSWP

http://www.3dvisiontech.com
http://www.scottjbaugh.com
FAQ731-376
RE: Convert from 2004 back to 2003
RE: Convert from 2004 back to 2003
Regards,
Scott Baugh, CSWP

http://www.3dvisiontech.com
http://www.scottjbaugh.com
FAQ731-376
RE: Convert from 2004 back to 2003
2. Your point on customers or vendors having older revs. is valid (and I have encountered it). But again, if you are really needing SW feature functionality after you export to them, then it is important enough that they ought to be up to the latest rev. In our business I would have a hard time dealing with companies that don't pay for the support licence. (Of course if you are the one who is out of date, well....).
3. As it turns out we have found that except under exceptional circumstances it is safer to send a Parasolid anyway. We have had some (even large) companies make very expensive mistakes by someone either using the wrong configuration or inadvertently suppressing a feature or something. You would think that was a no-brainer, but noooooo...... One of them was having a large and complex investment casting wax mold made and fortunately the machine shop happened also to be one that knows our parts very well. They figured out that the model they had been sent by the casting house was basically the machined configuration!!! We got lucky that time. Could have been a $100,000 mistake for them and a leadtime disaster for us.
4. If this 3rd party stuff does work the way we hope (IF) then the most we should expect is getting it as a Partner solution. I don't think SW would adopt it. Probably the time required to check it all out on new revs. would delay the new revs. (Of course there are always SP's....) As a 3rd party they can get away with some lag in their options as long as the basic software (in this case surfacing) works on time. Come to think of it, I believe we have a seat of it on one of our systems, which means we have a support licence for upgrades. Hey, guys, maybe I will be able to let you know if it really works? Ahh, look at me - getting all excited about something I didn't think much of yesterday! Never let it be said that I'm closed minded...
I was - and he did. So at least I didn't get coal.....
OK, OK, It's a reference to my holiday sig. "Be naughty - Save Santa a trip..."
RE: Convert from 2004 back to 2003
Just my 2p on running 2 versions on the same machine...
"Gimme dat stickwelder, will yer lad. No need to get all fancy wid'those modern drills." Apprenticeship Lesson 61
RE: Convert from 2004 back to 2003
I have both 2004 and 2003 running on my machine as I'm responding to this. I'm assuming that the error you got said something like "Solidworks Journal Files already Exist". If that was the error you have to go into Tools, Options, System Options. Then in file locations make sure the directory name for the journal files that SW creates are different for each version of SW.
mncad
RE: Convert from 2004 back to 2003
One you have to install each version in it own directory. EX: Solidworks01+, Solidworks03, Solidworks04...
If you run each of them at the same time you might get that error that mncad posted.
If your saving a parasolid from SW04 and try to open it in SW03 make sure you save the Parasolid to version 14. Same goes for SW03 - Version 13 - Always save it one verion back of the recent Parasolid version for and older version of SW to open it.
I run SW04, SW03 and SW01+ and I can run all 3 together at one time. So I know running them together and loading them onto one machine does work.
Regards,
Scott Baugh, CSWP

http://www.3dvisiontech.com
http://www.scottjbaugh.com
FAQ731-376
RE: Convert from 2004 back to 2003
If everyone out there who has had to even consider this thread, would call their retailer and /or solidworks direct and complain then you'd see the programmers develop solidworks just like autocad. You don't see autocad preventing backward compatible issues from slowing down sales do you. We run 2001+ and won't upgrade for just the reasons presented here.
I urge everyone to complain. "The squeeky wheel gets the grease!"
db
AES PRODUCTS INC.
CHICO, CALIFORNIA
RE: Convert from 2004 back to 2003
RE: Convert from 2004 back to 2003
The magnitude of code change necessary to maintain solid bodies and their parametric features is tremendous when compared with the code changes necessary in displaying arcs and lines in three-view format.
Jeff Mowry
Industrial Designhaus, LLC
http://www.industrialdesignhaus.com
RE: Convert from 2004 back to 2003
Now don't go and take this all personal, but the mere fact that you don't seem to understand this and the real technical problem in general suggests that maybe you ought not be be using this type of CAD system? Maybe the old stuff of more the kind of thing you need?
BTW: I only said "AUTOCRUD" just to stir all of you up, so don't take umbrage - just a joke. It is a fine system for many purposes, just as virtually all CAD systems are. They all have their stengths and weaknesses.
I was - and he did. So at least I didn't get coal.....
OK, OK, It's a reference to my holiday sig. "Be naughty - Save Santa a trip..."
RE: Convert from 2004 back to 2003
AutoCAD is preventing users from bring in older files to their new versions of AutoCAD. At least SW lets you bring in old files to newer versions. (This is what I have been told by my customers and other people. I can't test this because I don't have AutoCAD here... Why would I want it... I have SW!!!)
Anyhow I'm back from the Conference and I checked out what I posted above.
Not what you might think. It's a neat concept but that's about it. When I asked about the program they informed me that it was still in experimentation mode, which was fine.
1) First thing he did was he open a part.
2) The part was a small cylinder extruded. With a square extrusion off of it. The Edges had round corners. At the end of the square Extrusion there was wavy surface. That Surface cut the Square extrusion.
3) First thing he did was remove the surface and the cut feature.
4) He saved the file as a 3dx file format.
5) Close the file.
6) Reopen it in SW04
That tells me nothing about how SW03 or older versions will interrupt the file.
7) SW04 rebuilt the file... like using a macro to make the part... simple.
I asked if Dimensions from the sketches could be transferred.
8) He tried it again... No dice! The dimensions are removed.
I asked how does this program handle new functions in later versions of SW for older versions?
9) His response... They are import features.
Just like saving out a Parasolid.
So to my conclusion. This functionality and this program as it is now is useless.
1) Because a new function is brought in as an imported feature. Yes you get some of the features it will recognize. But you could get the same thing if you used Feature Works, and it would leave the rest as an imported feature.
2) It doesn't save Dimensions that are required for editing of the sketches. Then the sketches become under defined and can be moved by accident.
3) I didn't see him try and open it in SW03 or older version. So how can I tell what the response would be?
4) If you did export out this info then the face ID's are different. What are you going to do when you do this with and assembly? You will lose mates if you used faces...
These are some things to think about when saving to different versions.
If I think of more I'll post them!
Regards,
Scott Baugh, CSWP

http://www.3dvisiontech.com
http://www.scottjbaugh.com
FAQ731-376
RE: Convert from 2004 back to 2003
It was also written above, "In our business I would have a hard time dealing with companies that don't pay for the support license." Is dealing with Asia, I don't always have the luxury of switching vendors. Pricing, capabilities, and a good working relationship seem like good enough reasons to look past the error of not paying for a support license.
RE: Convert from 2004 back to 2003
1) Deal with the fact that you will not be able to save back a version, because you cna't do it from SW natively.
2) Install all ther versions you need to install onto your HDD. Then work on the Version that your client is using. (You would have install each SW into a new directory - e.g. Solidworks01+, Solidworks03, Solidworks04, etc...)
3) Look at the baren-boym add-in. www.barenboym.com
YOu might only use extrudes, fillets, and revolves... but what about your customers? is that all they ever use? If so then you should look into Item3.
Regards,
Scott Baugh, CSWP
http://www.3dvisiontech.com
http://www.scottjbaugh.com
If you are in the SW Forum Check out the FAQ section
To make the Best of Eng-Tips Forums FAQ731-376