Problems with calling al dll inside a dll called by LabVIEW

[becktho]

Wow - I like your attitude about that topic.

We might unit and start some kind of crusade ;).

Maybe we find some more knights of the wire :D.

Thomas

[chrisger]

Hello again....

well, one thing has been untried by now: build a LV - executable and see what happens!

And guess what:

The LabVIEW - Code that produces rubbish data when executed in the LV - Environment does a pretty well (and correct!) job when called as an executable!!

And thats for both COM - automation and Call Library Node with DLL B!!

hmmmmmmm......

.. i think you both should wait before you get out and start to kill some innocent people on your crusade ..

anyway: such things shouldn't happen! and now i think its a problem of the LV - IDE, because thats the only environment for the 3Party code where the rubbish data occured!


best regards & thx for all the answers
chris

[becktho]

By now it's getting really strange.

I already had problems using simple dll's.
But these problems occured in the executable and not in the LV-IDE (the reason for the problems were path-settings in the dll-configuration).

Well - I think it still has something to do with dependencies which are correct in the executable and unfortunately are incorrect in the IDE.

[rolfk]

---

i think you both should wait before you get out and start to kill some innocent people on your crusade ..

I'm not for killing people, innocent or not. Just put them through their paces on the rack 😉

Rolf Kalbermatter