You can open SOLIDWORKS parts and assemblies using Service Pack 5 of the previous release.
For example, in SOLIDWORKS 2018 Service Pack 5, you can open SOLIDWORKS 2019
files. Version interoperability is only supported between consecutive releases. For
example, you cannot open a SOLIDWORKS 2019 file in SOLIDWORKS 2017 Service Pack 5.
Future version files appear in read-only mode when opened in the previous release
and have reduced functionality. The FeatureManager design tree contains limited data.
Any actions that require FeatureManager design tree data cannot be performed with
a future version file open in the previous release Service Pack 5. However, after you
upgrade to the next version of SOLIDWORKS, all the FeatureManager design tree data is
available.
With a SOLIDWORKS part or assembly open in Service Pack 5 of the previous release you can:
- View configurations.
- Use the Measure tool.
- View Mass Properties and Custom Properties.
- View Materials.
You cannot edit future version SOLIDWORKS parts or assemblies in Service Pack 5
of the previous release. You can use future version parts and assemblies in drawings and
assemblies of Service Pack 5 of the previous release.
Adding Future Version Files as Components in an Assembly
In SOLIDWORKS 2013 or later, you can use parts and assemblies from the current release of the SOLIDWORKS software as components of an assembly in Service Pack 5 of the previous release.
Interoperability is only supported between consecutive releases. For
example, you cannot open a SOLIDWORKS 2018 file in SOLIDWORKS 2016 Service Pack
5.
In Service Pack 5 of the previous release, in an assembly, you can do the
following:
- Mate the future version SOLIDWORKS component or subassembly to other components.
- Add a Bill of Materials that includes future and current version components.
- Suppress and unsuppress future version components.
- Create a drawing of the assembly that includes both future version and current version components.
- Use interference detection when mating future version and current version components.
- Mirror and pattern future version components.
- See and reference default planes and origins of the future version part or subassembly.
In multi-configuration models, for each configuration that you want to access in the older release, configuration data must first be generated and saved in the newer release.