Saving LLB fails - multiple files of same name

[JRy]

Hi,

When trying to save a new LLB, I'm given the following error:

"LabView: The save operation failed because multiple files of the same name cannot be saved into a single LLB. To correct this error, save to a folder instead of an LLB."

The problem seems to arise due to the fact that the drivers for 2 instruments, Keithly 24XX and Agilent 34401 contain common vi filenames. e.g. Initialize.vi.

For some reason, Labview doesnt seem to be able to distinguish between the two files when creating a new library, despite the fact they reside in different directories.

This is evident when one set of the vi's are renamed, the LLB can be created.

Has anyone encountered this issue before?

[smercurio_fc]

This is by design. An LLB is a flat file - thus it doesn't have a hierarchy. Consequently, if you try to put all the VIs from both drivers you will run into this conflict. I am assuming you are creating the LLB for distribution. This should be the ONLY reason for using an LLB. You should not be using an LLB to "hold" development code. Project libraries should be used for that.

For your particular issue you will need to create separate LLBs, or zip up the files into an archive.

However, the drivers should already come packaged as either an LLB (or multiple LLBs) if they were written pre-LabVIEW 8, or as a zip file, so it's unclear what you are trying to do with the instrument drivers. Or is this happening because you are trying to create a source distribution from your overall project, and you are using those drivers?

[JRy]

Thanks for the reply smercurio,

The LLB is being created for distribution.

So the only method of creating a single distributable file would be to rename all files causing conflicts?

@edit: replied before you edited your post.

Yes thats correct we're creainge a source distribution from the overall project.

In our case, would the best solution be to save to a folder structure instead of an LLB, then move the top level vi to the root directory?

So the user would just simply unzip the file and double click the top level vi.

[smercurio_fc]

That would probably be your best bet.