cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Setting Up VB API

SOLVED

Re: Setting Up VB API

Hi Seshu,

Thanks a lot for that !

Re: Setting Up VB API

thanx Seshu,

But I have some problem the software AMC is finished my comp has not taken AMC the links are reqired AMC. he links are not open. how can i work please help me yarr i am in very thanfull to you please help me give me your number if you dont have any problem.

Re: Setting Up VB API

I am able to get session object with Administrator access but on same system, one of my colleague who is not having admin access rights is getting error of toolkitnotfound exception....

Appreciate any help on this..

Regards

Ketan

Re: Setting Up VB API

Hi

In general, running VBA apps in Creo does not require any local admin permissions.

However, before you can run any VBA apps you need to run the vb_api_register.bat on all clients; and this will typically require local admin (this .bat registers some DLL's required by the API)

The thing is that if you run the vb_api_register.bat on a client without local admin permissions there is no error message displayed and you may assume that everything is OK while in fact it is not.

Re: Setting Up VB API

Hi,

Thank you very muech for your concern on this issue.

We have run vb_api_register.bat with local admin permissions and same is allowing us to build project.

Issue we are facing is as below in detail:

Case - 1 :

- Working fine with Admin Permission but not working without admin permission. Exception we got is the different one for different users. One is getting toolkitcantmodify whereas other fellow is getting toolkitnotfound exceptions.

All of us are using same system and same code. We are running application from source code rather than double clicking on application executable.

Case - 2 :

- Working fine with Admin Permission as well as without admin permission on different computer used in case - 1. These all users are also referring same code which are used by people of case - 1 and runs application from source code.

Case - 3 :

- Not Working fine with Admin Permission as well on client location. These all users are also referring same code which are used by people of case - 1 and runs application using application executable.

To conclude, as per my understanding, it has nothing to do with admin permission once we have registered bat file. This has something to do with users and systems but i m not able to figure out what is missing.

Any help on this is most welcome.

Thanks and Regards

Ketan

Re: Setting Up VB API

Re: Setting Up VB API

Hi all,

How to ftech creo installed path in VB.net? is there any system commands like %temp% and %appdata%

 

 Fetching from environment variables is the only way? please let me know...

 

~Zynk

Highlighted

Re: Setting Up VB API

you have to write your own algorithm... here is what i wrote... hope it helps.

 

Public Shared Function CreoParametricRootDirectory() As String
Try
Dim dirLocalProgramFiles As String = IO.Path.Combine(Environment.GetFolderPath(Environment.SpecialFolder.ProgramFiles)).Replace(" (x86)", "")
Dim tProRootDir As String = ""
For intVersion As Integer = 1 To 100
For intRelease As Integer = 10 To 400 Step 10
Dim strRelease As String = ""
If intRelease < 100 Then
strRelease = "0" & intRelease.ToString
Else
strRelease = intRelease.ToString
End If
tProRootDir = IO.Path.Combine(dirLocalProgramFiles, "PTC", "Creo " & intVersion.ToString & ".0", "M" & strRelease)
If IO.Directory.Exists(tProRootDir) Then
Exit For
Else
tProRootDir = ""
End If
Next
If tProRootDir <> "" Then Exit For
Next
If tProRootDir = "" Then Throw New Exception("Unable to find Creo Parametric Root Directory.")
Return tProRootDir
Catch ex As Exception
Return ""
MessageBox.Show(ex.Message)
End Try

End Function

Re: Setting Up VB API

What if I installed Creo correctly with VB API options selected at install. Added the system environment variable 'PRO_COMM_MSG_EXE' pointing to <creo_loadpoint>\<datacode>\Common Files\<machine_type>\obj\pro_comm_msg.exe and used the vb_api_register.bat in the <creo_loadpoint>\<datacode>\Parametric\bin directory. However, the COMM reference still will NOT show up when trying to add to my project in VS 2017. Also, I followed the same setup instructions on another machine and it worked great. I am not sure what is wrong here but do you have any ideas?