Here is the description from the user:
My project is to write a VBA application in Excel that will run a global interference analysis and produce a useable report in Excel. As you may know, the built-in global interference check is nearly useless for large assemblies since it does not indicate the paths of the interfering parts. Thus, if a screw is interfering, there is no way of knowing which subassembly contains the offending screw. Pro/E just says that "SCREW.PRT" is interfering. As you know, we have thousands of screws in the model. This is also true for other parts that are used in multiple places within an assembly and multiple places in different assemblies. Basically, it is really hard to track down where the interferences lie.
Anyway, the VB API appears (according to documentation) to have the ability to get to the component paths once the interference check has been run (yay). However, I get an "unimplemented" error when actually running it (sigh).
Can you please verify if this is truly unimplemented for the VB API? If it is true for the VB API, can someone tell me if it is available for J/Link or Pro/Toolkit? I really would like to pursue writing a useable interference analysis tool, and will consider Pro/Toolkit or J/Link if needed. Furthermore, is this fixed in Creo 2 or in other builds of Wildfire 4 (we are using M220)?
I am open to other methds to solve this. His initial question is how to use ComputeGlobalInterference in Visual Basic and if not is it available in J-Link or Toolkit? My question is this the best method to generate a relationship report for interfering objects and the assemblies/parts they interfere?
TIA.
Patrick Perry -- BAE Systems
Andreas,
pfcException::XUnimplemented;method:
Function GetInterferences(assembly As IpfcAssembly) As IpfcGlobalInterferences
Set globalEvaluator = ccInterference.CreateGlobalEvaluator(assembly)
End Function
When he goes to compile he gets the above error.