LOL, it's good to know we're not alone. What version of ProE did you use? We were running ProE 5.0 M070 and experienced the problem on our test system. We upgraded to M130 moments ago and that problem is gone.
[cid:image001.png@01CD2939.01ABBF80]
Patrick Williams | Engineering Systems | o: 616.698.3766 | c: 616.947.2110 [cid:image002.jpg@01CD2939.01ABBF80]
Yeah this is strange but I'd rather they devote resource to moving forward rather than backwards compatibility for something as new as Creo 1. This is kind of the Mozilla update path now too.
Well, maybe their thought process was like this...
Creo is new and different, so most of our customers will probably skip 1.0 since that seemed to be the case with Wildfire 1.0. Therefore we will not devote the massive amount of resources required to test/QA on all versions of our data management offerings knowing that more customers will adopt 2.0.
Patrick Williams | Engineering Systems | o: 616.698.3766 | c: 616.947.2110 [cid:image002.jpg@01CD293C.4DB5A960]
I am sorry, but...WHAT? CREO 1 has been out about 1 year now, that's it! I don't care how many people are on it or not, it is only 1 year into it's release cycle, and there should NOT BE any compatability issues, especially with Windchill..especially for a Windchill product that was being developed when CREO 1 was in development and released.
This isn't common but when you make such significant changes that sometimes they can't be retrofit. I think most of this is related to the new config management capabilities in Creo 2.0 and Windchill.
Its also not that anything is wrong with Creo 1.0 its just that WC10.1 has taken a big step forward.
