I have some people who are on 32 bit systems, so they downloaded the 32 bit SE version. However it does not open 2015 files, can I convert somehow to 2014? Is there any way for me to get them the files to view? I am on SW 2015.
No, you can not convert them to 14.
I guess the executable file won't work then??
That might not help as it is 64 but exe file.
Also have a look here: Re: Is there a solution to view Solidworks 2015 models on a 32bit computer, like eDrawings?
The only solution I found was to hijack the only 32 bit system left in the building, open my SW model with 2015 SE and save it with the 2015 SE - 32 bit version. If I did not have the 32 bit system left, we would have been sunk.
The E drawings 2015 SE will open 2015 SW files, but not 2015 e drawings files.........go figure. I cant believe this is the case, but it appears so.
Why you need to save them as eDrawings file? Can't they simply open the 2015 SW files directly with eDrawings 2015 SE 32 bit version?
In short, we do not want to be sending our models out in the world.........where competitors could obtain them. E drawings helps protect that aspect. Also, with E drawings we are not sending out a hundred or so files, and trying to direct them on which ones to open etc...
If one is clever, he/she can get the data even with the edrawings.
Further you don't need all files when opening SW assembly file in edrawings i.e. you can open the assembly file directly into eDrawings, without need to have any component file.
wow, excellent, I did not realize I only had to send the assembly. Once again, Deepak has taught me something!!!! Thanks!
As for getting the data, I know what you mean but at least its a "little" safer, aka takes more effort
Well with assembly file only, they can't open in SOLIDWORKS (so you're safe there). They can either open in view only mode or use eDrawings. So either way it would same case as sending an eDrawings file.
NO IT'S NOT THE SAME!!!! Only the last active configuration can be opened using this method. So unless you want to save your assembly once for each configuration this is not a solution either, and who wants to wade through 20 files instead of simply selecting a configuration from a list? Again I think that SolidWorks has taken a huge step back here. There Drive application which is only a dream at this point may promise to help but with them wanting to sell their Design Conceptual I don't see a lot of effort being put into the Drive product to resolve this issue properly.
Retrieving data ...