Academic Company Events NI Developer Zone Support Solutions Products & Services Contact NI MyNI
This Document is not yet Rated  Rate this Document

Why Am I Prompted For the Location of lvalarms.dll When Running an Executable?

Primary Software: LabVIEW Run-Time Engine
Primary Software Version: 8.0
Primary Software Fixed Version: N/A
Secondary Software: N/A

Problem:
I have created an executable for my application that uses a Timed Loop function in Labview 8 but when I run the executable, it cannot find the path to lvalarms.dll and prompts for the location. Why does this happen and how can I fix it?

Solution:
Lvalarms.dll is associated with the Timed loop function and it is called in the DAQmx Create Timing Source VI. When executable is built with a Timed Loop function, the lvalarms.dll is added to the data folder in the application executable directory. There are two ways to get around this problem:
  • Manually browse to the data folder in the executable directory and select the lvalarms.dll. However, you will need to repeat this process every time you run the executable.

  • Add the lvalarms.dll as a supporting file with the executable. To do this, open the project explorer;
    1. Right click on “My Computer” in the project explorer and select Add File, browse to
      “C:\Program Files\National Instruments\LabVIEW\8.0\vi.lib\Platform\TimedLoop”
      folder for lvalarms.dll.
    2. Right click on Build Specification and select “Application (EXE)”.
    3. In the Source File option, move the main VI into the StartupVI.
    4. Move the lvalarm.dll to the Dynamic and Support Files. (Figure1).


    5. Figure 1: Add lvalarms.dll to Supporting Files.

    6. In the Source File Settings, select “Destination Directory” in the “Destination to Apply” for lvalarm.dll (Figure 2).


    7. Figure 2: Change lvalarms.dll destination directory to the executable directory

    8. Click the “Generate Preview” button in the Preview category, to view the directory structure for the executable. It should be similar to Figure 3. It is important that the lvalaram.dll is in the sample directory as the executable.


      Figure 3: Executable Build Preview.

    9. Finally build the executable.


Related Links:

Attachments:


sourcefile1.JPG - sourcefile1.JPGsourcesettings1.JPG - sourcesettings1.JPGpreview.JPG - preview.JPG


Report Date: 04/13/2006
Last Updated: 05/07/2007
Document ID: 3WCFQF2M

Your Feedback! poor Poor  |  Excellent excellent   Yes No
 Document Quality? 
 Answered Your Question? 
  1 2 3 4 5
Please Contact NI for all product and support inquiries.submit