Search results for query: *

I had tried the == previously but to no avail. However, I finally got it to take using the "Relations" - "Look In" - "Feature" instead of "Part". It verified the relations and all seemed well but in the end, Pro-E did not remove the feature as requested when creating the part. I’m blank on this...

OK, I do not know VB language but Pro-E wildfire 3 does use something similar that allows expression very much like VB. Given the problem at hand, I've almost got this thing to work. Currently I have: IF L1_THRD=YES M1_THRD=NO ELSE M1_THRD=YES ENDIF Pro-e tells me "INVALID SYMBOL FOUND" after...

How about it? Anyone up to the Pro-E (Wildfire 3) Relations IF/THEN VBA challenge?

More accurately, I incorrectly used the phrase "Part Interface". The correct term is "Component Interface".

I would like to create an "IF" "THEN" expression to allow on condition to exist in a part "Family Table". I've created 2 part interfaces and would like to express that "IF" one particular part feature (interface) is used (as expressed in the family table as "Y" (YES)) "THEN" the other feature...

I've learned a new & valuable trick. Thanks dgallup!!!

I've created a Part Model & added a Family Table consisting of 5 parts. All are variations of the 1 part. I have created an assembly, utilizing all 5 of the Part Models & have added 2 Helicoils & 2 Pins. Each of these extra parts are added only once (2 Helicoils & 2 Pins total). I created a...