Report Generation broken after deployment - Excel Set Cell Color and Border.vi

Upon deployment, the Excel Set Cell Color and Border.vi became broken.  After installing LV2010 SP1 to view the VIs in the deployment, I noticed that in the second case structure where the code draws the border using the BorderAround invoke node, there is an extra variant input parameter named 'Parameters'.  Upon right-clicking, an option to 'Relink Invoke Node' appeared and after selecting this, the extra input disappeared and the VI was no longer broken.
Why does "Relink Invoke Node" appear?  How do I create a deployment with this issue?  Has anybody else experienced this?  Why is the TestStand deployment so buggy?  

Hi Ching-Hwa,
I have set up a test deployment here where I am deploying a workspace that contains a sequence file.  This sequence file has a LabVIEW Action Step calling a VI that opens a new Excel file and simply calls the Excel Set Cell Color and Border VI.  After deploying this, both the VI and my test sequence ran on the deployment machine without error.  Therefore, I do have some more questions to more accurately reproduce what you are seeing.
First, what operating systems are you developing on and deploying to?  Also, what license do you have for TestStand on the machine you are deploying to?  If you have a development version, can you manually take the sequence file and VI to this machine and run it?  I know you now have LabVIEW 2010 SP1 on your development machine, but if you have the development version of TestStand as well, it would be interesting to see if you copy the files over if you still see this behavior.  Are you including the TestStand Engine in the deployment?
Can you open a blank VI on the deployment machine and add the Excel Set Cell Color and Border VI?  It would also be interesting to see if this is not a product of the deployment, but rather an issue with something on the deployment machine itself.  What version of the Report Generation Toolkit do you have on each machine?  Also, what versions of Excel are you using on the development and deployment machine?  Again, it would be helpful for me to know exactly what versions you have installed on both the development and deployment machines so that I can reproduce this as accurately as possible.
One last thing to try, too, would be to try deploying the VI by itself just to see if it also has the same behavior.  Do you have the Application Builder in LabVIEW?  If so, could you also try building an executable from the VI, create an installer, and deploy this to the deployment machine?  
In regards to the "freezing" of code by removing the block diagrams, I do not believe this will be a proper work around in this case.  While this removes the block diagram from actually being deployed along with the VI and restricts users from editing the code on the deployment machine, if something is getting changed in the compiled code upon deployment, this will not stop this from happening.  This option is available more as a memory option to lower the size of the deployment as well as prohibit any users on the development machine from editing the block diagram themselves.    
Thanks, Ching-Hwa!  I look forward to your response so that I can continue trying to reproduce this issue.  Have a great day! 
Taylor G.
Product Support Engineer
National Instruments
www.ni.com/support

Similar Messages

  • NI_Excel.Ivclass:Excel Set Cell Color and Border.vi Error

    Hi
    I was trying to compile a file and I kept getting an error. It zeroed in on the vi that was not compiling. I am attaching the vi to this message. The vi seems to be broken. And I am not sure how to fix this. Can some one please help me out with this. Thanks in advance. 
    I guess it is associated with Report Generation Toolkit. Please let me know if you need any more details.
    This is the error message 'One or more required inputs to this function are not wired or are wired incorrectly. Show the Context Help window to see what the connections to this function should be.'
    Regards
    Mr Miagi
    Solved!
    Go to Solution.
    Attachments:
    Excel Set Cell Color and Border.vi ‏20 KB

    http://forums.ni.com/t5/LabVIEW/Set-excel-cell-color-and-border-broken-can-t-build-application/m-p/1...
    Please do a search.

  • Excel Set Cell Color and Border VI

    您好,
    請問如果不小心更改到Excel Set Cell Color and Border VI的內容,應如何復原?
    謝謝!!!
    已解決！
    轉到解決方案。
    附件:
    Excel Set Cell Color and Border.jpg ‏231 KB

    http://search.ni.com/nisearch/app/main/p/bot/no/ap/tech/lang/zht/pg/1/sn/catnav:du/q/report%20genera...
    以下載點除了 labview 2012 report generation toolkit 以外
    其他都是 patch 檔
    如果您有購買正式版，也許您可以跟 NI 客服部求救

  • Excel Set Cell Color and Border.viのbackground color 設定について

    お世話になっております。
    Microsoft オフィス用レポート生成ツールキットを使って
    LabVIEWで収集したデータをExcelファイルで出力しようと考えています。
    そこで質問が有ります。
    題名のようにExcel Set Cell Color and Border.viのbackground color 設定についてです。
    デフォルト（未配線）では白に設定されていますが、”色なし”に設定するにはどうしたら良いのでしょうか？
    又、罫線色等を指定する数値設定に関しては、何処を調べたら良いのでしょうか？
    ご教授の程、宜しくお願い致します。

    _YN 様
    平素よりNI製品をご利用頂きまして誠にありがとうございます。
    日本ナショナルインスツルメンツ技術部の湧川と申します。
    ご質問にお答え致します。
    色なしにしたいとの事ですが、こちらでExcel Set Cell Color and Border.viを使用して簡単なVIを実行させてみましたが色なしに設定することはできませんでした。
    そこで質問したいのですが色なしにする理由というのはバックグラウンドが白のままだとセルの枠が見えなくなるからでしょうか。
    もしそうであれば設定により枠をつけることができますのでそちらの方を試して頂けたらと思います。
    方法としましては同じExcel Set Cell Color and Border.viを使い設定します。
    アイコンの上部にピンク色のピンが２つあるかと思いますがそちらからセル内側の線、外側の線を設定できます。
    添付した画像を参照して下さい。
    画像のように設定しますとセルに黒色の枠ができると思います。
    数値設定などに関しても質問されていますが、そちらはヘルプがありますのでそちらを参照頂けると詳しい情報がわかるかと思います。
    LabVIEWでVIを開いている時に　ctrl + H を押しますと小さいウィンドウ「詳細ヘルプ」が立ち上がります、その状態でマウスのポインタをアイコンに重ねて頂きますと詳細ヘルプにアイコンの説明が記述されます。
    ウィンドウズ内のリンクからオンラインヘルプを参照することもできます。
    上記内容をご確認いただきまして、何かS_YN様の意図と違う点などありましたらご連絡下さい。
    宜しくお願い致します。
    日本ナショナルインスツルメンツ株式会社
    技術部
    湧川　朝満
    添付:
    Excle Set Color Sample.JPG ‏58 KB

  • Need help with Report Generation Toolkit: Excel Set Cell Format.vi

    Hi people,
    I've been searching and found this old thread of someone asking what is the input parameter "Number format". And I dont know what should I put in there. I've tried so many possibilities, but nothing works so far, such as:
    0,0
    0,?
    0,#
    #,0
    ?,0
    and also with @, doesnt works. Where would I find help about this parameter?
    I'm using Excel2003, german version, thus local decimal separator is a comma.
    I also found this help from NI, but seems doesnt help me either. Do I miss something important?
    thanks,
    Yan. 

    Hi,
    I've used your suggestion and some numbers in excel doesnt need to get "right click, change to numbers" anymore (green indicators on the left-top side in some cells are gone). But, I think its still not a number, because I cant use a simple formula, such as in cell A10 I type "= A1/2" (cell A10 equals cell A1 divided with 2) . I got error which says its not a number.
    Well, but other thing is found, any format-string I put in the input of Excel Set Cell Format.vi, such as #,########, will be shown the same as "customize #,########" if I right click in a cell in excel and click "Zellen formatieren" (formatting cell). But however, the numbers are still depends on the input of the format I put in the Append Table to Report.vi.
    regards,
    Yan.

  • \National Instruments\LabVIEW 2011\vi.lib\addons\_office\excel.llb\Excel Set Cel

    \National Instruments\LabVIEW 2011\vi.lib\addons\_office\excel.llb\Excel Set Cel  with a broken arrow
    Attachments:
    error pic.png ‏27 KB

    version of Excel is 2010, but i have this problem with Excel 2007, Excel 2003. This property also has a problem in old  versions of  labview  (8.6; 9; 10).
    Attachments:
    excel1.png ‏86 KB
    pic2.png ‏4 KB
    excel version.png ‏38 KB

  • I am using report generation toolkit 1.1 with Labview 7.0 and Office 2003 profession​al. The create new report VI opens Excel but throws error (-21471672​62- 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

  • Excel Set Color and Border VI: no fill?

    If i use Excel Set Color and Border VI to modify the format of a cell, i will get white as my default color for my cell.  However, I am looking for no fill.  I don't want any color, since the color will hide the gird line.  What do I get the no fill option for cell color in LabVIEW?
    Kudos and Accepted as Solution are welcome!
    Solved!
    Go to Solution.

    I have to say I was waiting for this question (I have tried it and observed the same thing). The only solution I see is to use a combination of the RGT vis and ActiveX.
    Ben64
    note, I have connected Cell1 and Cell2 of the _Worksheet Range method but it is probably sufficient to connect only Cell1 here.
    edit: Good, your solution seems a lot more simple!

  • Setting cell color in ALV

    Hi All
    I would be greatful if someone could please help...
    I am still attempting to get cells painted within a WDA ALV grid display.
    I have tried to use the method stated in the WDA sap press book - but this method is for use with TABLE element and I am using a ViewContainerUIElement for my table. There are mentions of wonderful ways to color cells in a list display - but I cannot understand how this can be achieved. I currently have this working appart from the numeric numbers of the design being set into the relavant column cell.
    If anyone could help that would be great...
    Please see: http://picasaweb.google.co.uk/dave.alexander69/Pictures#5244800978549492338
       LOOP AT lt_zdata INTO ls_zdata.
            lv_index = sy-tabix.
    *       set column values
    *       loop at row data and set colour attributes of individual cells
            LOOP AT lt_columns ASSIGNING <fs_column>.
              lr_col_header = <fs_column>-r_column->get_header( ).
              lr_col_header->set_ddic_binding_field( ).
              CREATE OBJECT lr_input_field EXPORTING value_fieldname = <fs_column>-id.
              lr_column = lr_column_settings->get_column( <fs_column>-id ).
    *         for the date columns only...
              IF <fs_column>-id(4) = 'CELL'.
    *           get and set column dates from select option user input
                READ TABLE lt_dates INTO ls_dates INDEX 1.
                IF lt_dates IS INITIAL.
                  lr_col_header->set_text( 'Date' ).
                ELSE.
                  ls_dates-low = ls_dates-low + lv_incr_date.
                  MOVE ls_dates-low+2(2) TO lv_for_col_date+6(2).   "Year
                  MOVE ls_dates-low+4(2) TO lv_for_col_date+3(2).   "Month
                  MOVE ls_dates-low+6(2) TO lv_for_col_date(2).     "Day
                  MOVE lv_for_col_date   TO lv_col_date.
                  lr_col_header->set_text( lv_col_date ).
                  lv_incr_date = lv_incr_date + 7.
                ENDIF.
                LOOP AT lt_orgdata_dates INTO ls_orgdata_dates
                  WHERE crew = ls_zdata-crew
                    AND position = ls_zdata-position
                    AND name = ls_zdata-person
                    AND trip_arr >= ls_dates-low
                    AND trip_dep <= ls_dates-low.
    *             column heading settings
                  lr_field = lr_table->if_salv_wd_field_settings~get_field( <fs_column>-id ).
                  lr_field->if_salv_wd_sort~set_sort_allowed( abap_false ).
    * trying to set cell variants ?@#??!!???
    *              lr_cv = lr_column->set_key( ls_zdata-variance ).
    *              lr_cv->set_editor( lr_input_field ).
    *              lr_cv->set_cell_design( value = '01').
    *              lr_column->add_cell_variant( lr_cv ).
    * current method of seeting the cell colors... (but puts value in cell!)
                  FIELD-SYMBOLS: <fs> TYPE data.
                  lr_column->set_cell_design_fieldname( value = <fs_column>-id ).
                  ASSIGN COMPONENT <fs_column>-id OF STRUCTURE ls_zdata TO <fs>.
                  WRITE: CL_WD_TABLE_COLUMN=>e_cell_design-one TO <fs>.
                  MODIFY lt_zdata FROM ls_zdata. " INDEX lv_index.
                ENDLOOP.
              ENDIF.
    Kind Regards
    Dave Alexander

    Hi check this code to set cell colors for ALV grid.
    Take a context attribute with type WDUI_TABLE_CELL_DESIGN.
    Here i am populating colors based on some condition.Check the loop of the internal table.
    method get_flight_details .
    data:node_flights type ref to if_wd_context_node,
         it_flights type sflight_tab1,
         ls_flights type sflight,
         it_final type   if_componentcontroller=>elements_flights,
         ls_final type   if_componentcontroller=>element_flights.
        select * from sflight into table it_flights
    up to 100 rows.
        node_flights = wd_context->get_child_node( 'FLIGHTS' ).
        loop at it_flights into ls_flights.
           move-corresponding ls_flights to ls_final.
           if ls_final-price = '185.00'.
              ls_final-readonly = abap_true.
              ls_final-celldesign =
    cl_wd_table_column=>e_cell_design-badvalue_light.
           else.
              ls_final-readonly = ' '.
              ls_final-celldesign =
    cl_wd_table_column=>e_cell_design-goodvalue_light.
           endif.
           append ls_final to it_final.
        endloop.
        node_flights->bind_table(
            new_items            = it_final
            set_initial_elements = abap_true
    *        INDEX                = INDEX
    data: l_ref_cmp_usage type ref to if_wd_component_usage.
    l_ref_cmp_usage =   wd_this->wd_cpuse_alv( ).
    if l_ref_cmp_usage->has_active_component( ) is initial.
       l_ref_cmp_usage->create_component( ).
    endif.
    data: l_ref_interfacecontroller type ref to iwci_salv_wd_table .
    l_ref_interfacecontroller =   wd_this->wd_cpifc_alv( ).
       data:
         l_value type ref to cl_salv_wd_config_table.
       l_value = l_ref_interfacecontroller->get_model(
    * Make Price column editable
    data:l_column type ref to cl_salv_wd_column,
          l_column1 type ref to cl_salv_wd_column,
          lr_input type ref to cl_salv_wd_uie_input_field,
          l_input1 type ref to cl_salv_wd_uie_input_field.
    l_column = l_value->if_salv_wd_column_settings~get_column( 'PRICE' ).
    create object lr_input
      exporting
        value_fieldname = 'PRICE'
    l_column->set_cell_editor( value = lr_input ).
    * to make some cells non editable
    lr_input->set_read_only_fieldname( value = 'READONLY' ).
    l_value->if_salv_wd_column_settings~delete_column( id = 'READONLY'   )
    *Set the table Editable
    l_value->if_salv_wd_table_settings~set_read_only( value = abap_false ).
    *Give colors to cells
    l_column1 = l_value->if_salv_wd_column_settings~get_column( 'CARRID' ).
    l_column1->set_cell_design_fieldname( value = 'CELLDESIGN'  ).
    l_value->if_salv_wd_column_settings~delete_column( id = 'CELLDESIGN' )
    endmethod.
    Thanks
    Suman

  • Setting Font Color and Bold Property in ALV Grid

    I have a requirement to set the font in particular ALV Cells  in red color.
    Also this font (text) has to be set to Bold.
    I know how to set cell coloring in ALV Grid, but have no idea regarding how to set font color.
    Could please give me an idea/code segment/suggestion.
    Thank You!

    Please refer this post
    Coloring of ROWS in ALV tree

  • Excel report generation does not exit excel

    I am using the excel report generator to save test reports.  I can create the report using a template and write to it when needed with no problems.  After every test step I add data and save the report.  I keep excel closed by using the no change setting for the window state.  I do not want the user to see excel or even know it is there.
    The issue is when I am done testing and use the dispose report vi, it leaves an instance of excel open that you can see in the task manager.  And the only way to close that instance is to open one of the files that was created and close it and then exit excel.  The memory used by that instance grows a little each time a new file is created.
    Labview 2011 SP1 (11.0.1.F2 32bit)
    Excel 2007
    How can I close excel completely after each test?
    Solved!
    Go to Solution.
    Attachments:
    Report Example.png ‏52 KB

    I find it very hard to believe that this function isn't somewhere in the report generation toolkit.  But my 30 second look for it came up with nothing.  So instead I wrote a function that does a task kill for you.  Keep in mind this only works in Windows, and this will do the same thing as a end task in Taskmanager so only use it when you are sure your are done saving all reporting.  Saved in 2011.
    Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
    If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.
    Attachments:
    Taskkill Excel Report.vi ‏22 KB

  • Report generation broken VIs in LV2009

    Hi,
    C:\Program Files\National Instruments\LabVIEW 8.2\vi.lib\Utility\NIReport llb has 2 VIS "Get modified data" and "Set modified data" which are used by Report generation tool kit .
    I installed LV2009 in which "Get modified data" and "Set modified data" are not present. When i installed report generation toolkit then, the report generation VIs in "LV2009\vi.lib\addons\_office" VIs are broken because they are search for above mentioned VIs.
    Report generation 1.1.1 is what i am using.
    Please suggest me a solution.
    Regards,
    Muthuraman S
    Message Edited by Muthuraman on 10-29-2009 01:10 AM
    Regards,
    Muthuraman

    yes might be, why don't you use the report generation toolkit along with the developer suite.
    because same thing happened to me when i installed Report generation 1.1.1 with LabVIEW 8.6, then installed Version 1.1.2 which was along with developer suite.
    Regards
    VIsuman

  • Report generation toolkit: Get all excel worksheets

    Hej everybody,
    how can I get a list (name and number) of all worksheets in an Excelfile using the report generation toolkit and Labview 8.2?
    Thanks for answers,
    Christoph

    Hi,
    I made the similar application using excel dll in LabVIEW 7.1 
    Try this...
    Regards
    DC
    Attachments:
    Excel_Worksheets.vi ‏48 KB

  • WebUtil and Microsoft Excel: Setting cell border properties

    I'm using the CLIENT_OLE2 package shipped with WebUtil to create a Microsoft Excel spreadsheet from an Oracle 10g Form and, so far, have managed to:
    - Create multiple worksheets
    - Populate cells with values and formulae
    - Format cells, including setting font name and size, setting bold italic and underline attributes
    The final requirement is to set a border on a cell or group of cells, but this is where I'm stumped. My code thus far looks like this:
    DECLARE
      l_application   CLIENT_OLE2.OBJ_TYPE ;
      l_workbooks     CLIENT_OLE2.OBJ_TYPE ;
      l_workbook      CLIENT_OLE2.OBJ_TYPE ;
      l_worksheets    CLIENT_OLE2.OBJ_TYPE ;
      l_worksheet     CLIENT_OLE2.OBJ_TYPE ;
      l_cell          CLIENT_OLE2.LIST_TYPE ;
      l_borders       CLIENT_OLE2.OBJ_TYPE ;
    BEGIN   
      l_application := CLIENT_OLE2.CREATE_OBJ('Excel.Application') ;
      l_workbooks := CLIENT_OLE2.GET_OBJ_PROPERTY(l_application,'Workbooks') ;
      l_workbook := CLIENT_OLE2.GET_OBJ_PROPERTY(l_workbooks,'Add') ;
      l_worksheets := CLIENT_OLE2.GET_OBJ_PROPERTY(l_workbook,'Worksheets') ;
      l_arguments := CLIENT_OLE2.CREATE_ARGLIST ;
      CLIENT_OLE2.ADD_ARG(l_arguments,'Sheet1') ;
      l_worksheet := CLIENT_OLE2.GET_OBJ_PROPERTY(l_workbook,'Worksheets',l_arguments) ;
      CLIENT_OLE2.DESTROY_ARGLIST(l_arguments) ;
    --  Select cell A1
      l_arguments := CLIENT_OLE2.CREATE_ARGLIST ;
      CLIENT_OLE2.ADD_ARG(l_arguments,1) ;
      CLIENT_OLE2.ADD_ARG(l_arguments,1) ;
      l_cell := CLIENT_OLE2.GET_OBJ_PROPERTY(l_worksheet,'Cells',l_arguments) ;
      CLIENT_OLE2.DESTROY_ARGLIST(l_arguments) ;
      l_borders := CLIENT_OLE2.GET_OBJ_PROPERTY(p_cells,'Borders') ;
    --  What happens next...?
    --  Clean up
      CLIENT_OLE2.RELEASE_OBJ(l_borders) ;
      CLIENT_OLE2.RELEASE_OBJ(l_worksheet) ;
      CLIENT_OLE2.RELEASE_OBJ(l_worksheets) ;
      CLIENT_OLE2.RELEASE_OBJ(l_workbook) ;
      CLIENT_OLE2.RELEASE_OBJ(l_workbooks) ;
      CLIENT_OLE2.RELEASE_OBJ(l_application) ;
    END ;I'd be obliged for a pointer in the right direction!

    Well, in spite of 80-odd views, it looks like I've answered my own question.
    The borders around a range of cells in Excel are actually separate elements of the Borders object. You need to specify which border you want and set it individually. The code below draws a border around cells A1 to C3. Note the constants defined at the top of the listing; these are the "actual" values of the corresponding Excel constants that are referenced in the VBA code if you draw the border by hand while recording a macro.
    Enjoy!
    DECLARE
      c_automatic     CONSTANT NUMBER := -4105 ;  -- ColorIndex = xlAutomatic
      c_thin          CONSTANT NUMBER := 2 ;      -- Weight = xlThin
      c_medium        CONSTANT NUMBER := -4138 ;  -- Weight = xlMedium
      c_thick         CONSTANT NUMBER := 4 ;      -- Weight = xlThick
      c_continuous    CONSTANT NUMBER := 1 ;      -- LineStyle = xlContinuous
      c_edge_left     CONSTANT NUMBER := 7 ;      -- Border = xlEdgeLeft
      c_edge_top      CONSTANT NUMBER := 8 ;      -- Border = xlEdgeTop
      c_edge_bottom   CONSTANT NUMBER := 9 ;      -- Border = xlEdgeBottom
      c_edge_right    CONSTANT NUMBER := 10 ;     -- Border = xlEdgeRight
      l_application   CLIENT_OLE2.OBJ_TYPE ;
      l_workbooks     CLIENT_OLE2.OBJ_TYPE ;
      l_workbook      CLIENT_OLE2.OBJ_TYPE ;
      l_worksheets    CLIENT_OLE2.OBJ_TYPE ;
      l_worksheet     CLIENT_OLE2.OBJ_TYPE ;
      l_range         CLIENT_OLE2.LIST_TYPE ;
      PROCEDURE draw_border (
        p_range       IN CLIENT_OLE2.LIST_TYPE,
        p_side        IN NUMBER,
        p_weight      IN NUMBER)
      IS
        l_edge      CLIENT_OLE2.LIST_TYPE ;
        l_border    CLIENT_OLE2.OBJ_TYPE ;
      BEGIN
        l_edge := CLIENT_OLE2.CREATE_ARGLIST ;
        CLIENT_OLE2.ADD_ARG(l_edge,p_side) ;
        l_border := CLIENT_OLE2.GET_OBJ_PROPERTY(l_range,'Borders',l_edge) ;
        CLIENT_OLE2.DESTROY_ARGLIST(l_edge) ;
        CLIENT_OLE2.SET_PROPERTY(l_border,'LineStyle',c_continuous) ;
        CLIENT_OLE2.SET_PROPERTY(l_border,'Weight',p_weight) ;
        CLIENT_OLE2.SET_PROPERTY(l_border,'ColorIndex',c_automatic) ;
        CLIENT_OLE2.RELEASE_OBJ(l_border) ;
      END draw_border ;
    BEGIN   
      l_application := CLIENT_OLE2.CREATE_OBJ('Excel.Application') ;
      l_workbooks := CLIENT_OLE2.GET_OBJ_PROPERTY(l_application,'Workbooks') ;
      l_workbook := CLIENT_OLE2.GET_OBJ_PROPERTY(l_workbooks,'Add') ;
      l_worksheets := CLIENT_OLE2.GET_OBJ_PROPERTY(l_workbook,'Worksheets') ;
      l_arguments := CLIENT_OLE2.CREATE_ARGLIST ;
      CLIENT_OLE2.ADD_ARG(l_arguments,'Sheet1') ;
      l_worksheet := CLIENT_OLE2.GET_OBJ_PROPERTY(l_workbook,'Worksheets',l_arguments) ;
      CLIENT_OLE2.DESTROY_ARGLIST(l_arguments) ;
    --  Select the box with top-left of A1 and bottom-right of C3.
      l_arguments := CLIENT_OLE2.CREATE_ARGLIST ;
      CLIENT_OLE2.ADD_ARG(l_arguments,'A1:C3') ;
      l_range := CLIENT_OLE2.GET_OBJ_PROPERTY(p_worksheet,'Range',l_arguments) ;
      CLIENT_OLE2.DESTROY_ARGLIST(l_arguments) ;
    --  Draw border along the left edge of cells in range
      draw_border(l_range,c_edge_left,c_thick) ;
    --  Draw border along the top edge of cells in range
      draw_border(l_range,c_edge_top,c_thick) ;
    --  Draw border along the right edge of cells in range
      draw_border(l_range,c_edge_right,c_thick) ;
    --  Draw border along the bottom edge of cells in range
      draw_border(l_range,c_edge_bottom,c_thick) ;
    --  Clean up
      CLIENT_OLE2.RELEASE_OBJ(l_range) ;
      CLIENT_OLE2.RELEASE_OBJ(l_worksheet) ;
      CLIENT_OLE2.RELEASE_OBJ(l_worksheets) ;
      CLIENT_OLE2.RELEASE_OBJ(l_workbook) ;
      CLIENT_OLE2.RELEASE_OBJ(l_workbooks) ;
      CLIENT_OLE2.RELEASE_OBJ(l_application) ;
    END ;It's worth pointing out that the code above has been culled from my specific procedure and has been simplified. It hasn't been tested, although the DRAW_BORDER nested procedure has been copied straight from working code.

  • Does Numbers support Excel functions CELL, SUBSTITUTE, and REDIRECT?

    Been trying to find the list of Excel-compatible functions but did not succeed. I would like to use Numbers to edit my Excel files in iPad. I often generate reports by pulling data out from a seperate sheet using Excel functions like CELL, SUBSTITUTE, and REDIRECT. I have not purchased Numbers yet, that is why I would like to know where I find the complete list of Excel-compatible functions or at least know if Numbers support these functions.  Thank you in advance.

    Numbers does support the function substitute()
    I did not see the functions cell() and redirect() in the function browser.
    There is afree function reference here:
    iWork '09 Formulas and Functions User Guide
    which you can use

Maybe you are looking for