Skip to main content
H
hsjökvist1-Visitor
1-Visitor
August 12, 2015
Solved

Setting up VB API, examples not working

  • August 12, 2015
  • 1 reply
  • 1499 views

Hello Everyone,

For a project at work we are planning to use the VB API of Creo 2.0 to automate some engineering processes. I have set up Creo Parametric 2.0 (M110) and it works so far. I have also successfully run vb_api_register.bat and have added the correct reference to the VB API examples project. In the Object Browser of Visual Studio I can explore the methods, classes, interfaces and so on that the API has to offer. I am missing three interfaces though:

CCpfcAsyncConnection, IpfcAsyncConnection and IpfcAsyncActionListener are missing.

All else seems to be there for the examples to work, but can't test them since these three types are not defined by the API.

Best Regards

Hans


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.
Best answer by hsjökvist

The solution was really simple: Running the vb_api_register.bat with an account that has admin-rights is not enough if UAC is turned on. You have to force the UAC-prompt to appear by right clicking the batch file and selecting "Run As Administrator". Otherwise it will just end without any message telling that it was unsuccessful.

1 reply

H
hsjökvist1-VisitorAuthorAnswer
1-Visitor
August 14, 2015

The solution was really simple: Running the vb_api_register.bat with an account that has admin-rights is not enough if UAC is turned on. You have to force the UAC-prompt to appear by right clicking the batch file and selecting "Run As Administrator". Otherwise it will just end without any message telling that it was unsuccessful.

Terms & ConditionsCookie settingsAccessibility statement