Appending orbit plots to report

Hey everyone,
I have been having issues appending images of orbit plots and polar plots to excel reports that I am generating using the Report Generation Toolkit. Within the report there are multiple orbit plots that I am generating, and the first one is always blank. It seems like no matter what I do I can't get that first one to show any data. If I change the axis label that will show up, but never any data. Only for the first plot though, the rest show up just fine. Also if I append just a generic plot that seems to work just fine, so I don't think it's any issues with the front panel not loading.
Has anybody else ran into this problem? Were you able to fix it?
Thanks and Best Regards,
Ryan
Attachments:
polar_plot.jpg ‏220 KB

Hey Travis,
I am using the Append Control Image to Report block to generate these pictures. So I am sending a reference of the control to the block and the block then puts the image of the control in the excel report. The reason I'm doing it this way is because the plots make it easy to look at only certain orders of the signal, which would be a lot harder to do within excel.
I have an inkling of a feeling that it has to do with the way the plots are set up, they allow you to calculate many different orders and then select which order you want to look at. Well since my report generation process is automated I don't really need to select which plot I want to look at because I will only be sending one plot at a time to the report. What I think is happening is the data gets calculated correctly, but when it gets plotted the one order that I want to send to my report never gets selected, so the plot remains blank. I can't really explain to you why its only happening to the first one though.
I am using Labview 2010 with Excel 2007.
Thanks for the help,
Ryan
Attachments:
polar_plot_code.jpg ‏88 KB

Similar Messages

  • Error 1055 OA_Get Max Axis Dispaly Value.vi - OUT Orbit Plot (Unfiltered).vi

    Hello to Everyone,
    I am trying to use OA Orbit.vi, but i having trouble, this error message is displayed: Error 1055 OA OA_Get Max Axis Dispaly Value.vi -> OA Orbit Plot (Unfiltered).vi. Is there any solution?
    LabVIEW 8.5 is used.
    The way how is connected, followed a LabVIEW Order Analyses Toolkit User Manual:
    - signal from tachometer is input to OAT Analog Tacho Procces.vi, output Speed Profile is input for Oat Orbit Plot,OAT Convert to Even Angle Signal.vi
    - signal from two proxymity probes is scaled to EU units with SVL Scale Voltage EU.vi
    - scaled signal is input to OAT Convert to Even Angle Signal.vi to get Even Angle Signal
    - Even Angle Signals (from two sensors) is input to Oat Orbit Plot.vi
    - output Even Angle Position Info from OAT Convert to Even Angle Signal.vi is connect with Oat Orbit Plot.vi
    Thanks.
    Best rigards,
    Nandor Spacek

    Hi Nandor,
    Welcome to the NI forums!
    I am not sure that I fully understand your vi based on your description, so I would kindly ask you to create a VI Snippet from the code in question, and embed it in your reply forum post as a picture. This is the recommended best practice when discussing code. Alternatively you can always attach the .vi itself to your post.
    Your LabVIEW version 8.5 is fairly dated, did you make sure that you are using a compatible version of the Order Analysis toolkit? You can check the versions of your software in MAX, or by generating a MAX report.
    Also, please post a screenshot of the error message you are getting. Sometimes you can also just hit Ctrl+C when you have the error message active, and that will copy the error message to the clipboard so you can post it here.
    Best Regards,
    T Simon
    National Instruments
    Applications Engineer
    Certified LabVIEW Developer - Certified TestStand Architect

  • Smartforms: Appending Spool o/p(report)  to  PDF generated by SSF

    Dear Murugesh
    I have attached the code for Appending Spool o/p(report)  to  PDF generated by SSF below
      Please suggest as i will have 2 finish by this SAT.
    (Hint : Under 1 SOrdr there may be several line items==>
      The material with ref 2 every line-item either may be configurable(ZPL3) or nonconfigurable(ZA3C)) .
    *ENCLOSER TO PACKING LIST
    SELECT VBELN POSNR INTO CORRESPONDING FIELDS OF TABLE T_VBAP
                        FROM  VBAP
                        WHERE VBELN = SSORD.
    *For capturing the o/p pages from ZPL3 and consolidating into table
    *T_OTF to get single PDF
      LOOP AT T_VBAP INTO T_VBAP.
        ITNO = T_VBAP-POSNR.
      SELECT SINGLE * FROM ZPP_PLCMH WHERE VBELN = SSORD
                                     AND   POSNR = ITNO.
       IF SY-SUBRC EQ 0.
         SET PARAMETER  ID: 'AUN' FIELD SSORD ,
                            'APO' FIELD ITNO.
         CALL TRANSACTION 'ZPCE' AND SKIP FIRST SCREEN.
         IMPORT A = T_OTF2 FROM  MEMORY ID 'MEMID'.
         LOOP AT T_OTF2  INTO T_OTF2.
           APPEND T_OTF2 TO T_OTF.
         ENDLOOP.
         REFRESH T_OTF2.
       ELSE.
    *For capturing the o/p pages from ZA3C and Appending
    *at the end of the PDF file just created by the above code
        SELECT SINGLE * FROM ZPLH WHERE VBELN = SSORD
                                  AND   POSNR = ITNO.
         IF SY-SUBRC EQ 0.
           SET PARAMETER  ID: 'AUN' FIELD SSORD,
                            : 'APO' FIELD ITNO.
           CALL TRANSACTION 'ZPNE' AND SKIP FIRST SCREEN.
           IMPORT B = SPOOL_ID  FROM  MEMORY ID 'MEMID2'.
           CALL FUNCTION 'CONVERT_ABAPSPOOLJOB_2_PDF'
             EXPORTING
               SRC_SPOOLID                    = SPOOL_ID
               NO_DIALOG                      = ''
               DST_DEVICE                     = E_DEVTYPE
              PDF_DESTINATION                = 'LOHP'
            IMPORTING
               PDF_BYTECOUNT                  = BTC
             PDF_SPOOLID                    =
             LIST_PAGECOUNT                 =
             BTC_JOBNAME                    =
             BTC_JOBCOUNT                   =
            TABLES
               PDF                            = T_SPOOL_2_PDF
           EXCEPTIONS
             ERR_NO_ABAP_SPOOLJOB           = 1
             ERR_NO_SPOOLJOB                = 2
             ERR_NO_PERMISSION              = 3
             ERR_CONV_NOT_POSSIBLE          = 4
             ERR_BAD_DESTDEVICE             = 5
             USER_CANCELLED                 = 6
             ERR_SPOOLERROR                 = 7
             ERR_TEMSEERROR                 = 8
             ERR_BTCJOB_OPEN_FAILED         = 9
             ERR_BTCJOB_SUBMIT_FAILED       = 10
             ERR_BTCJOB_CLOSE_FAILED        = 11
             OTHERS                         = 12
           IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
           ENDIF.
    ELSE.
           TEXT02 = ITNO.
           MESSAGE I014(ZQOTBANK) WITH TEXT02.
       ENDIF.
    ENDIF.
    ENDLOOP.
    CALL FUNCTION 'CONVERT_OTF_2_PDF'
      EXPORTING
        USE_OTF_MC_CMD               = 'X'
      ARCHIVE_INDEX                =
    IMPORTING
        BIN_FILESIZE                 = BIN_FILESIZE
    TABLES
        OTF                          = T_OTF
        DOCTAB_ARCHIVE               = T_DOC
        LINES                        = T_LINES
    EXCEPTIONS
       ERR_CONV_NOT_POSSIBLE        = 1
       ERR_OTF_MC_NOENDMARKER       = 2
       OTHERS                       = 3.
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    CALL FUNCTION 'GUI_DOWNLOAD'
      EXPORTING
        BIN_FILESIZE                    = BIN_FILESIZE
        FILENAME                        = 'C:\SD6.pdf'
        FILETYPE                        = 'BIN'
        APPEND                          = 'X'
      WRITE_FIELD_SEPARATOR           = ' '
      HEADER                          = '00'
      TRUNC_TRAILING_BLANKS           = ' '
      WRITE_LF                        = 'X'
      COL_SELECT                      = ' '
      COL_SELECT_MASK                 = ' '
      DAT_MODE                        = ' '
      CONFIRM_OVERWRITE               = ' '
      NO_AUTH_CHECK                   = ' '
      CODEPAGE                        = ' '
      IGNORE_CERR                     = ABAP_TRUE
      REPLACEMENT                     = '#'
      WRITE_BOM                       = ' '
      TRUNC_TRAILING_BLANKS_EOL       = 'X'
    IMPORTING
        FILELENGTH                      = BIN_FILESIZE
      TABLES
        DATA_TAB                        = T_LINES
      FIELDNAMES                      =
    EXCEPTIONS
      FILE_WRITE_ERROR                = 1
      NO_BATCH                        = 2
      GUI_REFUSE_FILETRANSFER         = 3
      INVALID_TYPE                    = 4
      NO_AUTHORITY                    = 5
      UNKNOWN_ERROR                   = 6
      HEADER_NOT_ALLOWED              = 7
      SEPARATOR_NOT_ALLOWED           = 8
      FILESIZE_NOT_ALLOWED            = 9
      HEADER_TOO_LONG                 = 10
      DP_ERROR_CREATE                 = 11
      DP_ERROR_SEND                   = 12
      DP_ERROR_WRITE                  = 13
      UNKNOWN_DP_ERROR                = 14
      ACCESS_DENIED                   = 15
      DP_OUT_OF_MEMORY                = 16
      DISK_FULL                       = 17
      DP_TIMEOUT                      = 18
      FILE_NOT_FOUND                  = 19
      DATAPROVIDER_EXCEPTION          = 20
      CONTROL_FLUSH_ERROR             = 21
      OTHERS                          = 22
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    Thanx
    Moni
    Message was edited by: md monirujjaman

    Hello,
    Can you explain the problem in detail plz.
    I do see that the logic which was proposed is implemented in code.
    please check at various places, in run time the following points:
    1. Spool ID exported into ABAP Memory.
    2. Contents of the Main OTF IntTab.
    3. Conversion of the Spool to PFD.Check whether SUBRC = 0. <b>Un-comment all the Exceptions in your FMs where-ever you make a call in your program.</b>
       If this conversion of Spool to PDF is successful, you can choose "Append" option from the popup.
    Hope this helps you. Or if you have any specific query let me know.
    Regards, Murugesh AS

  • Cluster not saved correctly in Append Control Image to Report VI

    [LV8 with Windows XP]
    I'm using the Append Control Image to Report VI to save the image of a control to Word (the same problem occurs if I save to Excel). This VI seems to work fine with all my controls except clusters. Not all of the contents of the cluster show up in the saved image. I have to expand the edges of the cluster way beyond the cluster contents in order for all the contents to show up in the saved image. Is this a bug? Is there a way to "realign" the contents of the cluster within the boundaries?
    George

    Hi,
    just had a customer with the problem with this cluster picture function and I wrote a little VI that manually gets the picture, resizes it to the cluster and the rest is up to you. The only thing is, that you have to place the "zero point" of the frontpanel in the upper left corner to get the proper image.
    For Users who want to upgrade: This issue is fixed with the next LabVIEW release.
    Best Regards,
     Andreas Pistek
    ~~~ Logic is a systematic method of coming to the wrong conclusion with confidence ~~~
    Attachments:
    better picture.vi ‏19 KB

  • I can't append control image to report on 1 page with appended text report

    I am attempting to create a report which is simply header, experiment information, and two graphs of data. I am using a Easy Text Report and Append Control Image to Report. I have successfully printed out this report, but on two separate pages. The header info is on the first page, and the graphs on the second page. This doesn't seem to be a margins problem, as the header is very brief and the graphs aren't that large either. I would like to make this into a one page report.  Any help is greatly appreciated.
    Message Edited by csmrunman on 01-15-2010 10:18 AM

    Nevermind. I neglected to see the Append Report Text.vi. That solved everything.

  • Need custom column widths in Append Text Table to Report

    I need to print reports with tables of different column widths specified for each column, as the contained fields vary in width from just 3 characters in one column to 40 characters in another.  Also we are trying to match the reports generated by a non-labview routine.  In the past I have been able to achieve this by editing the Append Table to Report vi, working my way through the inner hierarchy to replace the DBL numeric COLUMN WIDTH control with a DBL numeric array.  The innermost vi, Set Table Column Width, assigns the numeric to a property node in a for loop, so the change is simple: replace the scalor with an array and enable indexing on the for loop.  Of course, after each Labview upgrade, I've had to go back in and repeat these edits on the overwritten upgraded vi's.  This time there is a problem.  The new version of this toolkit is object oriented, and disturbing these vi's wrecks the class methods in a way I don't understand (mostly because I've had no dealings with object oriented programming) and which cannot be undone.  I recently tried this and after not being able to fix the problem even with phone support, I had to spend the next two days unistalling and reinstalling Labview!  I desperately need a way to achieve this functionality without killing the toolkit, which is used (in its original functionality) by another absolutely critical program.  PLEASE HELP!
    The hierarchy is as follows:
    NI report.lvclass:Append Table to Report (wrap)
    NI report.lvclass:Append Table to Report 
    NI Standard report.lvclass:Append Text Table to Report
    NI Standard report.lvclass:tables
    NI Report Generation Core.lvlibet Table Column Width

    There is a highly relevant thread under discussion here:
    http://forums.ni.com/ni/board/message?board.id=fea​tures&thread.id=429
    You may wish to read it and chime in as it is a discussion of LabVIEW's policy (and possible change in policy for the future) concerning the handling of non-palette VIs between LV versions.
    Rob Hingle wrote:
    > Is that to say NI will not be helping me with this?  Pretty disappointing lack of support, seems
    > like a terrible idea to go to object oriented if even your own application engineers can't figure
    > out such a simple fix.  Gotta give NI a huge thumbs down on this one, thanks for nothing.
    I doubt that it is a simple fix -- our AEs are generally top notch at figuring out solutions for customers -- if it were simple, my bet is they'd have solved it. Asking an AE to work around a bug is different from asking them to rearchitect the toolkit. You are asking them to add a feature that the new version of the toolkit is not
    designed to support. The difficulty in doing this is completely independent of the decision to use LabVIEW classes to implement the toolkit. If any piece of software is not designed with a particular use case in mind, what may be a simple tweak under one design may become a very hard problem under another design.
    In your case, the solution is very straightforward: Use the older version of the toolkit. Any time you create a custom modification of the VIs that ship with LV or one of its toolkits, you should make your own copy and have your VIs link against the copy. LabVIEW promises to maintain all the public functionality version over version. Usually we succeed at that. What we do not promise is to maintain our private implementation of that functionality. It is impossible for LabVIEW (or any other software library) to maintain all of its private internal operations while still continuing any development. Using a copy of the original VIs shields you from having to recode your changes every version (something you've already mentioned is a chore) and it guarantees that functionality that you relie upon does not disappear.
    I hope you are willing to be understanding of this situation and not hold it against the AEs working on this. They try hard to provide excellent customer service, and spend lots of time inventing custom solutions for our users.  This happens to be a situation where the correct fix is not to modify the new toolkit version to do something it wasn't designed to do but to modify your development process so that the problem is solved now and into the future. 

  • Append Control Image to Report stops Source Distributi​on from working

    I have a top level built executeable that calls various external vi's using the "Call by Reference Node" function.  This seems to work ok, to a point.  An additional point here is this is code that I had running well in LV8.2 and am now trying to get running in LV2010 as there have been some significant changes in LV that have impacted on this project and this has forced me to change things.
    The external vi that is called is stored in a "Source Distribution" directory structure, which has been generated via its own project specifications.  An examination of the directories and vi's stored at the destination looks like everything should be there. 
    When it comes to running the vi in the source distribution directory (from the top level built executeable) I get the following error message "Error 1003 occurred at Open VI Reference in Run HTML Report Generation VI LV10.vi->Generate Reports.vi", with the additional suggestion " The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located. Select File>>Open to open the VI and then verify that you are able to run it.".  So it looks like there is something missing in the "Source Distribution" directories.
    Doing as suggested, opening the vi in the "Source Distribution" with the development environment, shows that it has no broken arrow.  My suspicion is the development environment is supplying whatever it is missing.
    Using the built top level application, using trial and error and using the diagram disable structure, I have narrowed down the location of the problem to an "Append Control Image to Report" sub vi (its from the NI Report menus).  Disabling this vi at the level it is called, allows the "Source Distribution" vi to run.  "Append Control Image to Report" is part of a class structure and I must say I have not used class structures so my understanding of their implications is very limited.
    If I instead dive into "Append Control Image to Report" vi and disable the vast majority of its diagram (everything in the "No Error" case), the original error pops up again.  Bit strange considering there are only controls and indicators and a case statement left.
    I would appreciate any suggestions, as this has got me stumped.  Hopefully I have made myself clear enough as it is all a bit complicated.  Let me know if I haven't.  Thanks.
    Herbert Niesler

        Hi Caleb,
          "When the VI displays the broken arrow and displays that error in the dialog, does it take you to a particular diagram component? Does the diagram have any broken arrows or something?"...      it doesn't take me to a particular diagram.  Is this possible in the RTE?  If it is how do I enable it?
       I can follow the chain of broken arrows (front panel only) down to my vi that calls the NIreport vi that is causing the problem.  However I am unable to open the NIreport vi's in the RTE, so cannot chase this any further down the call chain.
      I have tried opening the offending top level vi (on a network drive) and it opens ok.  When I close it, it wants to save some changes which i think might point at where the problem is.  The attached file shows the screen shots of the "Explain Changes" window.  Hopefully they mean something to you.
           Cheers
                    Herbert
    Herbert Niesler
    Attachments:
    Explain Changes.jpg ‏46 KB

  • Bug in Append Control Image to Report in 8.5?

    I am now at an end with this.  I seem to have some sort of problem when using the Append Control Image to Report.  I have a program that creates two reports.  One is a condensed version, the other detailed.  Both reports contain JPG images of some front panel displays.  For the most part it seems to work except what ever it is doing appears very unstable.  The problem seems to center around me trying to include a Multicoulmn Listbox.  I create a Reference of it and then run that to my Append Control Image, just like any other image I want to include.  If I probe the Reference, it appears to be correct, i.e. the name, etc. all seem right.  However, what the image that gets included is a whole different graphic.   Some times I will get the listbox, other times nothing at all.  If I look in the directory and bring up the images, indeed, if it prints the wrong graphics, it also has created two of the ne that it includes. 
    Running the same program unmodifed seems to do the same thing, i.e. it always will print the wrong graphic.  As I have tried different things to try and skirt the problem, I get different effects.  
    I have seen the same problem with other graphics as well, not just the listbox, but I can't come up with any hint as to why it does what it does. 
    Attachments:
    LABVIEW_err.jpg ‏18 KB

    I have dug into this a little further and it appears this bug has to do with creating two reports at the same time. If I only generate a single report, everything works flawless.
    I placed the sections of the code that append data to the reports into a sequence so they would not happen at the same time. This seemed to have some effect, but the reports were still incorrect.
    Is LabView just not able to create two reports within a single progeam?
    I can work around this by creating just the detailed report for now, but it would sure be nice if there were a way to make it work.

  • How do you set the line spacing when using the Append Text Table to Report VI?

    I have a table of numbers which I wish to print using the report generation VI's. Since each column has a different numerical format, I first convert the number for each cell to a string with the appropriate format and then build a string array to pass to the Append Text Table to Report VI. The table is printed with double line spacing. How do I reset this for single spacing?
    Attachments:
    print_array.vi ‏112 KB

    Dave,
    The issue is not with the NI-Reports functionality, but the Array to Spreadsheet String funvtion in the for loop. Here is the context help for this function:
    "Converts an array of any dimension to a table in string form, containing tabs separating column elements, a platform-dependent EOL character separating rows, and, for arrays of three or more dimensions, headers separating pages."
    The thing to note here is that it says it adds an EOL (end of line) character at the end of every row. This is what is happening. Your first column of data has a \r\n in it and adds the second row to each data item. This in turn makes the rest of the columns have a larege blank space at the bottom so that all of the cell heights are equal. I w
    ould re-write that little bit of code so that you just do one large string concatenation of number, spaces, number, spaces, number and this should solve your issue.
    Thank you for using the Developer Zone Discussion Forums.
    Randy Hoskin
    Applications Engineer
    National Instruments
    http://www.ni.com/ask

  • Append to an existing report

    Hi Everyone,
    Is there a way to append a report to another existing one. I mean, I have already saved and closed a report as a HTML and I want open and add more data and figures to it. I'm using LavVIEW 8.0.
    Any help would be appreciated.
    Mike
    Message Edited by q123456789 on 02-10-2007 01:18 AM

    Hello Mike,
           I could not find a VI that would open an existing HTML report.  Without an "Open Report" VI, you cannot get a reference to your pre-existing HTML report.  I recommend opening both html files as text files, concatenating those strings and then replacing the pre-existing HTML file with the combined string.  I tested it with just adding some line breaks at it seemed to work fine.  Let us know how it works for you.
    Cheers,
    NathanT

  • Append Intensity Chart to Report

    Hello everybody
    I am trying to append an intensity chart to word report generation VI, any ideas to do this? I am thinking about append front panel image to report vi. but it doesn't accept my chart reference.
    The idea is to send the picture to report whenever defect is detected by the intensity chart during the test
    thank you 

    You cannot have multiple copies of the Report Generation Toolkit installed to different LabVIEW versions.  If you want to use the Report Generation Toolkit in LabVIEW 8.2, you will need to uninstall it from your previous LabVIEW version, then reinstall it to LabVIEW 8.2.  If you really need the toolkit installed to multiple LabVIEW versions, there is a workaround outlined in this KnowledgeBase entry, although it's not a complete workaround for the Report Generation Toolkit, since this toolkit is one of the only ones that actually replaces shipping LabVIEW files.
    We are currently investigating ways to alleviate the pain of using toolkits with multiple LabVIEW versions.  Let me know if you have any other questions.
    -D
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

  • Print report and append control image to report.vi problem

    why print report.vi and control image to report.vi can't executable in xp service pack 3??
    before that, i use xp service pack 1. these sub vi can use successful. but after i transfer all ni file into xp service pack 3, that sub vi can't executable..why it happen???
    please, help me...

    When you said that you used your VIs in service pack 1 and then transferred to Service pack 3, are you referring to 2 different computers or you simply updated the computer with SP1 to SP3?
    If you are using 2 different computers, were all the software and the toolkit also installed in the pc with SP3? I am using XP with SP3 and I am not having any problems with the print vi.
    If you have more information, like if you get an error message, kindly post it here as well.
    Best regards,
    Mary Anne
    .....YOU WONT LEARN IF YOU ALREADY KNOW.....

  • Append table with multi-line cells to word report

    Hi,
    I am using LabView 7.0. I need to append table to word report and I am using Append Table to Report VI. My VI works fine as long as the table cells do not have multiple lines. For multiple lines, each line is put is a seperate cell in the word report.
    Is there a way to append multi-line cells to Word Report??? If not, any suggestions on how I can copy the multi-line table to Word report???
    Please kindly help!!
    Please see the attached document for details on the problem.
    Thanks,
    Mim
    Attachments:
    Table with multiple line cells.doc ‏33 KB

    Hi Mim,
    Yes I understood the multiple-lines part. I think the doc is the report you want. Correct ?
    The doc is generated with your VI without any modifications.
    I am using XP, Office 2002 SP3 and LV7.1
    Attachments:
    Verification Report.doc ‏39 KB

  • How to make a PDF embedded image append a report and send via fax electronically from MS SSRS 2012?

    How can I make a PDF embedded image append a SSRS 2012 report and send via fax all electronically?  Is this possible?
    Thanks in advance for your time!

    Hello,
    1. The report item Image can be used to display the image which  embedded in the report, stored in a database, stored on the report server, or stored elsewhere on the Web.
    For example, you can embedded the PDF image in the report and stored as text in the report definition.
    2.Reporting Services includes an e-mail delivery extension and a file share delivery extension which you can send report to user or group through e-mail or send the report to a shared location on your network.
    If you want to send the report to FAX, you may try to create a custom delivery extension depend on your faxing software.
    Reference:Implementing a Delivery Extension
    Regards,
    Fanny Liu
    Fanny Liu
    TechNet Community Support

  • I am unable to edit 'tables.vi' (part of report generation)

    I wish to create a table in a report, using different column widths. I've saved 'Append text table to report.vi", "tables.vi" and "set table column width.vi" under different names, without update callers.
    When i make any change (placing any function), the report data property turns black, and error are given. I've noticed that NIReports.report item of the data clusters returned form "Generate report data to modify.vi", does not have any properties when connecting it to a propery node.

    Can you post a stripped down version of your code that reproduces this behavior? I am not sure if something on the VI turns black or the report turns black. If you get an error message what is it? What version of LabVIEW are you using?
    I found a link to a document that you may find useful.
    Tables in Standard Reports are Limited in Width, Regardless of Margin Settings

Maybe you are looking for