Can LLB be called with Run-Time Engine?

[Foreshadow20]

Can VIs from a LLB be called with the run-time engine?

I have a version of the RuntimeServer that I built with TestStand if that can be an alternative way.

This is a reference to my other recent thread where I try to call a LLB from VBA (which is having issues with references such as LabVIEW.Application):

https://forums.ni.com/t5/Measurement-Studio-for-VB6/Excel-VBA-missing-References-with-LabVIEW-LLB/td...

Thanks

[Ben]

Yes but you have to ensure the llb is the same version as the run-Time and you are using the correct path into the llb.

Ben

[crossrulz]

---

@Foreshadow20 wrote:

Can VIs from a LLB be called with the run-time engine?

---

Assume the following, yes.

1. The VIs were saved without the "Separate From Compiled".  This way, the compiled code is part of the VI.  A pain for SCC, but works in this situation.
2. The VIs were saved in the same version of LabVIEW as the RunTime Engine.
3. The VIs are not depending on anything hiding in vi.lib, instr.lib, etc.  Actually, any dependencies outside of the LLB could cause problems.

[Foreshadow20]

---

@crossrulz wrote:

---

@Foreshadow20 wrote:

Can VIs from a LLB be called with the run-time engine?

---

Assume the following, yes.

1. The VIs were saved without the "Separate From Compiled".  This way, the compiled code is part of the VI.  A pain for SCC, but works in this situation.
2. The VIs were saved in the same version of LabVIEW as the RunTime Engine.
3. The VIs are not depending on anything hiding in vi.lib, instr.lib, etc.  Actually, any dependencies outside of the LLB could cause problems.

---

Hmm I think I'll run into issues because I'm using a LLB to circumvent the issue that DAQmx 14.5.1 is not compatible with VBA/VB6.

The drivers of DAQmx are installed on the target computers. Most of the target computers have DAQmx 9.3.x, however some have DAQmx 14.5.1 (which my dev also has). 14.5.1 is the latest version that I can use with LabVIEW 2011. 

I'm now assuming to have the same issues if I build a DLL, which was my second backup option that I already started to investigate.

Should I then create one or multiple *.exe that are executed through VB with arguments? Assuming it is possible to get returned values from a LabVIEW *.exe (without going through a file or registry).

[Ben]

---

@Foreshadow20 wrote:

---

...

Should I then create one or multiple *.exe that are executed through VB with arguments? Assuming it is possible to get returned values from a LabVIEW *.exe (without going through a file or registry).

---

We are approaching the outer limits of Kludge-land so gird up your loins.

It has been ages since I was asked to do so but...

LabVIEW application can expose an ActiveX interface. It is a check box in the build spec somewhere.

If you develop the code in the LV exe with the functions you need, you can poke a prod at the exe using ActiveX.

Ben