Report Generation Toolkit with Excel 2003 and Excel 2000

Hello,
I'm using the Report Generation Toolkit to generate an Excel report from an Excel template.
The "NI_Excel.lvclass" is included in the "source" section of the application builder options.
I create an exe file on a PC where Excel 2003 is installed. On a Notebook, where only Excel 2000 is installed, the application crashes at the generation of the report:
I guess the problem is the different version of Excel but I don't know. On the developer PC with Excel 2003 it works fine.
In this document it's only talked about different Word versions.
How can I use the Report Generation Toolkit here?
I'm using it that way:
Regards

Oh, it seems that the Report Generation Toolkit "only" supports Excel XP/2003/2007.
I think, that's the problem.

Similar Messages

Problem for Report Generation Toolkit for excel 2000

Hi all,
Now I am Developing my program with Report Generation Toolkit 1.1.0 and Labview 7.1.
In my computer I am using Excel XP, and there is not any problem. But when I build to
a exe file, and use in a computer with Excel 2000, it didn't work.
And I try to check the source file in this computer, I found that there any some connection
error. And this is caused by the active X class. As I know Excel 2000 is using Microsoft Excel
Object Library 9.0, but i cannot find it in the list of active x. So it is using Microsoft Excel Object
Library with a very old verison. So in the property node there are missing functions, such as the
UsedRange in _Worksheet in the Excel_Get_Range.vi. However, In VBA, I can find the 9.0 Library.
Is it the problem of 9.0 library? How can I solve the problem? How can I upgrade the library to 10.0?
Thanks.
Regard,
Ryan

Hi Mike,
Since my program is for all the staff in office, everyone may use it.
I cannot call the whole office to upgrade the excel to XP.
And I think Report Generation Toolkit is alway support Excel 2000,
since the old version of it is not support for Excel XP.
Regard,
Ryan

Report generation toolkit with excel 97 Graphing issue

I am trying to set-up mu data output to use the report generation Vis. However I am running into a problem when trying to update 2 graphs on the same sheet in Excel.
My set-up is:
Windows XP
Office 97
LabVIEW 7.1.1 with the Office toolkit installed
I noticed that I can write to the first Graph and update it without issues, but once I try to update the second I get error -41105 stating that MSGraph is not installed.
I did notice that if I set a break point between the Excel Quit Graph.vi and Excel Update Graph.vi if I click the mouse within excel in removes the highlight border from the first graph, the I continue and it works fine. For some reason LabVIEW is not releasing that Graph to be able to select another.
I tried to write data to a cell after quiting the graph and then selecting the second graph but that is not working either although it does work manually.
Next I may try a Macro but I would rather not have to do that.
Any suggestions?
Jeff
Jeff D.
OS: Win 7 Ultimate
LabVIEW Version: 2011,2010,2009 installed
Certified LabVIEW Architect

Well after some debugging I found it. Apparently for Excel 97 only there is a problem that when you qiut MSGraph it may not save properly so the VI had the Quit Property removed.
I have added it into my code and it seems to work and will see how well it does and if I run into any problems.
Jeff D.
OS: Win 7 Ultimate
LabVIEW Version: 2011,2010,2009 installed
Certified LabVIEW Architect

Report Generation Toolkit, Print Excel Report, LabVIEW Crash

Hello,
when printing a report generated with the report generation toolkit for excel my build application crashes on our customers PC.
When I run this application on my PC it works fine.
The problem is the active X invoke node that trys to print the report but i cant get any error messages to find out where to locate the problem.
Maybe that there is a problem with the active X node or the Excel Version on the customers PC?
I use LabVIEW 2010 and Excel 2007 the customer has Excel 2003 SP 3.
I changed the report to generate it in Word where the Print_Report.vi fine on both PCs. But in Word Report there is called another active X invoke node to print the Report. So it seems for me that there really is a problem with the Print in Excel active X invoke node.
Mybe someon can help me in finding out whats the problem.
Greetings Daniel.
Solved!
Go to Solution.

Hi Daniel,
your behavior has been reported by others. For example:
Application Build Failure on Excel.Print Report call
http://forums.ni.com/t5/LabVIEW/Application-Build-Failure-on-Excel-Print-Report-call/m-p/1563242
Problem posted: 05-17-2011 02:19 PM
Workaround posted: 06-01-2011 and later
So their workaround was to use Excel 2007 or 2010 instead of 2003. Is this working for your customer?
Best Regards,
Jan

Report generation toolkit with openoffice

hello all
i would like to know if it is possible to use the report generation toolkit with openoffice instead microsoft office? because i do not have the toolkit already i can't test it and i will only buy it if this is possible...
i ask also because i used another application with word export not long ago what was ending with the error message "windows ole server not found". so the question is if something of the microsoft product line is necessary? i am quite sure that the opening of a produced doc would be possible in openoffice without problems - at least i hope so!
only one thread i found, unfortunately in french : http://forums.ni.com/ni/board/message?board.id=4170&message.id=13060&query.id=139594#M13060
thanks a lot, mischl

Another option to consider is to use the report generation VIs that ship with LV and simply output to a PDF document rather than a hardcopy printer.
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 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

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

Office Report Generation Toolkit 1.0.1 and MS Office 2000 problem

Hello.
I'm tring to make a repot in word using a template..everything works just fine when in development..but when i make the executable the problem arises.
I get error code 7 (Cannot open vi reference) in NewReport.vi.. FYI i'm running the aplication in the same machine i'm developing.
I'm sure everything else is ok..- changed paths to work in executable, template in correct folder...i'm adding the necesary support llb to the executable(Win200), etc - ..i tried reinstaling office and the report generation toolkit but i still have the same problem...
How can i solve this?....
Thanks in advance for all yur help.

Well..that was a very good answer to my question...and it solved my problem. Thank you.
I thought that by adding just the llb as support files would be enogh..but now i see this is not correct..thanks again.

How can i create multiple page report using excel report generation toolkit from excel template?

i am having code which create report in excel.but it prints only single page. if content is more than size of template than insted of tacking new page it prints only single page.Please help me out.
Anyone has material for learning activeX in labview? Please mail me on [email protected]
PBP (CLAD)
Labview 6.1 - 2014
KUDOS ARE WELCOMED.
If your problem get solved then mark as solution.

Hi thanks for reply.....
PBP (CLAD)
Labview 6.1 - 2014
KUDOS ARE WELCOMED.
If your problem get solved then mark as solution.

Changing the Size of generated graph in excel report generation toolkit

Hi, i am trying to build a report generation vi for my Structural health monitoring system in which i need to export 3 graphs in to an excel report. The idea is to have the report on a single page, but when i paste them along with the ceiling and pillar deviation percentages, the report just exceeds the page limit. I wanted to know whether one can change the size of the graphs in excel? One can do it in word(tried that), but i dont want to use the bookmark option as it intend to put this up as a webservice in the next step. I am using LabVIEW 2009 Thanks.
LabVIEW 8.2,8.6,2009...still learning
Attachments:
Report Generation SHM.vi ‏30 KB

Hi,
I haven't tried this myself, but looking through the report generation toolkit the "Excel format image VI" (in the Excel specific tab of the Report Genertaion window) looks to be the one you are after. The help entry for the VI says to: "Use this VI to format any type of image in a worksheet, including front panel images, images from a file, and graphs"
Hopefully this will help.
-CC
"If anyone needs me, I'll be in the Angry Dome!"

Problem with report generation toolkit when installed new office 2010

Dear all, I had LabView 8.6.1 and report generation toolkit for MSoffice 2003 perfectly working in my laptop.
Now I have added MSoffice 2010 and report generation toolkit does not work anymore since it is linked to new office.
How can I inform Labview to link report generation toolkit to the old MSoffice 2003?
regards
Max

The Report Generation Toolkit is ActiveX based. When you install the newest version of Office it registers the ActiveX server for that software, which the toolkit adapts to and uses.
Uninstalling Office 2010 would solve the issue, otherwise you will need to look at unregistering the 2010 component of Office ActiveX - but I'm not sure if that's possible.
Regards,
Peter D

Error 10 when building an application in LV8 and Report generation toolkit 1.1.1

I am trying to build an application using LV8.0.1 and Report generation toolkit 1.1.1 and i get this error.
Error 10 occurred at ABAPI Dist Copy Non-VI Files.vi -> ABAPI Dist Build LLB Image.vi -> ABAPI Copy Files and Apply Settings.vi -> EBEP_Invoke_Build_Engine.vi -> EBUIP_Build_Invoke.vi -> EBUIP_Build_Invoke.vi.ProxyCaller
Any ideas?
Scientia est potentia!

Did you attempt to add the _wordsub.llb and _excelsub.llb files to the application as support files? I believe in LabVIEW 8.0 instead of adding the entire LLBs you should just add the _Word Dynamic VIs.vi and _Excel Dynamic VIs.vi as dynamic VIs. I think I've seen a similar post on the discussion forums in the past that recommended this.
If this suggestion doesn't help, please reply, and attach a simple VI and .lvproj file demonstrating the problem so I can investigate further.
Good luck,
-D
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Control checkbox form field in word with report generation toolkit for Microsoft office

Hi all,
Happy New Year!
I insert in the word template the check box form field. It has a bookmark name "Check1".
Now I'm trying to checked or unchecked this field using the report generation toolkit for Microsoft office and I couldn't. If anyone now how to do it? I'm using LabView 8.0
Thanks in advance,
Boris
Solved!
Go to Solution.

Boris,
The Microsoft Office Toolkit does not have support for checking/unchecking check box forum field. You would have to research the activex functionality that enables this to be checked or unchecked and then do the activex calls yourself. I did hear of one csutomer who used a special font to write a blank box or a checkbox into a word document and changed it that way as well.
Maybe http://www.ozgrid.com/forum/showthread.php?t=53715 gives a hint to an activex reference
Rob K
Measurements Mechanical Engineer (C-Series, USB X-Series)
National Instruments
CompactRIO Developers Guide
CompactRIO Out of the Box Video

I am using report generation toolkit 1.1 with Labview 7.0 and Office 2003 professional. The create new report VI opens Excel but throws error (-2147167262- from automation open VI) when I try to open MS word. please help...

I am using report generation toolkit 1.1 with Labview 7.0 and Office 2003 professional. The create new report VI opens Excel but throws error (-2147167262- from automation open VI) when I try to open MS word. please help...

Hi Leo22,
Does this error occur if you use any of the example programs that come shipped with LabVIEW? I would try opening one of the examples that write data to Word and see if those give you an error. Also, have you tried just putting down a New Report.VI and change the report type to Word? If this simple vi (that's all you need to open Word) breaks, I would check to see if there are any instances of Word still open. Check the task manager to see if any word processes are still open. There should not be a problem accessing Word 2003 from LabVIEW 7.0. If neither of these solutions work, please give some more detail about your application and we can research further. Thanks!
Jeremy L.
National Instruments
Jeremy L.
National Instruments

I can't transfer data properly to Excel 2003 with the report generation toolkit.

I have a table with number to transfer into Excel. I use EasyGraph.vi and it works correctly with Excel 2000. But when I try the same program to transfer my data into Excel 2003, the data are not transfered correctly. When I have for example 0,56, it is read as text in Excel and when I have something like 53,300 Excel 2003 read this 53 300 as if there was no coma.
Do you know what's happening with Excel 2003 ?

Separators have always been a pain in Excel !
A work around is to avoid using any separator at all, and to format numbers as power of 10.
For instance :
0.12345 -> 12345E-5
12.345 -> 12345E-3
The attached vi does the trick.
Chilly Charly (aka CC)
E-List Master - Kudos glutton - Press the yellow button on the left...
Attachments:
NoSeparatorEnumbers.vi ‏20 KB

Report Generation Toolkit with Excel 2003 and Excel 2000

Similar Messages

Maybe you are looking for