DLL (built in LV) dependencies?

[jojp]

Hi,

form some reasons I made a DLL with some functionality (read xml files, start VI by VI server).

I use this DLLs within a other VI (lets call it main.vi) by calling it in a CLF.

This used to work fine. I read xml files and opened some client.vis through this DLL.

Now I brushed my client.vi a bit. I reads now also xmls files utilizing NI_XML.Lib.

No I get a broken arrow, but no error message when executing the main.vi and calling the client.

The only to get the error message is to put main.vi and client.vi into the same project and execute main.vi.  After calling client.vi via DLL, close the vi once again and reopen it from project window.

[jojp]

Is there any possiblity to use a common LabVIEW Function like xml and error handler in DLL and a VI in LabVIEW at the same time?

Thanks for every suggestion. 

[jojp]

Someone has had this problem before 

http://forums.ni.com/ni/board/message?board.id=170&message.id=166412&query.id=4790265

Did anything change since then. 

[MikeS81]

Hi jojp,

can you rebuild this behaviour in a smaller project, which you can upload? Which error message did you get?

Does the information from the other link help?

Mike

[jojp]

Hi Mike,

here is a smal test programm which repoduces my problem.

Error numer is 1003: Vi broken.

It runs from : C:\Sourcen\labview\projects\

This mean the vi server path in the dll is hard coded to C:\Sourcen\labview\projects\test\client.vi

But I also included sources for the dll.

Best regards

Helmut 

[DianaS]

Hi Helmut,

the suggestions in the other Link:  http://forums.ni.com/ni/board/message?board.id=170&message.id=166412&query.id=4790265

are the solution because Labview can't load 2 VIs with the same name in memory.

In your case its hard to use unique names for the VIs because they are passwordprotected and

you may not be able to access the SubVIs.

But perhaps you can build the dll with another labview version as suggested.

[jojp]

Hi Diana,

thanks for your suggestion. I help my self now by seperating the main.vi which utilizes the DLL and the client.vis which are called on runtime through VI server.

It´s important to use the "Open Application  Reference" VI.

Now I can also build a application from my main.vi which includes the DLL. For sure I still have to run the Development Environment to get the client VIs running, which is a perfect solution for me.