inconvenience with application buiilder

[L.Steen]

Hi

I'm developing a quite large DLL (12MB+) in LabVIEW for use with an application also built in LabVIEW.

But I get two inconveniences when I use the DLL. Both only exist during development, not for the built .EXE file.

First when I load my application LabVIEW will display a number of warnings about VIs expected to be in vi.lib\config.llb, vi.lib\error.llb and vi.lib\inputdevices.llb but was loaded from inside my DLL instead.

And secondly, when I exit LabVIEW I get another set of warnings about VIs inside my DLL that were changed due to sub-VIs having moved. I get a prompt to save them, but of cause I can't since that would require writing to the DLL interiors.

Can I avoid this?

Is there for instance a way to not include the vi.lib\ LLB's when building a DLL?

BTW we're running on Windows2000 and XP.

I'm using LabVIEW 7.0 and have previously applied the work-around described in message 39BCEA2Q "Why Do I Get Error 1073 When I Build a LabVIEW Executable?" http://digital.ni.com/public.nsf/websearch/FB74F4EB7229D87786256E92006580B7?OpenDocument.

Kind regards

Lasse

[mohadjer]

Hi Lasse

I have tried to reproduce your problem by using some VI's from vi.lib in my DLL which I reused in my VI but it does not give the error you have been seeing.

Try removing the DLL from the VI and reopen the VI. Make sure it finds the subVI's from vi.lib. Then force a compile on the VI by pressing ctrl+shift and the run button in the VI. Make sure to save the VI. Insert the DLL in the VI again and see what happens.

The DLL and EXE files will include all subVI's in a VI including the subVI's from vi.lib. If the subVI's are linked to the VI's in vi.lib you should not see that problem.

You could eventually reorder the search paths given in LabVIEW, that might help too, knowing to look in the vi.lib before searching any other place. But not sure since it might look to load the DLL before the other subVI's.

Regards

Mohadjer

NI-DK

[L.Steen]

Thanks. I'll try that.

I have previously had some success with removing/deleting the DLL, opening the EXE project and saving all the VIs, and shutting down again. This would solve the first of the inconveniences that I mentioned, but I still got the option dialog to save the VIs encapsuled inside the DLL upon exit. This seems to only happen after I've modified the EXE project, though.

And it'll only work for a limited time. Suddenly the dialogs upon load reappears...

Best Regards

Lasse