07-03-2012 03:20 PM
Making a long story short, I'm trying to create an executable in Labview that I can call from another Labview program via active x. I've been using the following article as my guide:
https://decibel.ni.com/content/docs/DOC-9647
It seems simple but I keep getting error 6945 saying that the VI name is no longer suffiencient. I've checked and rechecked the VI name that feeds VI path and I know it is correct. All I'm really trying to do is grab the VI reference so I can hide the front panel. Attached is a screenshot of the code and the error. Any thoughts?
Solved! Go to Solution.
07-03-2012 06:56 PM
Is your "Hamilton Control Server.vi" owned by a library (lvlib) or a class (lvclass)?
07-04-2012 07:20 AM
07-04-2012 10:16 AM
I would first try to run the executable and get the VI path by including "Current VI's Path" primitive in the VI. This is to make sure your calling path really matches what is in the executable.
07-06-2012 05:17 PM
Thutch,
TailofGon realy hit this one on the head. Once we have that information we will better be able to help you with your issue.
Regards,
07-09-2012 08:14 AM
I feel stupid now. I don't know why I didn't try that before. I've even done that same thing in the past. It was buried in folders I didn't expect. I'll have to go though the build spec and see why.
I did, however, find a better solution. What I'm trying to do in the long run was create a background process. This seems to be a much better solution.
http://digital.ni.com/public.nsf/allkb/EFEAE56A94A007D586256EF3006E258B
07-09-2012 09:51 AM
07-10-2012 05:26 PM
Hi all,
Tail, you are correct, this was changed in LabVIEW 2009. This link has a description of changes made in LabVIEW 2009; the name conflict within applications is addressed about halfway down.
http://zone.ni.com/reference/en-XX/help/371361F-01/lvupgrade/labview_features/
Thanks,
David B
07-10-2012 05:37 PM - edited 07-10-2012 05:41 PM
Thanks, dbell
This is such an awaited improvement and I am shocked that I did not know about it until now. I want to move to LV 2009 or later so that I do not have to expose bunch of VIs outside of executables. In LV8.6 if you use inheritance of LV Classes then conflicting name was inevitable as overriden VIs always have the same name as the parent method VIs (prefix does not fix it).
And I guess we need to add some comments on this page from PO >> https://decibel.ni.com/content/docs/DOC-9647
07-11-2012 03:18 PM
Thanks for the comment and notes Tail, updating these really helps all users of LabVIEW. I'm glad that this helped you out; I'm sorry that the information didn't get disseminated to you sooner. Hope it helps.
Thanks,
David B