Skip to main content
3
356guy1-Visitor
1-Visitor
February 24, 2017
Solved

Has anyone used the PTC license required to enable solidworks files?

  • February 24, 2017
  • 3 replies
  • 4803 views

Has anyone used the PTC license required to enable Solidworks files in creo2 or 3?

I have no problem opening Creo files in SW2017 but if I try and open a SW file in Creo3 it says I need some additional license.

Does anyone with experience using both SW and Creo have any input?

Best answer by BrianMartin

Holy cow, Tom... I think you just inadvertently provided me with an answer to a question that's been plaguing me for some time. I didn't put it together. Whenever I disconnect from Windchill, Unite works (at least enough to open a SolidWorks 2016 file). Whenever I'm running a linked session, I get the ATB error. We actually own ATB and have it enabled, too... but we don't have the collaboration extension yet. I should've caught this but having you point it out no makes it seem obvious. Of course that's the problem!

Hey PTC... one license man... just take a bucket of money and give me everything. I am sick of playing with your weird licensing schemes. Geez, man... for the love of all that's holy please simplify this mess.

3 replies

T
TomD.inPDX17-Peridot
17-Peridot
February 27, 2017

For Creo 3, PTC came up with some kind of collaboration package extension.

After installing the SW Explorer for Creo 2.0, it opened SW files but they were still imports.

Creo 3.0 was touted on collaboration and that the SW exchange was going to be "wonderful".

All I found was unmanageable limitations if you didn't buy the extension.  ...Which means unending maintenance costs.

Overall, I do not regret my solution.  I bought SW instead.

For my purposes, this was cheaper in the long run and solved my problem.

Background: Client was on SW and I know Creo.

I needed to give them data back that was useful in SW.

Core Creo 3 didn't deliver anything in that regard for me.

The extension was also fraught with version compatibility concerns.

B
BrianMartin13-Aquamarine
13-Aquamarine
February 28, 2017

In my personal opinion, another missed opportunity and a rather large flub by PTC.

Don't advertise how great Unite Technology is then provide customers with some weird, functionality limited mess that requires an additional license to untangle. None of the advertising videos spelled out that this was a separately licensed thing. In fact, I feel they led you to believe otherwise. They caught me with it... we upgraded everything necessary to make it work: Creo, Windchill, Creo View adapters, etc... and then figured out we couldn't use the tool without an additional cost.

Thumbs down.

T
TomD.inPDX17-Peridot
17-Peridot
February 28, 2017

Oh yes, it was a bill of goods and received nothing but empty promises and additional problems for core users.

My going to Creo 3 for this one client created a serious mess.  Buying SW was my only way out.

I am staying on Creo 2 for reliability reasons.

Sorry Dan, the soapbox was out

Did you get your question answered yet?  ...or do we need clarification to your question?

M
MartinHanak24-Ruby III
24-Ruby III
February 28, 2017

Hi,

below mentioned information is related to CR3, only.

1.] Creo 3.0 is able to open Solidworks models (parts, assemblies) up to 2016 version. 2017 is not supported.

2.] Creo 3.0 license must contain Creo Unite module (336). This module is available for free and enables opening Solidworks models. If you are missing it, request new license file.

3.] To be able to save model into Solidworks 2005 format, you must buy Collaboration_Ext_SolidWorks module (341)

MH

B
BrianMartin13-Aquamarine
13-Aquamarine
February 28, 2017

I don't know Martin - I specifically had a conversation with my PTC rep saying we needed the collaboration extension for more than just saving. Also, I've pulled something like a dozen license files within the past 2 years and I never see 336 in the listing. If it's supposed to be free, someone has dropped the ball big time.

I mean, not that I'm surprised... but if this is true, I am irritated!

B
BrianMartin13-AquamarineAnswer
13-Aquamarine
February 28, 2017

Holy cow, Tom... I think you just inadvertently provided me with an answer to a question that's been plaguing me for some time. I didn't put it together. Whenever I disconnect from Windchill, Unite works (at least enough to open a SolidWorks 2016 file). Whenever I'm running a linked session, I get the ATB error. We actually own ATB and have it enabled, too... but we don't have the collaboration extension yet. I should've caught this but having you point it out no makes it seem obvious. Of course that's the problem!

Hey PTC... one license man... just take a bucket of money and give me everything. I am sick of playing with your weird licensing schemes. Geez, man... for the love of all that's holy please simplify this mess.

Terms & ConditionsCookie settingsAccessibility statement