Report generation in remote panel

I am using webpublishing tool, i have report button in my front panel,when the clients clicks the Report button the popup for saving the report is coming in the Server.I want the popup should come in the respective client machine so that the user can save or print the report.
Thank You

I don't think LV is going to be able to help you with what you need to do. If you want the report to be generated on the client side of the interface you need some sort of clent-side scripting (typically JavaScript) to implement that functionality. The links to the files containing that scripting need to be incorporated into the HTML page that the user sees when they access onto the site.
With a conventional webserver, this sort of thing is pretty easy. Unfortunately, if you are using the webserver deployment option in LV I don't know how you'd do it, or if it's even possible.
Better news is that there are packages like XAMPP that can install a fully functional webserver on a computer from a single installer. You will need to learn at least a dabble of a couple new languages (PHP and JavaScript) but they aren't very hard. Let me know if you would like to hear more about that approach.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Similar Messages

Using remote machines for report generation

Since LabView does not have cross-platform openoffice support, I was looking at ways of generating reports from a LabView session (2010) running on a mac. The report generation VI contains a somewhat suggestive machine name input. Can one connect to a remote machine (which is windows XP and has microsoft word / excel installed) to generate reports from a mac running LabView ?

m-s wrote:
Since LabView does not have cross-platform openoffice support, I was looking at ways of generating reports from a LabView session (2010) running on a mac. The report generation VI contains a somewhat suggestive machine name input. Can one connect to a remote machine (which is windows XP and has microsoft word / excel installed) to generate reports from a mac running LabView ?
With some work I think is is do-able.
If the PC had an exe deployed and running that was served via VI Server the report could be run and generated on the PC when invoked from the Mac.
So in theory yes!
Edit:
VI server is not required if the exe on the PC listens at a TCP/IP port and supports a protocol to accept the report "job".
I'll watch to see (and in hopes of) a better solution form others.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Report generation toolkit 1.1.2 doesn't show up on the panel

I installed Report Generation Toolkit 1.1.2 together with the Labview 8.5. But when I looked into the function panel, it didn't show up. No Labview has been ever installed on this machine. However when I went to control panel "Programs and Features"-> National Instrument, it did show the "Report Generation Toolkit for Microsoft Office 1.1.2" there. So I guess it did install it, but how can I add them into the function panel. Btw, my system is Vista.

Hi lshi,
Glad to hear that reinstalling the Report Generation Toolkit resolved
the problem. To answer your question, the installer prompts for an
installation directory to allow users with multiple versions of LabVIEW
to select a version other than the latest.
Peter K.
National Instruments

Report generation toolkit and signal express user step : problem of closing reference in "Stop" event

Hi all,
I'm trying to make a package of Vis to easily make Excel reports with Signal Express. I'm working on LabVIEW 8.2.1.
I'm using the report generation toolkit, so I build a .llb from my project which contains all the hierarchy of my steps, but also the hierarchy of dynamic VIs called.
I have made some steps, like "Open Workbook", "Write Data", etc.
My steps run well, excepts one step : "Close Workbook".
If my "Close Workbook" step is firing on "Run" Signal Express event, I have no error, so my reference is properly closed.
But if my "Close Workbook" step is firing on "Stop" Signal Express event, I have an error "1", from "Generate Report Objectrepository.vi".
I feel that I'm trying to use a reference which has been killed in the "Stop" step...
I would like to know what exactly do Signal Express on "Stop" event and why my close function does'nt run well.
Thanks,
Callahan

Hi Callahan,
SignalExpress (SE for short) does the following on the Stop event:
1. Takes the list of parameters that SE found on your VI's connector pane, and sets the values that the user set from the "Run LabVIEW VI" configuration page, if any.
2. Then tells the VI that SE is running the Stop event by setting the Enum found on your VI's front panel. This in turn should produce some boolean values telling your VI to execute the Stop case.
3. The VI is then run, with those values and states.
4. SE checks to see if any errors where returned.
5. Since this is the Stop event, SE releases the reference to the VI which it possesses.
Questions for you would be, is the reference to your Workbook linked to a control on your connector pane, or held in a uninitialized Shift Register. If it's held in a Shift Register, SE would not be aware of it, and would not be able to affect that reference.
Hope that helps. Feel free to post your LLB if it doesn't.
Phil

LabView Exe Application file not launch Excel application for report generation

Dear All,
I created one LabVIEW application file for report generation (using Excel Template).
While I run the program in programming mode it works well and create the report file in the specified path.
After creation of the application file(exe), it gives the correct path of where the excel template is placed. The same path is given to New Report.vi, but it gives the error 'File Not Found'.
Tell me, is any other configuration required for generating Excel reports? (During exe application mode)
Give me the solution.
Thank You
Jegan.

Hello,
Most likely you are encountering a problem of stripping and/or building paths. Probably the easiest thing to do is put a couple indicators on your front panel for the path or paths you care about, build your exe, and make sure you are really using the path you'd like. If you always put the report at some deterministic place relative to the exe (that is, even it the exe is moved, it will go with the exe and remain in the same relative path location, then you can use the Current VIs Path funtion found in the ... File I/O -> File Constants palette as a start path (where you will want to strip at least the exe name off of course).
I think this will bring some clarity to the issue!
Best Regards,
JLS
Best,
JLS
Sixclear

Report Generation & image

Hello,
I have been using Report Generation VIs to print Control/Indicator (Front Panel)icons on Word Document. The only issue is that it is so white that it blends with the background (example attachment below). Any suggestions.
Also, how can I use Report Generation VIs to print items (i.e. case structure and the items within it) from Block Diagram into Word Doc.
Thanks.
Attachments:
DocumentPicture.doc ‏24 KB

To answer your second question about inserting a Block Diagram image into your report, one way to do it would be to use a VI Invoke Node with the method Block Diagram >> Get Image Scaled to output Image Data for your Block Diagram (or whatever VI's Block Diagram you wire the VI refnum in for). Then use Draw Flattened Pixmap to change the Image Data format into a picture format that you can wire to a picture control. Then create a reference for this picture control and wire it into the Report Generation Toolkit VI called Append Control Image to Report. That will accomplish what you want.
I'll attach an example below, but unfortunately I only have the Report Generation Toolkit installed for LabVIEW 8 right now. I'll also paste the image below so you can get an idea of what I'm doing.
Message Edited by Jarrod S. on 04-14-2006 01:27 PM
Jarrod S.
National Instruments
Attachments:
ReportGenBD_Example.vi ‏20 KB
Screenshot.JPG ‏57 KB

Report generation tool kit not printing

I had the report generation tool kit version 1.01 for some time but never used it. I was comfortable with printing front panel vi 's.
But now I installed it on my computer with a windows 2000 and LabView 6.02 .
I created an application (executable) that will print (using the report
genartion tool kit). The application works fine in my development computer
(win 2000).
When I installed it on another computer with a win 2000, it prints as
expected
but when I try to exit I get a message from windows that the application is not responding (I have to go to task manager and terminate the application).
Both computers have word and Excell installed
I installed the application on a third computer (win 2000), but this com
puter does not have word or excell installed. The application does not print the
portion of the software that uses the report generation tool kit, but it can print the front panel of vi's (set to print an end of excution).
In all 3 computers, I have runtime engine 6.02 installed. My vi is simply
the example vi ""Sample test report.vi"", but customized to my application, printing standard report.
What is happening ?

Based on what you sent, the version of Excel and Windows that are being used is a non issue since none of the code makes any calls to either one. They all refer to the older version of the report generation VIs that use NI's proprietary report generator.
I can think of two explainations. First, you aren't using what you think you are. Second, NI retained the same VI names when they went to the Word/Excel version of the generator, and I am linked into the old version.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Report generation problems on the WinNT target machine

I'm using report generation VI's to generate a standard report, mixed with text and graphs.
In development mode (LV 6.0.2; Win-NT 4.0 SP6)there are no problems to print it. As soon as I make an application (application builder 6.0) and transfer it to the target machine (Win-NT 4.0 SP6; run time engine 6.0.2) I get an error -2147352567 unable to load picture..to Append front panel image to report.vi> If I delete the VI "Append front panel image to report.vi", I can print the text of my report without problems. Do you have any idea?

I could fix the bug in the meantime. I had installed an older version of the Internet Explorer. When I updated the target PC to Internet Explorer Vers. 5.5, there are no problems anymore. I think it must be a problem of ActivX.

Report Generation Tutorial, cannot find Rename Worksheet VI, Add Worksheet VI,

Report Generation Tutorial, cannot find Rename Worksheet VI, Add Worksheet VI,Get Worksheet VI, Append Table to Report. I have the Report Generation Toolset, where can I locate these VI's

Hello Jim,
First check to see if you have the Report Generation Toolkit installed. You can check by going to your Windows Control Panel >> Add/Remove Programs >> National Instruments >> Change. If you don't have a NI LabVIEW Report Generation Toolkit entry in the list that appears, then go ahead and reinstall your Report Generation Toolkit.
If you do have an entry for the Report Generation Toolkit, check to see if you have support installed for your version of Office. You can do this by going to your Windows Control Panel >> Add/Remove Programs >> National Instruments >> Change >> NI LabVIEW Report Generation Toolkit >> Modify. From there, you can install support for the necessary versions of Office.
If neither of those options work, I
would uninstall and reinstall the toolkit from the Add/Remove Programs utility.
Wendy L
LabWindows/CVI Developer Newsletter - ni.com/cvinews

Error -2417417851 using Report generation toolkit

I try to use the Report Generation toolkit (Version 1.0.1) for MS Office und the example "Generate Report from Template (Excel).vi" return an Error -2417417851
I run Labview 6.02, on Win2000 German, and use Office 97 (Everything is installed (included MS Graph))
Did someone experienced such a problem and found a solution?
Thank you for your Help!

Is LabVIEW and Office both German? Under Control Panel >> Regional Options >> General, is the language set to German? How about under Regional Options >> Input Locale? Reboot if you make any changes.
I would suggest reregistering the nireports.dll. It is located in the National Instruments\Shared\NI Reports directory.
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/4f811a9b23f1d46e862566f700615b7a?OpenDocument
Next, mass compile (Tools >> Advanced >> Mass Compile...) the LLB's in the \vi.lib\addons\_office
Chris_Mitchell
Product Development Engineer
Certified LabVIEW Architect

Can't print to Epson TM-U590 Slip Printer from Report Generation Toolkit with LabVIEW 8.6.1

Hi all,
I have an application that uses the Report Generation Toolkit to print tickets to a docket printer. Usually this works fine - I have 8 existing installations where there are no problems
I'm currently installing the software at a new site that uses an Epson TM-U590 slip printer and I can't for the life of me get printing to work
Using a Standard Report, the Print Report.vi returns error -41002 which indicates it can't find the printer. I've opened up the VI using remote debugging and it does find the printer name correctly with the Query Available Printers.vi. It gets an error code -2147352567 from the Printout node, which then gets replaced with the -41002 error which is reported.
For historical reasons I'm still using LabVIEW 8.6.1 for this project. I'm considering moving to 2011 or 2012 but I've had reliability issues with other parts of the application after attempting to update to a newer LabVIEW version so I'd like to avoid that at this stage.
The application is running on a standard desktop PC with Windows 7. The slip printer works fine if I print to it from Notepad, and my application is happy to print to any other printer, just not the slip printer.
The slip printer is using the LPT port. Previously the docket printers I've used have been USB but I would expect the printer driver to hide this detail from the application...
Any ideas would be much appreciated
Cheers
Brett
Senior Software Development Engineer
Certified LabVIEW Architect and LabVIEW Champion
Solved!
Go to Solution.

I've managed to sort out the problem, thanks to this KB article: http://digital.ni.com/public.nsf/allkb/67D60209102E2161862568AC0074BF64
I'm now having the same issue with a Star docket printer (a TUP592), this time with another program developed in LabVIEW 2011.
As mentioned in the article, the problem is actually to do with the margin settings rather than the printer name, despite what the error message says
After some experimentation, I've gotten the Star printer to work by setting a large (>14cm) right margin. No idea why this is required as it seems to print right up to the right edge of the paper quite happily, but there you go.
So I haven't defintely fixed the original problem yet as I haven't gotten back to the site, but hopefully this will be of some help to someone else.
Cheers
Brett
Senior Software Development Engineer
Certified LabVIEW Architect and LabVIEW Champion

Report generation microsoft tools missing in LV 8.5.1

I upgraded LabView from 8.5 to 8.5.1 and installed all of the toolkits. all of the toolkits seem to be working except for the report generation toolkit as the menu doesn't show any of the word or excel options.
Has anyone else had this problem?

Hi there,
I had this problem too. But fortunately others had posted their problems to various message boards and I was able to solve it easily.
I didn't try Andrey's method. (It may be faster)
I went into Windows control panel --> Add/Remove Programs --> National Instruments. When you select that, another menu opens so that you can select which component to remove. I uninstalled the Report Generation Toolkit and then re-installed. Worked just fine.
Patrick Allen

LV 2011 Report Generation Toolkit Constantly asks for 8.6.1 CD

I am having a strange issue.
Its a bit intermittant, so I will try my best to explain when it occurs.
-If I make a new project and run something from the report generation toolkit, I will get an installer from labview 8.6.1. I am running Labview 2011 and have never had 8.6.1 installed on this computer. It will spend about 3 minutes installing something, then demand a labview 8.6.1 CD.
-If I hit cancel it goes away for the project, until I restart the computer. It does not actually need the CD, it just asks for it. The VI containing the report subvi will execute fine, but if I open any of the front panels I get the installer message again.
-If I have run something that uses the report generation toolkit previously in this login session I do not encounter the bug.
-Restarting labview does not make it appear, only restarting the computer
Solved!
Go to Solution.

There are classes in the RGT that are loaded dynamically. You need to include the VIs in your build.
We found you should add the following two folders to your project and then force them to be in your EXE build.
<LabVIEW>\vi.lib\Utility\LVClass
<LabVIEW>\vi.lib\Utility\NIReport.llb
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Report Generation Toolkit - Error message rpcrt4.dll

Hello
My labview app. calls functions from the Report Generation Toolkit. I tested the runtime version, and this work fine under in Windows NT and Windows 2000, but does not work under Windows 98. I got and error message say "rpcrt4.dll Page not valid" that seem come from Windows and is related to a Remote Procedure Call. I already check the version of this dll 4.71.2900

The rpcrt4.dll is part of the DCom98 package. I have seen other problems, unrelated to LabVIEW, with this .dll arise when other programs have installed different versions of some of the DCom DLLs. You may want to consider trying this program out on another Win98 machine, or you may want to search through the Microsoft Support page for errors with this dll, specifically with the error number in the message you receive. The ones that I have seen have suggested restoring the DCom dlls to the original ones from the Win98 disk. There is also an update to the DCom components for Windows 98 (version 1.3) on the Microsoft website.

Report generation toolkit (1.1.2) and 8.5

I am not as crazy as I thought!
I wrote a program today that collects data from excel reports in many directories using cell names and it worked well. Unitl I saved it. I had been saving the sub vi's, but when I went to close them I got a message about unsaved changes and I guess I clicked to save the changes today. The program never worked the same again. I would get errors like 41106 and 41110 at random (problems with excel not opening and other stuff). I tried adding waits which slowed everything down and worked mostly. But the only way to not drop data and get errors was to have a copy of excel open while getting my data.
Well I just uninstalled/reinstalled the toolkit and rebuilt the vi that was having problems with the fresh install and everything is great again. So my question is why does the toolkit have problems when I save it in 8.5? The warning does say that the vi's are from 7.1 and I cant find any updates so I am hoping this is the latest version that came with my 8.5 suite.

Hi Bryan,
There should not be a problem with saving the VIs from the Report Generation toolkit in LabVIEW 8.5. I have checked the readme files to make sure but RGT 1.1.2 should work with any version of LabVIEW later than 7.0. However, the readme does discuss an specific upgrade issue. It says if you previously created VIs that use the built-in Report Generation VIs in LabVIEW Professional, Full, or Base packages or VIs from a previous version of the Report Generation Toolkit, installing the Report Generation Toolkit 1.1.2 might break the VIs you created. If the VIs you created contain any of the following VIs, edit them so they are compatible with the Report Generation Toolkit 1.1.2.
Append Front Panel Image to Report VI—The Image Format input of the LabVIEW 6.1 version of this VI is a different enumerated type than the current toolkit version. Right-click the input and select Create»Control or Create»Constant from the shortcut menu to create a compatible control or constant.
Append Table to Report VI—The connector pane position of the show grid lines input changed from the Report Generation Toolkit 1.0.1 version of the VI. Reconnect the original wire to the new input location.
Get Report Settings VI—The cluster order of the font settings input changed from the Report Generation Toolkit 1.0.1 version of the VI. Right-click the output and select Create»Indicator from the shortcut menu to create a compatible indicator.
Report Express VI—If a VI includes the LabVIEW built-in version of the Report Express VI on the block diagram, the VI breaks after you install the Report Generation Toolkit 1.1.2. Double-click the Report Express VI to launch its configuration dialog box, then click the OK button. Reconnect all wires to the Report Express VI.
You might need to relink the following subVIs after installation because the connector panes changed in the Report Generation Toolkit 1.1.2. Right-click the VIs and select Relink to SubVI.
New Report
Dispose Report
Append Front Panel Image to Report
Append Hypertext Link Anchor to Report
Append File to Report
Append Horizontal Line to Report
Set Report Font
One thing that might have happened is if you had created the program in an earlier version of the toolkit, then saved it in the new version of the toolkit, maybe some of the upgrade issues regarding the VIs listed aboved cause LabVIEW to start giving you errors. Also, which version of excel are you using? After you re-did the VI program, have you tried to save it again and see if the same problem occurs?
Carla
National Instruments
Applications Engineer

Report generation in remote panel

Similar Messages

Maybe you are looking for