Report toolkit et erreur 41110

Bonjour à tous et toutes,
Je voudrais essayer d'utiliser le module tookitreport, en particulier pour excel.
J'ai un soucis, en retour j'ai le code erreur 41110, en regardant de plus près l'erreur se situe au niveau de mon excel template.
Je ne vois pas trop ce que je dois mettre, dans l'aide sur le site pour ce code erreur il est écrit la chose suivante :
Problem:
When I use the LabVIEW Report Generation Toolkit to write data to a Microsoft Excel worksheet LabVIEW returns error -41110 even though the cell exists in the worksheet. Why does the error occur?
Solution:
The LabVIEW Report Generation Toolkit supports writing data only to the first worksheet in a workbook. To fix the error, make sure you write the data to the first worksheet.
Hors le fichier que j'ai mis, est juste un fichier excel vierge de toute case.
J'ai mis en piece jointe le classeur vierge excel et le fichier labview (le deux vi est pour labview 9.0, au cas ou).
Résolu !
Accéder à la solution.
Pièces jointes :
génération essai.vi ‏15 KB
essai.xls ‏14 KB
génération essai.vi ‏12 KB

Bonjour,
Vous n'avez pas de Worksheet "truc" dans votre document. En rendant ce string vide, vontre programme fonctionne:
Cordialement 
Florian Abry
Application Engineer Group Leader
NI Germany

Similar Messages

  • NI Report Toolkit VI's changed or missing in 8.5 compared to 8.2 and earlier

    I am trying to open an application I built in 8.2 in 8.5.  At this point I have managed to get all the toolkits installed to the right directories I think, but the NI Report Toolkit is very different with the 8.5 installation than it was in the earlier versions I have used.  I cannot load any of the report generation vi's I wrote in 8.2, because the new NIReport.llb does not contain many of the old vi's that my code is calling.
    So far I have found these inconsistencies:
    Append Image to Report (path).vi theoretically has been changed to just Append Image to Report.vi.  I re-targeted to this vi but I haven't been able to fully load yet so I don't know if this is going to break wires.
    RGT Does File Exists.vi is part of the older NIReport.llb but no longer exists in the new NIReport.llb. 
    The new NIReport.llb is much smaller than the old NIReport.llb, 2.3MB compared to 2.8MB.  So a lot has apparently been removed.
    What should I do to open all my old code with the new toolkit?  Or should I just throw out the new toolkit and continue to use the old one?
    Message Edited by billings11 on 11-15-2007 08:23 AM
    -Devin
    I got 99 problems but 8.6 ain't one.

    Nevermond.  honestly I don't know why but somehow on every computer NIreport.llb is different.  I don't know what is going on.  I think since I have to mass compile every time I want to build an exe it is re-saving every called file in NIReport.llb.  I think it saved  additional instances of polymorphic vi's in there by name, and I don't know where that RGB vi came from.  This is one reason why mass compiling every time I do a build is not a good workaround.
    -Devin
    I got 99 problems but 8.6 ain't one.

  • Is anyone else seeing this with the report toolkit

    I am using LV 8.6 and using the LV report functions inside a VI. This VI is my main VI for the TS user interface. What is happening is, I built my main vi into an executable and then I am building a deployment in TS with the executeable included. I get a tremendous amount of errors when I do this saying that the vi's that are part of the report generation in LV are not able to be loaded because they have no front panel or block diagram. So I did some investigating and sure enough the toolkit was changed to Object Oriented for LV 8.6. This explains why i can get it to build on a machine with LV8.5 installed instead of 8.6.
    I was just wondering if anyone has had this problem with the toolkit and TS.
    I also had a meeting with Brian Buress (field engineer for NI) and Jeff Phillips (LabVIEW product manager) they saw this activity (they were here and I showed it to them) and they could not explain it.
    The problem has to lye in the fact that the report VI'S are now object oriented.
    Is anyone else have trouble with this toolkit.
    Joe.
    "NOTHING IS EVER EASY"

    Hi Joe,
    Yes, I also had a problem with the report toolkit.
    See here for the problem and workaround

  • Report Toolkit Standard Report Print Problem

    We are trying to print a label out on a Zebra QL220+ Thermal Printer.  Using the Report Generation Toolkit and selecting the Report Type as "WORD" it works fine.  However by ONLY changing the Report Type to "STANDARD REPORT" it still prints out the label OK, but then scrolls out another blank label - it's like some sort of form feed character/command is somehow being appended.
    We don't want to use the WORD Report Type, because I assume we have to install MS Office, which we don't want.
    As you can see from the attached VI, it is just some very basic text that we are writing to the Label.
    Is there some way we can see what data is actually being sent to the Printer for the two different Report Types?
    Chris
    Attachments:
    Zebra Label Print.vi ‏43 KB

    If your printer is networked you would open a TCP connection on port 6101 to the printer. If serial simply send the data via normal VISA commands.
    Here is the CPCL for the one example label in your code:
    ! 0 200 200 440 1
    TEXT 0 2 10 10 Date: <DATE>
    TEXT 0 2 10 30 Time: <TIME>
    TEXT 0 2 10 50 Operator: <INITIALS>
    TEXT 0 2 10 70 Location: <LOCATION>
    TEXT 0 2 10 90 Reason: <REASON>
    TEXT 0 2 10 110 Post Comment: <COMMENT>
    TEXT 0 2 10 130 S/N: <SN>
    TEXT 0 2 10 150 Dryness Fraction:
    TEXT 0 2 10 170 Signature:
    LINE 100 190 300 190 1
    PRINT
    In the above label you would programmatically replace the "<x>" fields with the actual data you wanted printed. For your multiple S/Ns you would use a loop to add the lines with each S/N.
    From the CPCL manual here are the pages for the elements I used above:
    TEXT Commands
    The TEXT command is used to place text on a label. This
    command and its variants control the specific font number
    and size used, the location of the text on the label,
    and the orientation of this text. Standard resident fonts
    can be rotated to 90° increments as shown in the example.
    Format:
    {command} {font} {size} {x} {y} {data}
    where:
    {command}: Choose from the following:
    TEXT Prints text horizontally.
    (or T)
    VTEXT Prints text (vertically) rotated 90
    (or VT) degrees counterclockwise.
    TEXT90 (Same as VTEXT above.)
    (or T90)
    TEXT180 Prints text (upside down) rotated
    (or T180) 180 degrees counterclockwise.
    TEXT270 Prints text (vertically) rotated 270
    (or T270) degrees counterclockwise.
    {font}: Name/number of the font.
    {size}: Size identifier for the font.
    {x}: Horizontal starting position.
    {y}: Vertical starting position.
    {data}: The text to be printed.
    LINE Commands
    Lines of any length, thickness, and angular orientation
    can be drawn using the LINE command.
    Format:
    {command} {x0} {y0} {x1} {y1} {width}
    where:
    {command}: Choose from the following:
    LINE Prints a line.
    (or L)
    {x0}: X-coordinate of the top-left corner.
    {y0}: Y-coordinate of the top-left corner.
    {x1}: X-coordinate of:
    - top right corner for horizontal.
    - bottom left corner for vertical.
    {y1}: Y-coordinate of:
    - top right corner for horizontal.
    - bottom left corner for vertical.
    {width}: Unit-width (or thickness) of the line.
    <!> {offset} <200> <200> {height} {qty}
    where:
    <!>: Use '!' to begin a control session.
    {offset}: The horizontal offset for the entire label.
    This value causes all fields to be offset
    horizontally by the specified number of
    UNITS.
    <200>: Horizontal resolution (in dots-per-inch).
    <200>: Vertical resolution (in dots-per-inch).
    {height}: The maximum height of the label.
    The maximum label height is calculated by measuring
    from the bottom of the first black bar (or
    label gap) to the top of the next black bar (or label
    gap). Then 1/16” [1.5mm] is subtracted from this
    distance to obtain the maximum height. (In dots:
    subtract 12 dots on 203 d.p.i printers; 18 dots on
    306 d.p.i. printers)
    {qty}: Quantity of labels to be printed.
    Maximum = 1024.
    Mark Yedinak
    "Does anyone know where the love of God goes when the waves turn the minutes to hours?"
    Wreck of the Edmund Fitzgerald - Gordon Lightfoot

  • Standard report vis fail (error 1) after report toolkit loaded

    Labview 6.1 report vis will not work (when dealing with standard report types) after loading the report generation toolkit 1.0.1. This is depite fixing the known issues found in the knowledge base. ie replace automation open with automation close in font style vi and recompiling the vis.
    Running the text report example.vi included demonstrates the problem. Error 1 will be returned.
    A sub vi in this called tables.vi appears to have 4 automation close vis two of which are inside for loops. I think these need to be outside of the loops? This then transfers the problem to the set font.vi which then returns error 1.

    I have the same problem. I am using LabVIEW 6.1 and Microsoft Office 97. I have installed and reinstalled the Toolkit. Whenever I try to run ANY sample VI's that come with the toolkit (by going to "FIND EXAMPLES"), none of them run. The ERROR LIST says that none of the subVI's are found. Why are these subVI's not being found? I see that they are there. Is there a directory error? Both LabVIEW and the Toolkit were installed in their default directories. The Toolkit is in C:\Program Files\National Instruments\LabVIEW 6.1\vi.lib\addons\_office
    Advice Please?! I have a sample screenshot.
    Attachments:
    screenshot.jpg ‏72 KB

  • Generation report toolkit funciona con office 2007?

    Saludos...
    Mi pregunta es, ¿Report generation toolkit, funciona con office 2007?
    Gracias

    Hola Anghell,
    Depende de la compra que se hizo, algunos paquetes de software incluyen actualizaciones por un año. La persona indicada que puede responder su pregunta es un Representante Técnico, el cual puede contactar en cualquiera de nuestros números gratuitos:
    http://digital.ni.com/worldwide/latam.nsf/sb/Generic+One?opendocument&node=165680_esa
    ¡Saludos!
    Tania Lozoya | National Instruments

  • Report toolkit opening multiple spreadsheets after program runs

    I have a program that generates multiple spreadsheets through the Report Gen Toolkit. After I generate ~4-5 files if I go to open any of them up all of the files open up instead of just the one I clicked on. Is there anyway to prevent this from happening when I create the files?

    Is the reference to the excel sheets still open? I had a similar problem to the one you are seeing and I could get rid of it 2 different ways. The first is to make sure LabVIEW is entirely shut down. The second is to make sure you close the spreadsheets or dispose of the reference. These are workbooks that are essentially open in the background, so when you open excel they will show. Try either closing labview or the references to see if this helps your problem. Posting your code would also help.

  • Reporting Toolkit: How to insert a blank line into an MS Word Report?

    Hello,
    I have created an MS Word report, but I haven't been able to find out how to "write" a blank line to the report.  I've tried every combination of \n, \\n, "\n", '\n', \\n etc., but I haven't had any good luck.
    Thanks,
    Chris

    Hello,
    If you're using "append report".vi it's has one input for "new line".
    Message Edited by Jorge Amaral on 05-02-2008 03:28 PM
    Software developer
    www.mcm-electronics.com
    PS: Don't forget to rate a good anwser ; )
    Currently using Labview 2011
    PORTUGAL
    Attachments:
    append.PNG ‏3 KB

  • Oracle Report toolkit and 3rd components

    Hi folks:
    I am a newbie to Oracle (10g) realm who am expected to write reporting functionality.
    My question is what the report tool out of the box in Oracle and is there any 3rd components for wrting reports?
    Thanks,
    Ricky

    user12086319 wrote:
    Hi folks:
    I am a newbie to Oracle (10g) realm who am expected to write reporting functionality.
    My question is what the report tool out of the box in Oracle and is there any 3rd components for wrting reports?
    Thanks,
    RickyHi Ricky and welcome to the forum
    Could you please elaborate more? What do you exactly want? You can run any sql at SQL*Plus and take the output as report
    You can use Oracle Reports to create a report or you can use Crystall Reports as third part utility

  • Running SMS Reporting Toolkit for inventory

    I’m using SMS Reporting tool kit  ver 4.0, with SCCM 2007 R3.  Is there a newer version?
    How long would it/should it take for SCCM to query 2500 systems in SCCM for Adobe SWTAG files? The current scan has been running for about 3 hours now.
    Will the SWTAG scan pick up more recent Adobe CS5/6 products?
    I added SWTAG file collection in SCCM software Inventory.  Inventory has run on many systems, but I cannot run a SCCM query to locate systems with these files.  Does anyone have a SCCM query to find these systems with SWTAG files?
    I have looked on other Adobe/Microsoft forums with little success.

    v_GS_* views are for hardware inventory.
    All discovery information goes into v_R_System.
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • LabVIEW 8.6 and report generation toolkit

    I was wanting to upgrade to 8.6 but noticed that my rep gen toolkit(1.1.1) is not compatible.
    Will NI be offering a free upgrade? or do I have to go to management and ask to purchase rep gen toolkit 1.1.3 for 500 US dollars?  Purchasing the same toolkit every few years when you have an SSP for a full development system is getting kind of old.
    Brian

    Unfortunately there is some delay in us Aussies getting the original DVDs sent to us, so at this stage my NI rep has burned me a copy of the main LabVIEW install but I can't find the Report Toolkit on it.
    I am an SSP customer but when I go to the Services Resource Centre I get this message:
    Important Message
    Access to the Services Resource Center could not be verified.
    The email address is not subscribed and/or activated with the appropriate level of service. If this is the incorrect email address, please login here
    Please confirm that your correct country information is specified, please select here
    If you have just subscribed you may need to wait up to 48 hours for your subscription to be processed
    If access is urgent, or to subscribe, please contact a NI Representative at (800) 206-2179. Outside of the US and Canada please contact your local NI branch office

  • Report Generation Toolkit 1.01 and broken arrow

    Hi,
    I desperately need help because I need to build my application tomorrow morning for our production department and have trouble with the report toolkit.
    I am aware of your knowledge base entry regarding this problem. I already deinstalled and reinstalled the toolkit (version 1.0.1 for LV 6), and I checked the windows registry entries. Still, after mass-compile, the report generation toolkit VIs are not executable (broken arrow, invalid property node). I have LabVIEW 6.02, 7.0 and 7.1 on my computer and I am using the report generation toolkit version 1.0.1 with LabVIEW 6.02 and version 1.1 with LabVIEW 7.1. The application that I need to build is written in LabVIEW 6.02. What else can I do to get rid of the broken arro
    ws?
    Thanks in advance for your fast answer....
    Gabs

    Hi,
    the problem is the following: during the build error 1003 occures at ....\internal.llb\Word_New_Page.vi. Possible Reasons: LabVIEW: The VI is not executable. When I open my main VI, I see no broken arrow. When I force a mass-compile (Strg+Shift+Run button), the broken arrow appears suddenly. I can then see the following error message: Word Easy Text.vi is broken because Word Format Text.vi is broken because the Property Node Range\Style calls an invalid property. Actually, the property nodes in these VIs have NO properties and the invoke nodes NO methods.
    I know now that this is due to the fact that I need to build this application for a computer on which Word97 is running, so I installed the Report Generation Toolkit for Word97. But - on my developme
    nt computer where LabVIEW is installed Office XP is running, not Office97. If I install the Report Generation Toolkit for OfficeXP, no error occurs during the build, but the executable does not run properly on the target computer (when calling Word97).
    Question for NI: How am I supposed to build an executable using Microsoft Word Report Generation Functions if the target computer has Word97 installed but the development computer has WordXP installed???
    Please help,
    thanks,
    Gabs

  • Report Generation Toolkit and App Builder question..

    Hello,
    I am in process of modifying my test code for writing my data to Excel. When I first developed the tests I did not have the Report Toolkit of Excel so I built the ActiveX VIs I needed. Now since I have upgraded to 7.1.1 with the MSOffice Toolkit I am rewriting my test code to use the toolkit VIs as it seems to work much better and faster then what I had done.
    My question is this. Since I have my testcode distributed to multiple machines when I build my App, do I need to add every Dynamic VI within the toolkit to my App? if so is there and simple way to find exactly which dynamically called VIs are used within the toolkit VIs?
    Thanks
    Jeff
    Jeff D.
    OS: Win 7 Ultimate
    LabVIEW Version: 2011,2010,2009 installed
    Certified LabVIEW Architect

    Greetings jdebuhr ,
    I'm using LabView 7 and have the report generation toolkit, In the "Report Generation Toolkit User Guide.pdf" manual under the title Cearating stand alone applications you 'll find the names and the path of the required dynamic VIs to be included in your EXE file (using appliocation builder)
    Check this manual.
    Ayman Mohammad Metwally
    Automation Engineer
    Egypt - Cairo

  • Report generation toolkit problem with office 2000 and office XP

    Hello, I am having a problem with running my vi after it is compiled with application builder. The dev machine is an XP box and the targer is windows 2000. I included _Excel Dynamic VIs.vi and _Word Dynamic VIs.vi from the office 2000 section of the install cd (for the report toolkit) in the compile but did not include those files for XP. When I run the application on the target machine (2000), the reporting functions call Excel just fine and the program does not come up with any errors. The program however, is not loading the approprate template and inserting the approprate data. Did I leave some neccessary files out of the compile? Thanks in advance!
    Greg
    Gregory Osenbach, CLA
    Fluke

    Hi Acer,
    The recommended procedure in your case is to install Microsoft Office 2000 on the development machine and then reinstall the LabVIEW Report Generation Toolkit. When the toolkit is installed, it will check for the current version of Office and install the corresponding VIs to support it. The VIs include different ActiveX calls according to the version of Office. Therefore it is not enough to change the support manually without having the correct version of Office installed first.
    However, I would recommend that you just try to run your executable on a machine that has Office 2000 installed. The difference in the ActiveX API for Office XP and 2000 is not that significant, so your application might work perfectly on an Office 2000 machine. If you try to run the executable on a machine with Office 97 installed I'm willing to bet my right arm that you will experience errors.
    Good luck Acer!
    - Philip Courtois, Thinkbot Solutions

  • Malfunctio​n in generating word report out of an app (using the report generation toolkit)

    I placed in my program some features that generate a word report with some graphics and text using the report generation toolkit. When I'm in the developing system everything works. But the point is that I have to create an exe for a user and in testing this the report is not generated (and no error msg occurs). Does anyone handeled this problem already and could give me some hints? Thx.

    Hi muchalla,
    the report generation toolkit for MS office depends on the version of MS Office (not the OS). You must generate your application for the version of MS Office or use some dynamic technic.
    The different versions of the llbs you need are on the CD in a subfolder called compability.
    Here I have asked if some ideas to do this will work. Until now I haven't got the time to verify it by myself.
    You will find here more information about using the report toolkit with applications.
    Waldemar
    Waldemar
    Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
    Don't forget to give Kudos to good answers and/or questions

Maybe you are looking for