LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Application Builder for labVIEW 7 Doesn't support any report generation function

I'm Using LabVIEW 7.0 to build an application My Application is exporting data to an excel report. the vis were working great until i tried to creat an .EXE file. The application is working fine but when i try to generate the report nothing happens.

So, I decided to test the report generation functions alone (New Report.vi, Append report text.vi and Dispose Report.vi). The Problem Still there, the .EXE file takes no action when i attend to generate a report. any suggetions please.
0 Kudos
Message 1 of 10
(4,166 Views)
If you are using the get base path function look at your path when you build the exe. An example path in the development enviroment C:\Temp\viA.vi. In an exe, C:\Temp\viA.vi\viA.exe. You will have to do a second strip if you are getting the base path.

Also if this doesn't solve the problem are you tracking any errors using the error cluster. If you are what is the error?

If these are not the causes please post the vi so we can look at it. Hope this helps.
BJD1613

Lead Test Tools Development Engineer

Philips Respironics

Certified LV Architect / Instructor
0 Kudos
Message 2 of 10
(4,166 Views)
Shady Yehia wrote:
> I'm Using LabVIEW 7.0 to build an application My Application is
> exporting data to an excel report. the vis were working great until i
> tried to creat an .EXE file. The application is working fine but when
> i try to generate the report nothing happens.
>
> So, I decided to test the report generation functions alone (New
> Report.vi, Append report text.vi and Dispose Report.vi). The Problem
> Still there, the .EXE file takes no action when i attend to generate a
> report. any suggetions please.

Another possible reason besides of possible path problems: Are you
running that application on the same computer? If not you need not only
to install the Runtime-Engine (automatic when you create an installer)
but also the Report Active X support.
To include that into the installer
you go into the Installer Settings Tab, then press the Advanced button
and make sure that you check the NI Reports Support checkbox before
creating an application build.

Rolf Kalbermatter
Rolf Kalbermatter
My Blog
0 Kudos
Message 3 of 10
(4,166 Views)
Hello,

These are all great suggestions, and I would like to add to them by mentioning that you can programmatically return whether the program is being run as an executable or a VI.

To do this, call the application property "App.Kind". This property returns whether the program is currently being run in the "Development System" or "Run-Time System". You can then use a case structure to use a different number of Strip Path functions depending on the system.

Hope this helps!

Liz F
National Instruments
0 Kudos
Message 4 of 10
(4,166 Views)
I've tried every thing. and still nothing works, so i'm sending you the following files:

1- test.vi: My VI
2- template.xls: My Excel template
3- report test.bld: My Build file

i'm using windows Me and Office 2000.

Don't forget to place template.xls on the "C:\" directory.

Thanks in advance
Download All
0 Kudos
Message 5 of 10
(4,166 Views)
Your example suggests you are using the report generation tool kit.

Then you have to add
_Word Dynamic Vis.vi from _wordrdsub.llb and
_Excel Dynamic VIs.vi from _exclsub.llb

as dynamic VIs on the source files Tab when you build the application

You find these on Labview directory\vi.lib\addons|_office\
Message 6 of 10
(4,167 Views)
Thank You guys very much. It worked beutifully..

Another Question Please..

My VIs was designed to work under office 2000, (that what I choosed when I installed the report generation tool kit, my excel template also was desinged by office 2000).

When i tried to run my VIs under office XP (on another machine) it didn't work. i recieved an error no. 41106 and the possible reason was:

"Report Generation Toolkit: Microsoft Word or Excel did not open. Make sure Microsoft Word or Excel is installed."

Is there any way so i can upgrade from Office 2000 to Office XP without much effort.

Thanks In Advance.
0 Kudos
Message 7 of 10
(4,166 Views)
The following KB discusses the error with having two different versions of Office when building executables. Ignore the 214... error number.
Error 2146959355 When Running Exe on Machine With Different Version of Office

After you install the new version of office on your development machine, you will need to uninstall and reinstall the report generation toolkit so that the toolkit installer will install the version of the VIs that work with your newer office.
0 Kudos
Message 8 of 10
(4,166 Views)

Hi all,

I have the same problem too.

I'm developping the application by using a MS OFFICE REPORT from a MS report generation toolkit. Then when I test and run my application, the results work fine, I can chose the location to save my excel file and then I can open the saved excel file to see my result. However, the problem arises when I try to built the .EXE file, it doesn't work. Even though, I've already added 2 dynamic VIs as follows:

  • _Word Dynamic Vis.vi from _wordrdsub.llb
  • _Excel Dynamic VIs.vi from _exclsub.llb

Could anyone advise how to solve this problem ? Additionally, I'm using LabVIEW8 and MS OFFICE EXCEL 2003.

Thanks in advance.

Pravee

Solimac (Thailand)

 

0 Kudos
Message 9 of 10
(3,758 Views)

If I recall correctly, the Report Generation Toolkit User Guide indicates some special steps that are required when building an executable that uses the MS Office Report Express VI.  Specifically, I believe you need to add the following two files as Support Files in your application before building:

[LabVIEW]\templates\Report\MSOffice_RGT_Template.dot
[LabVIEW]\templates\Report\MSOffice_RGT_Template.xlt

See if this helps,
-D

P.S. - If you're still having problems after reading this suggestion and the user guide, I recommend a more detailed description of the specific error you receive, along with attaching a simple project file and VI that demonstrate the behavior.

0 Kudos
Message 10 of 10
(3,746 Views)