Thank you, Ben and Greg, for your effort. But my solution for now is
not to use DLLs. I have only little time left for my project, so I
can't spend any time in this problem.
But to the idea with the wrapper VI: I don't believe that this would
help, because even the wrapper VI will run in the same n
Hi Ben,
thanks for your answer and the interesting link. But I think I have
the direct inverted problem to yours: You had the problem that a dll
called from VB runs in a different memory space than LV, so you have
no direct access to your LV application. But my problem is that a dll
called from LV
I have built a set of LabVIEW VIs to a DLL. Some of these VIs call
some of my own LV subroutines, e.g. read_ini.
When I call the DLL functions from a higher level LabVIEW program,
which also uses these subroutines, e.g. read_ini, I get some problems.
The DLL functions obviously don't find the subro
