LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Excel 2000.lib

I currently have an application, written by someone else.  I am trying to create a Build Installer for the applicaiton.  Some of the VIs are in a folder called Excel 2000.lib folder and are a bunch of VI which access an Excel file for reading data from it.  This applicaiton works fine on the development machine.  Even the installed application works fine.  However, when I run the Installed application on another machine, it hangs at the point, where the Excel files should have been accessed. 

Should the files from the Excel 2000.lib folder have been in a Lib file? 

Is there a way to determine what files are included into the Installed Application, so I can verify all the files are getting installed with the application?  I have already run into this once, where another section of the code has a VI hardcoded into an Invoke Node VI and it doesn't get installed with the application due to not showing in the VI Hierarchy.  I fixed this by adding it as a Dynamic VI into the Application Builder, but I have yet to verify if all the files in the Excel 2000.lib folder were getting installed.  I intend to use Orca.exe to open the created .msi file to check it as well, but I would like an easier way to do this.

Thanks

0 Kudos
Message 1 of 8
(3,792 Views)
One other question, is the Excel 2000.lib archive normally distributed with the Report Generation Toolkit for Microsoft Office?
0 Kudos
Message 2 of 8
(3,790 Views)

There is no file called "Excel 2000.lib" that installs with the Report Generation Toolkit.  We have separate LLBs (not .libs) that contain Office version-specific VIs for use with different Office versions (as of the latest version of the toolkit, 1.1.1, we shipped support LLBs for Office 2000, XP, and 2003).  When you build an executable with the toolkit, you must add some dynamically-called VIs to the build when making an EXE.

So it sounds like whatever VIs you are using do not incorporate the Report Generation Toolkit.

-D

0 Kudos
Message 3 of 8
(3,782 Views)
I meant LLB file format.  I started trying to add the VIs one at at time, since there is not multiple selection option in the Builder version 7.0 (hear that NI, there should be) and it is cumbersome with 40+ files.

However, I am getting an error when trying to add some files that says NI 488 not installed or some such thing, so I don't include those.
0 Kudos
Message 4 of 8
(3,774 Views)

The Application Builder in LabVIEW 8.0 allows you to add multiple VIs from your project at once to your build.

-D

0 Kudos
Message 5 of 8
(3,768 Views)
awesome thanks.  Might be a reason to upgrade right there, but we shall see what ends up being the problem.
0 Kudos
Message 6 of 8
(3,765 Views)
I am using the report generation toolkit and also having problems getting the excel functions to work on the install machine.  The executeable works fine on the development machine but does not work on the application machine.

Using LabVIEW 8.2:

Source Files:
included _Excel Dynamic VIs.vi as a dynamic VI/support file

Source File Settings:
destination of _Excel Dynamic VIs.vi as inclusion type dynamic VI; destination applicaion.exe

Development machine has Excel 2000  (9.0.6926 SP-3)
Application machine has Excel 2000 (9.0.2720)


Thanks in advance,

Adam
0 Kudos
Message 7 of 8
(3,559 Views)
Nevermind, it works.

I had my template file installing to the wrong directory.
0 Kudos
Message 8 of 8
(3,542 Views)