Academic Company Events Community Support Solutions Products & Services Contact NI MyNI
4 ratings:
 2.5 out of 5   

How Do I Save VIs in a Library File (.llb) Without Using a .vi Extension?



Primary Software: LabVIEW Development Systems>>LabVIEW Full Development System
Primary Software Version: 6.0
Primary Software Fixed Version: N/A
Secondary Software: N/A

Problem:
I developed a large set of libraries containing VIs with unique file name extensions using LabVIEW 5.0. After upgrading to LabVIEW 6.0, I can no longer save VIs using my unique extensions, such as .run or .dat. In LabVIEW 6.0, is there a way to maintain my unique file name extensions when saving VIs in a library file?

Solution:
In LabVIEW 6.0, VIs saved in a library file have a mandatory default extension of .vi. If a file has another extension, LabVIEW appends .vi to the filename when you save it in the library. For example, start.run becomes start.run.vi.

To work around this issue, you must save a file individually and then immediately save it to the library without making any changes. This workaround succeeds because LabVIEW does not query a recently saved file for a new name when subsequently saved to a library file.

If your VI already exists with a unique extension in the library file, select File»Save instead of Save As or Save with Options and then Development Distribution. If you are creating a new VI or if you need to change the name of an existing VI, complete the following steps.
  1. Save the VI to a temporary directory by selecting File»Save As.

  2. Save the VI with the desired extension, such as "test.run". Use quotation marks around the filename to force LabVIEW to save your file without a .vi extension.

  3. Save the VI to the library file by selecting File»Save with Options, selecting Development Distribution, and clicking the Save button. In the dialog box that appears, you can select an existing library file or create a new one.


Related Links:
LabVIEW 2010 Help: Saving VIs KnowledgeBase 642C0D28: How Do I Extract Files from a LabVIEW Library File (LLB)?

Attachments:





Report Date: 08/06/2001
Last Updated: 12/04/2013
Document ID: 2C5C7HON

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