Skip to main content
C
ChrisCunningham1-Visitor
1-Visitor
June 24, 2010
Solved

Setting up VB API

  • June 24, 2010
  • 1 reply
  • 12240 views

I am having trouble setting up the VB API. I would like to use it through excel and I am trying to get the example excel/VB program to run, but I am getting the error no: -2147352567, Error: pfcExceptions::XToolkitGeneralError.

I think that I don't have my PRO_DIRECTORY set correctly, and/or the Pro/E Executable Path I'm using isn't correct. My PRO_DIRECTORY goes to my /ptc/proewildfire4 folder and I've tried the full executable path to xtop.exe, and proe.exe.

Can anyone help me with this?

If it makes a difference, when I try to run xtop.exe, I get the error RgiWrapIsoLib.dll was not found. Thanks for any help.

Best answer by JoeVarghese

PRO_DIRECTORY should link to the root folder where proe is installed and not to the exe or bat file.

PRO_COMM_MSG_EXE should be the path to the pro_comm_msg.exe. Its located in <Load point>\i486_nt\obj. (for win xp/nt)

for e.g.

PRO_DIRECTORY = "C:\PTC\ProeWildfire4"

PRO_COMM_MSG_EXE = "C:\PTC\ProeWildfire4\i486_nt\obj\pro_comm_msg.exe"

HTH

Joe

1 reply

C
ChrisCunningham1-VisitorAuthor
1-Visitor
June 25, 2010

I fixed an error in my PRO_COMM_MSG_EXE path, and the executable path i'm using is C:\...\bin\proe.exe (which pro/e says is the startup command). The computer seems to be thinking more, a command prompt going to C:\...i486_nt\obj\pfclscom.exe opens, but now I'm getting the error pfcExceptions::XToolkitNotFound

J
JoeVarghese1-VisitorAnswer
1-Visitor
July 28, 2010

PRO_DIRECTORY should link to the root folder where proe is installed and not to the exe or bat file.

PRO_COMM_MSG_EXE should be the path to the pro_comm_msg.exe. Its located in <Load point>\i486_nt\obj. (for win xp/nt)

for e.g.

PRO_DIRECTORY = "C:\PTC\ProeWildfire4"

PRO_COMM_MSG_EXE = "C:\PTC\ProeWildfire4\i486_nt\obj\pro_comm_msg.exe"

HTH

Joe

    C
    ChrisCunningham1-VisitorAuthor
    1-Visitor
    July 29, 2010

    Thank you, that's what I ended up doing.

    Terms & ConditionsCookie settingsAccessibility statement