{Blank Subject 2010-09-13}

[akelly]

Using Pro/Intralink 9.1 and Wildfire 4

I have an assembly "A" with a component "B". I want to replace component "B" with component "C".

I could do this in Pro/E, but "B" has a lot of dependencies, so it would take a while to reconstruct those. What I want to do is have Pro/Intralink replace "B" with "C" in assembly "A". "C" is a copy of "B" with a few changes, so the feature IDs of the dependent references should be the same between the two.

I tried performing a "Save As" on "B" from the Pro/Intralink workspace to get "C", so I could use the update parents screen, but ran into a conflict because "C" already exists in Commonspace. It is not possible to override this conflict to tell Pro/Intralink to ahead and use the existing "C" model in place of the copy.

Any ideas how to get Pro/Intralink to replace component "B" with component "C"?

Andrew Kelly, P.E. | Senior Engineer | Crane Aerospace & Electronics | +1 440 326 5555 | F: +1 440 284 1090


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

[rcrisp]

Proe Users,



Are Wildfire 4 & 5 files cross compatible w/ 32-bit & 64 bit systems?

SolidWorks 2010 is a memory hog and is forcing me to move to 64-bit but I
need to verify that I will not have any compatibility issues with Proe files
for clients that are operating on 32 bit systems. If they are not compatible
are there any software utilities offered that will convert the files? Or is
this wishful thinking J



Dell Precision M6500 Intel(R) Core i7 2.67GHz 4MB RAM



Ryan Crisp | Senior Mechanical Engineer

Priority Designs
501 Morrison Rd.
Columbus, OH 43230
(614) 337-9979
<">http://www.prioritydesigns.com> www.prioritydesigns.com

CONFIDENTIALITY NOTICE: This email along with any attachments contains
proprietary information, some of which may be legally privileged. If you are
not an intended recipient of this email, you must not disclose, copy or take
any action in reliance of this transmission. If you received this email in
error, please contact the sender and permanently delete all copies of the
email and any attachments.

[ptc-169947]

Hi all,

What's the relationship between the STYLE tool and surfacing (WF 2)? Our style icon is greyed out. Can anyone tell me what that means. Is is necessary for advanced surfacing (like a mouse)?

Thanks,
Stefan

[bfrandsen]

This should do the job when "C" is a copy of "B":

Check in "C" to Commonspace.
Set config.pro option let_proe_rename_pdm_objects Yes
Open assembly "A" with "B"
Rename "B" to "C" in session
Save assembly "A"
Update "C" from Commonspace.

Otherwise I would suggest the enhanched Replace Unrelated functionality in
WF4. When "C" is a copy of "B" it can redefine many references
automagically.
Bjarne




"Kelly, Andrew C" <->
13-09-2010 15:46
Please respond to
"Kelly, Andrew C" <->


To
-
-
cc

Subject
[proecad] - {Blank Subject 2010-09-13}






Using Pro/Intralink 9.1 and Wildfire 4
I have an assembly "A" with a component "B". I want to replace component
"B" with component "C".
I could do this in Pro/E, but "B" has a lot of dependencies, so it would
take a while to reconstruct those. What I want to do is have
Pro/Intralink replace "B" with "C" in assembly "A". "C" is a copy of "B"
with a few changes, so the feature IDs of the dependent references should
be the same between the two.
I tried performing a "Save As" on "B" from the Pro/Intralink workspace to
get "C", so I could use the update parents screen, but ran into a conflict
because "C" already exists in Commonspace. It is not possible to override
this conflict to tell Pro/Intralink to ahead and use the existing "C"
model in place of the copy.
Any ideas how to get Pro/Intralink to replace component "B" with component
"C"?
Andrew Kelly, P.E. | Senior Engineer | Crane Aerospace & Electronics |
+1 440 326 5555 | F: +1 440 284 1090
We value your opinion! How may we serve you better?Please click the
survey link to tell us how we are doing:

[ptc-726111]

Hi Ryan,

I use the 64-bit version of Pro-E WF 3.0 and have shared the files with 32-bit Pro-E users without problems. I cannot speak for WF 4.0 & 5.0, but there should not be a problem sharing CAD files between 32-bit & 64-bit systems.

A problem 64-bit users occasionally experience when switching to 64-bit systems is the lack of drivers for older software, such as printer drivers. I had a problem with the PDF driver for QuickBooks Pro until I upgraded to the 2008 version a few years ago.

In Reply to Ryan Crisp:

Proe Users,



Are Wildfire 4 & 5 files cross compatible w/ 32-bit & 64 bit systems?

SolidWorks 2010 is a memory hog and is forcing me to move to 64-bit but I
need to verify that I will not have any compatibility issues with Proe files
for clients that are operating on 32 bit systems. If they are not compatible
are there any software utilities offered that will convert the files? Or is
this wishful thinking J



Dell Precision M6500 Intel(R) Core i7 2.67GHz 4MB RAM



Ryan Crisp | Senior Mechanical Engineer

Priority Designs
501 Morrison Rd.
Columbus, OH 43230
(614) 337-9979
< www.prioritydesigns.com

CONFIDENTIALITY NOTICE: This email along with any attachments contains
proprietary information, some of which may be legally privileged. If you are
not an intended recipient of this email, you must not disclose, copy or take
any action in reliance of this transmission. If you received this email in
error, please contact the sender and permanently delete all copies of the
email and any attachments.

[ptc-593619]

Ryan,
We recently changed to 64 bit because of long wait times for massive
files and it has been nothing but positive in the results. Because I am
a bit of a skeptic, I opted to have both the 64 bit and 32 bit ProE
loaded as per Chris's comment some older software is not 64 bit
compatible. As far as switching between systems it is absolutely
seamless so no problems there. The printer drivers are a bit of a pain
as the printers will only work on the 64 bit system!

Richard A. Black
Lead Design Engineer
Eaton Corporation
440 Murray Hill Road
Southern Pines
NC 28387 USA

[A.DelNegro]

Sorry for the off-Pro/E topic again but this list is way to useful for
just Pro/E.



We are having some issues with a part we cast in urethane. Specifically
RoyalCast 3105 material. If there is anyone out there who is an expert
on urethanes that could offer some advice, please contact me ASAP.



Thanx in advance.

Tony





J. Anthony DelNegro, P.E.

Product Development Engineer

Micropore, Inc.

350F Pencader Drive

Newark, De 19702

PH: 443-245-4130

FAX: 302-731-8214