Automatic VI description

Since I'm involved in some big projects I wonder if there is an option to automatically add some previously set description in a new VI created in LV? Assume I want to avoid adding my signature and other repeatable significant info in each VI added to project. This seems to be an easy feature but I haven't discovered something like that before.

You can create a VI template. 
http://zone.ni.com/reference/en-XX/help/371361J-01/lvhowto/creating_vi_templates/
Scripting is not strictly neccesary to update the VI description. You can use basic functions to load a VI into memory, modify the Description by way of a property node, and then save the VI.
http://forums.ni.com/t5/LabVIEW/Programmatically-modifying-a-VI-s-Description/td-p/612300
Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
If you don't hate time zones, you're not a real programmer.
"You are what you don't automate"
Inplaceness is synonymous with insidiousness

Similar Messages

  • Automatic axis description for charts in BEx 7.0

    In BEx Analyzer 7.0, if I have a simple table and hit the 'Chart' button, it creates the graph but does not put the descriptors on the X axis.  The X axis has numbers (the same amount as the number of rows).  What I want is for it to automatically populate the description instead of putting a number.
    Here is what I get.
    100  |
    50
    0
              1       2       3       4     5
    Here is what I want.
    100
    50
            |
    0      |----
              TX     CA    NV     OK     TN
    How can I have the X axis automatically put in dexcriptors instead of numbers?

    Hi Ronald,
    The chart Report will show, what ever is displayed in your table Report. Probably you have selected. Right click on Chart and select "Select Data" and see waht is selected for Rows and columns. For example in first column you have customer and if it is set as display Key in table it will show you Key in chart as well.
    Do some Trial and error with "Select Data source" option in Chart, you will get the desired result.
    Regards,
    Kams

  • Automatic material description

    Hi gurus,
    I am using table control.i am input material number then i want material discription come automatically in next coloum of table control.
    How can i do the coding for this.
    Pls. guided me.
    Best Regards.
    Pravin

    Hi,
    In PAI module, when you are looping at the table control. When you are modifying the table control data to internal table, before that fetch the material description and populate the respective field of the internal table. And during PBO, when you are reading the internal table automatically the material desc wil be displayed.
    Thanks & Regards,
    Navneeth K.

  • How can I automatically include photo descriptions when creating a book through iPhoto so that I don't have to type them all again?

    I am scanning hundreds of old photographs onto my iMac and including descriptions when I import them to iPhoto.  When I have created a book as a test, the photo descriptions are not automatically included.  I don't want to have to add captions to the book I've created so how do I automaticaly include each description with the photograph?

    There are no themes that automatically add descriptions that have been added to the photos. The Folio theme will pickup the file name and user name of the account
    but not the description.
    OT

  • How to streamline process of adding descriptions in Book mode

    Working through completing a Photo Book. Understand how to add text to each photo and make changes.
    My question concerns streamlining the process of adding my descriptions I attached to each photo when first ordered. Instead of having to click to the Library from the Project, search for the photo, copy the description, then click again on the Project and the page I'm working on, is there a way to obtain the photo description while I am editing the Book page?
    I apologize if this has been answered previously, but did not find a similar Q&A while moving through the discussion group.

    Old Toad, thank you. That is the answer I expected, but didn't hurt to ask. I wil follow your suggestion and make a feature request to Apple Co.
    Old Toad wrote:
    I've not found a way to do that.  There's only one theme, Folio,  that has info/descriptions boxes for every photo on every page and it only enters the title automatically.
    Send a feature request to Apple via http://www.apple.com/feedback/iphoto.html for a way to automatically add descriptions to a photos's text box in the theme.
    OT

  • How can I automatically reconnect NAS shares when disconnected?

    I have a Seagate BlackArmor 110 NAS device I use as a media repository. I have my Mac Mini setup to auto-connect to the NAS when login occurs. The problem is, intermittently the connection is severed, and the only way to reconnect is to logout and log back in. Unfortunately, it seems to happen when I am traveling and am unable to do so.
    Is there a way to "ping" or pulse the share, and if it disconnects, to have it auto-reconnect? Both the NAS and the Mac Mini are hard wired through a Gigabit switch, so it isn't a wireless "hiccup".
    Thanks.

    There are no themes that automatically add descriptions that have been added to the photos. The Folio theme will pickup the file name and user name of the account
    but not the description.
    OT

  • Default description of interaction in Interaction centre

    Hi All,
    Currently whenever we end the interaction on Web IC,interaction is created automatically with description empty.
    Our requirment is to default the description text for the interaction record if user does not create the interaction manually in Web IC.
    Please help.
    Regards
    Nikhil

    Hi NIkhil,
    This question has already been posted and answered in another thread.
    Default description in the interaction record in interaction centre
    Thanks
    Vishal

  • Auto filling field description should be done by selecting Field number

    Hi,
    I have created EEW fields (Number and description) in UI 7.0.
    Now I am selection one record from drop down e.g. Code number, based on that description has to fill in second field automatically (code description). Pulling the data should be from data base.
    2nd : Selection of description should be language Dependant. (Base on Logon language)
    I agree, this functionality is provided by AET
    Kindly suggest where and how to code the functionalities.
    Shakeer

    A simple example.  May not meet your needs depending on the number of products.
    Droplist named ProductCode
    Text Fields named Description and Price
    Java Script the droplist on the change event
    if (xfa.event.newText=="5864-98723-124")
    {Description.rawValue="Black Pens"
    Price.rawValue="$5.25"

  • Summing up a Column in ALV report

    Hi All,
    I have developed an ALV Report which will display Invoices and other details.
    Now i need to display the sum of NETWR column, if user wish to select that column and click the "SUM" icon.
    As of now, if i select the NETWR column and click 'SUM" column, i am getting Runtime error.
    How to resolve this issue?
    Regards
    Pavan

    Hi Pavan,
    ALV GRID CONTROL:
    This task is performed by the SAP Control Framework.
    The R/3 System allows you to create custom controls using ABAP Objects. The application server is the Automation Client, which drives the custom controls (automation server) at the front end.
    If custom controls are to be included on the frontend, then the SAPGUI acts as a container for them.
    Custom controls can be ActiveX Controls or JavaBeans.
    The system has to use a Remote Function Call (RFC) to transfer methods for creating and using a control to the front end.
    ABAP objects are used to implement the controls in programs.
    An SAP Container can contain other controls (for example, SAP ALV Grid Control, Tree Control, SAP Picture Control, SAP Splitter Control, and so on). It administers these controls logically in one collection and provides a physical area for the display.
    Every control exists in a container. Since containers are themselves controls, they can be nested within one another. The container becomes the parent of its control. SAP containers are divided into five groups:
    SAP custom container: Displays within an area defined in Screen Painter on screens or sub screens.
    Class: CL_GUI_CUSTOM_CONTAINER
    SAP dialog box container: Displays in a modeless dialog box or as a full screen. Class:
    CL_GUI_DIALOGBOX_CONTAINER
    SAP docking container: Displays as docked, resizable sub-window with the option of displaying it as a modeless dialog box. Class: CL_GUI_DOCKING_CONTAINER
    SAP splitter container: Displays and groups several controls in one area - that is, splits the area into cells Class: CL_GUI_SPLITTER_CONTAINER
    SAP easy splitter container: Displays controls in two cells, which the user can resize using a split bar. Class: CL_GUI_EASY_SPLITTER_CONTAINER.
    In the control, you can adjust the column width by dragging, or use the 'Optimum width' function to adjust the column width to the data currently displayed. You can also change the column sequence by selecting a column and dragging it to a new position.
    Standard functions are available in the control toolbar. The details display displays the fields in the line on which the cursor is positioned in a modal dialog box.
    The sort function in the ALV Control is available for as many columns as required. You can set complex sort criteria and sort columns in either ascending or descending order.
    You can use the 'Search' function to search for a string (generic search without *) within a selected area by line or column.
    You can use the 'Sum' function to create totals for one or more numeric columns. You can then use the "Subtotals" function to set up control level lists: You can use the 'Subtotal' function to structure control level lists: select the columns (non-numeric columns only) that you want to use and the corresponding control level totals are displayed.
    For 'Print' and 'Download' the whole list is always processed, not just the sections displayed on the screen.
    You can define display variants to meet your own specific requirements. For information on saving variants, see 'Advanced Techniques'.
    The ALV grid control is a generic tool for displaying lists in screens. The control offers standard functions such as sorting by any column, adding numeric columns, and fixed lead columns .
    Data collection is performed in the program (with SELECT statements, for example) or by using a logical database. The data records are saved in an internal table and passed on to the ALV control along with a field description.
    The field description contains information about the characteristics of each column, such as the column header and output length. This information can defined either globally in the Dictionary (structure in the Dictionary) or in the field catalog in the program itself. You can also merge both techniques.
    The ALV link is a standard function of Query and QuickViewer. If multiline queries or Quick View lists have been defined, they will automatically be compressed to a single line and output in the ALV control as a long, single line list.
    Use Screen Painter to create a sub screen container for the ALV grid control. The control requires an area where it can be displayed in the screen. You have to create a container control that determines this area.
    Use the corresponding icon in the Screen Painter layout to create the container control. The size of area "MY_CONTROL_AREA" determines the subsequent size of the ALV control.
    The valid GUI status must be set at the PBO event in the flow logic of the ALV subscreen container.
    The OK_CODE processing for the cancel functions must be programmed at the PAI event.
    The reference variables for the custom container and the ALV grid control must be declared.
    To create reference variables, use ABAP statement TYPE REF TO .
    The global classes you need to do this are called cl_gui_custom_container (for the custom container control) and cl_gui_alv_grid (for the ALV grid control).
    The global classes are defined in the Class Builder. You can use the Class Builder to display information for the methods, their parameters, exceptions, and so on.
    Use ABAP statement CREATE OBJECT to create the objects for the container and the ALV control. Objects Are instances of a class.
    When an object is created (CREATE), method CONSTRUCTOR of the corresponding class is executed. The parameters of method CONSTRUCTOR determine which parameters have to be supplied with data when the object is created. In the above example, object alv_grid is given the name of the container control (g_custom_container) in exporting parameter i_parent, which links the two controls. For information on which parameters method CONSTRUCTOR possesses and which of these parameters are required, see the Class Builder.
    Objects should only be created once during the program. To ensure that this is the case, enclose the CREATE OBJECT statement(s) in an IF IS INITIAL. ... ENDIF clause. The objects must be generated before the control is displayed for the first time - that is, during the PBO event of the ALV subscreen container.
    To display the requested dataset in the ALV control, the data must be passed on to the control as an internal table, and a field description must exist indicating the order in which the columns will be output.
    In the simplest case, the field description can use a structure from the Dictionary. The Dictionary also determines the technical field attributes like type and length, as well as the semantic attributes like short and long texts. The ALV control uses this information to determine the column widths and headers. The column sequence is determined by the field sequence in the structure.
    If no suitable structure is active in the Dictionary, or you want to output internal program fields in the control, then you will have to define information like the output length and column header in the field catalog.
    In a typical program run, the dataset is read first (SELECT ....), the internal table is filled with the data to display (... INTO TABLE ...), and ABAP statement CALL SCREEN is then used to call the ALV sub screen container.
    The data transfer to the ALV control takes place during the call of method
    set_table_for_first_display from class cl_gui_alv_grid. The method call must be programmed at the PBO event of the ALV subscreen container.
    The name of the Dictionary structure that supplies the field description is specified in exporting parameter i_structure_name. The name of the internal table that contains the data records to display is specified in changing parameter it_outtab.
    The field description for the ALV control can be ta ken from an active Dictionary structure (fully automatic), by passing a field catalog (manual), or through a mixture of the two options (merge).
    The field catalog is in internal table with type lvc_t_fcat. This type is defined globally in the Dictionary.
    Each line in the field catalog table corresponds to a column in the ALV control.
    The field characteristics (= column characteristics) are defined in the field catalog. The field catalog is in internal table with type lvc_t_fcat. Each line that is explicitly described in the ALV control corresponds to a column in the field catalog table.
    The link to the data records to output that are saved in internal table is established through field name . This name must be specified in column "fieldname" in the field catalog.
    This field can be classified through a Dictionary reference (ref_table and ref_field) or by specifying an ABAP data type (inttype).
    Column headers and field names in the detail view of an ALV control line can be determined in the field catalog in coltext and seltext, respectively.
    The position of a field during output can be determined with col_pos in the field catalog.
    If you want to hide a column, fill field no_out with an "X" in the field catalog. Hidden fields can be displayed again in a user display variant.
    Icons can be displayed in the ALV control. If you want a column to be interpreted as an icon, then the icon name must be known to the program (include .) and icon = "X" must be specified for this column in the field catalog.
    The above example shows a semi-automatic field description: Part of the field description comes from the Dictionary structure (sflight), while another part is explicitly defined in the field catalog (gt_fieldcat).
    The field catalog (internal table) is filled in the program and is passed on together with the name of the Dictionary structure during the method call. The information is merged accordingly in method set_table_for_first_display.
    For a user to save display variants, parameters is_variant and i_save must be passed on during method call set_table_for_first_screen. To assign display variants uniquely to a program, at least the program name must be supplied in the transferred structure (gs_variant).
    Program names can be up to 30 characters long.
    If you only pass on the current parameters for is_variant, then existing variants can be loaded, but no new ones can be saved. If you use parameter i_save, you must pass on a variant structure with is_variant.
    I_SAVE = SPACE No variants can be saved.
    I_SAVE = 'U' The user can only save user-specific variants.
    I_SAVE = 'X' The user can only save general (shared) variants.
    I_SAVE = 'A' The user can save both user-specific and general (shared) variants.
    You can use parameter is_layout of method set_table_for_first_display, for example, to define the header in the ALV control and the detail display.
    To do this, define a query area in the program in accordance with Dictionary structure lvc_s_layo, and pass on the text to display in field -grid_title or -detailtitl.
    If you want to create print lists with zebra stripes, set field -zebra to "X". You can display a print preview for print lists by requesting standard function "Print".
    All parameters of method SET_TABLE_FOR_FIRST_DISPLAY from global class
    CL_GUI_ALV_GRID are defined in the Class Builder.
    Events are defined in global class cl_gui_alv_grid; you can use these events to implement user interaction within the program. To respond to a double -click on a table line, you must respond to event DOUBLE_CLICK.
    You receive control in the program, allowing you to implement interactive reporting - such as a full screen details list. The events for cl_gui_alv_grid are located in the Class Builder.
    To define an implement a local class in the program, you use a handler method. In this handler method, you program the functionality to trigger by a double -click in the output table.
    To activate a handler method at runtime, a class or an object from that class registers itself with an event using command SET HANDLER. The names of the IMPORTING parameters in the handler method correspond to the names of the EXPORTING parameters of the related event.
    In the above example, the local class is LCL_ILS and the handler method is ON_DBLCLICK. An object - ALV_DBLCLICK - is created and registers itself for event DOUBLE_CLICK.
    You can query parameter e_row-index to determine which output line was requested by the double -click. This parameter corresponds to the line number of the output table (internal table with the data records to output). If you need information for the selected line, you have to read it with READ TABLE itab INDEX e_row-index.
    This subsequent read in the output table generally corresponds to the HIDE area in conventional reporting. You first have to make sure that the user has double -clicked a line in the output table (similar to the valid line selection with the HIDE technique).
    A field group can contain global data objects, but not data objects that have been defined locally in a subroutine or function module.
    You can use INSERT to specify both fields and field symbols. This makes it possible to dynamically insert a data object referred to by a field symbol into a field group at runtime. Any field symbols that have not been assigned are ignored, which means no new field is inserted into the field group.
    The EXTRACT statement writes all the fields of a field group as one record to a sequential dataset (transport takes place with similarly named fields). If a HEADER field group is defined, then its fields are placed ahead of each record as sort keys. You can then sort the dataset with SORT and process it with LOOP ...ENDLOOP. In this case, no further EXTRACT is possible.
    The INSERT statement is not a declarative statement: This means field groups can also be expanded in the program flow section.
    As soon as the first dataset of a field group has been extracted with EXTRACT, that field group can no longer be expanded with INSERT. In particular, the HEADER field group cannot be expanded after the first EXTRACT (regardless of the field group).
    When the GET events are processed, the logical database automatically writes hexadecimal zeros in all the fields of a node when it returns to an upper-level node in the hierarchy. Since the HEADER normally contains sort fields for all field groups, these hexadecimal zeros in the HEADER serve as a type of hierarchy key: The more zeros there are, the further up in the control level hierarchy you go.
    &#61550;&#61472;The SORT statement sorts the extract dataset in accordance with the defined field sequence in field group HEADER. The addition BY ... sets a new sort key.
    Each must be either a field of field group HEADER or a field group that consists only of fields of the field group HEADER. You can use the additions ASCENDING and DESCENDING to determine whether the fields are sorted in ascending (default) or descending order.
    Fields containing X'00' in the logical databases are always displayed before all other values during a SORT.
    Processing of an extract dataset always takes places within a LOOP. The contents of the extract dataset field are placed in program fields with the same names.
    The group change always involves the fields of the HEADER. Single record processing for extract datasets is performed using language element AT ( = field group).
    CNT() is not a statement, but instead a field that is automatically create d and filled when is a non-numeric field from field group HEADER and is part of the sort key. At the end of the group, CNT() contains the number of different values that the field recorded in this group level.
    SUM() is not a statement, but instead a field that is automatically created and filled when is a numeric field of an extract dataset. At the end of the group, SUM() contains the control total of field .
    *** and CNT are only available at the end of the group level or at AT LAST.
    Single record processing for extract datasets AT WITH is only performed when field group is immediately followed by field group in the temporary dataset.
    Loops over an extract dataset cannot be nested. However, several contiguous loops are permitted.
    The sequence of the control level changes within the LOOP must correspond to the sort sequence.
    Totals can only be calculated within control footer processing.
    Extracts allow only appends (EXTRACT), sorting (SORT) and sequential processing (LOOP).
    Once a SORT or LOOP has occurred, the intermediate dataset is frozen and cannot be expanded with EXTRACT. Operations that insert into or delete from EXTRACT datasets are not supported.
    Extracts allow for several record types (FIELD-GROUPS) with fields that can be set dynamically (INSERT is not a declarative statement!). Internal tables have a single, statically-defined line type.
    Internal tables use the sequence of table fields according to the declaration for the hierarchy of the control leve l. The control level structure for internal tables is therefore static, and is independent of which criteria were used to sort the internal table.
    Extracts do not depend on the field sequence for control level processing: a re-sort or a completely different control level process can take place. The control level structure for extract datasets is therefore dynamic. It corresponds exactly to the sort key of the extract dataset. The sort key is the sequence of fields from the field group HEADER, and is used to sort the extract dataset.
    Extracts rely on the compiler to determine which combinations of group levels and a cumulating field the control level totals desire. The desired control level totals are determined by the processing of LOOP ... ENDLOOP blocks. Internal tables build the control level total with the SUM statement.
    This procedure leads to high resource depletion for totaling control levels in internal tables.
    Regards,
    Chandru

  • Setup problem - sql server 2014 - "could not find the database engine startup handle" - 0x851a0019

    I tried to install ,deleted and re-installed several times and no help at all.
    visual studio 2013 with update 2 rc and adk installed in my computer.
    error code: 0x851a0019
    error messege in setup: could not find the database engine startup handle
    edition: Microsoft SQL Server 2014 Enterprise (Evaluation)
    logs:
    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2061893607
      Start time:                    2014-04-03 13:53:29
      End time:                      2014-04-03 14:47:48
      Requested action:              Install
    Setup completed with required actions for features.
    Troubleshooting information for those features:
      Next step for RS:              Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for SQLEngine:       Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for DQ:              Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for FullText:        Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for Replication:     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
    Machine Properties:
      Machine name:                  ARIELUBA-PC
      Machine processor count:       8
      OS version:                    Windows 8
      OS service pack:               
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                    Feature                
                     Language             Edition              Version         Clustered  Configured
      SQL Server 2012      SQLEXPRESS           MSSQL11.SQLEXPRESS             Database Engine Services                 1033      
              Express Edition      11.1.3128.0     No         Yes       
      SQL Server 2012      SQLEXPRESS           MSSQL11.SQLEXPRESS             SQL Server Replication                   1033      
              Express Edition      11.1.3128.0     No         Yes       
      SQL Server 2012      ADK                  MSSQL11.ADK                    Database Engine Services            
        1033                 Express Edition      11.0.2100.60    No         Yes       
      SQL Server 2012      ADK                  MSSQL11.ADK                    SQL Server Replication              
        1033                 Express Edition      11.0.2100.60    No         Yes       
      SQL Server 2012                                                          LocalDB        
                             1033                 Express Edition      11.1.3412.0     No         Yes    
    Package properties:
      Description:                   Microsoft SQL Server 2014 
      ProductName:                   SQL Server 2014
      Type:                          RTM
      Version:                       12
      SPLevel:                       0
      Installation location:         C:\Users\Arie Luba\Downloads\WS2012R2DC\SQLServer2014-x64-ENU\x64\setup\
      Installation edition:          Evaluation
    Product Update Status:
      None discovered.
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      true
      AGTSVCACCOUNT:                 NT Service\SQLSERVERAGENT
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Manual
      ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Backup
      ASCOLLATION:                   Hebrew_CI_AS
      ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Config
      ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Data
      ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Log
      ASPROVIDERMSOLAP:              1
      ASSERVERMODE:                  MULTIDIMENSIONAL
      ASSVCACCOUNT:                  NT Service\MSSQLServerOLAPService
      ASSVCPASSWORD:                 <empty>
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            ARIELUBA-PC\Arie Luba
      ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Temp
      BROWSERSVCSTARTUPTYPE:         Automatic
      CLTCTLRNAME:                   
      CLTRESULTDIR:                  C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir\
      CLTSTARTUPTYPE:                Manual
      CLTSVCACCOUNT:                 NT Service\SQL Server Distributed Replay Client
      CLTSVCPASSWORD:                <empty>
      CLTWORKINGDIR:                 C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir\
      COMMFABRICENCRYPTION:          0
      COMMFABRICNETWORKLEVEL:        0
      COMMFABRICPORT:                0
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_135327\ConfigurationFile.ini
      CTLRSTARTUPTYPE:               Manual
      CTLRSVCACCOUNT:                NT Service\SQL Server Distributed Replay Controller
      CTLRSVCPASSWORD:               <empty>
      CTLRUSERS:                     ARIELUBA-PC\Arie Luba
      ENABLERANU:                    false
      ENU:                           true
      ERRORREPORTING:                false
      FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, MDS
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher
      FTSVCPASSWORD:                 <empty>
      HELP:                          false
      IACCEPTSQLSERVERLICENSETERMS:  true
      INDICATEPROGRESS:              false
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    MSSQLSERVER
      INSTANCENAME:                  MSSQLSERVER
      ISSVCACCOUNT:                  NT Service\MsDtsServer120
      ISSVCPASSWORD:                 <empty>
      ISSVCSTARTUPTYPE:              Automatic
      MATRIXCMBRICKCOMMPORT:         0
      MATRIXCMSERVERNAME:            <empty>
      MATRIXNAME:                    <empty>
      NPENABLED:                     0
      PID:                           *****
      QUIET:                         false
      QUIETSIMPLE:                   false
      ROLE:                          AllFeatures_WithDefaults
      RSINSTALLMODE:                 DefaultNativeMode
      RSSHPINSTALLMODE:              SharePointFilesOnlyMode
      RSSVCACCOUNT:                  NT Service\ReportServer
      RSSVCPASSWORD:                 <empty>
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         <empty>
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  Hebrew_CI_AS
      SQLSVCACCOUNT:                 NT Service\MSSQLSERVER
      SQLSVCPASSWORD:                <empty>
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           ARIELUBA-PC\Arie Luba
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  false
      TCPENABLED:                    1
      UIMODE:                        Normal
      UpdateEnabled:                 true
      UpdateSource:                  MU
      USEMICROSOFTUPDATE:            false
      X86:                           false
      Configuration file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_135327\ConfigurationFile.ini
    Detailed results:
      Feature:                       Management Tools - Complete
      Status:                        Passed
      Feature:                       Client Tools Connectivity
      Status:                        Passed
      Feature:                       Client Tools SDK
      Status:                        Passed
      Feature:                       Client Tools Backwards Compatibility
      Status:                        Passed
      Feature:                       Management Tools - Basic
      Status:                        Passed
      Feature:                       Reporting Services - Native
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred during the setup process of the feature.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       Data Quality Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       Full-Text and Semantic Extractions for Search
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       Master Data Services
      Status:                        Passed
      Feature:                       Distributed Replay Client
      Status:                        Passed
      Feature:                       Distributed Replay Controller
      Status:                        Passed
      Feature:                       Integration Services
      Status:                        Passed
      Feature:                       Data Quality Client
      Status:                        Passed
      Feature:                       Analysis Services
      Status:                        Passed
      Feature:                       Reporting Services - SharePoint
      Status:                        Passed
      Feature:                       Reporting Services Add-in for SharePoint Products
      Status:                        Passed
      Feature:                       SQL Browser
      Status:                        Passed
      Feature:                       Documentation Components
      Status:                        Passed
      Feature:                       SQL Writer
      Status:                        Passed
      Feature:                       Setup Support Files
      Status:                        Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_135327\SystemConfigurationCheck_Report.htm
    2014-04-03 14:14:28.01 Server      Microsoft SQL Server 2014 - 12.0.2000.8 (X64) 
    Feb 20 2014 20:04:26 
    Copyright (c) Microsoft Corporation
    Enterprise Evaluation Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)
    2014-04-03 14:14:28.01 Server      UTC adjustment: 3:00
    2014-04-03 14:14:28.01 Server      (c) Microsoft Corporation.
    2014-04-03 14:14:28.01 Server      All rights reserved.
    2014-04-03 14:14:28.01 Server      Server process ID is 7148.
    2014-04-03 14:14:28.01 Server      System Manufacturer: 'Dell Inc.', System Model: 'Inspiron N5110'.
    2014-04-03 14:14:28.01 Server      Authentication mode is WINDOWS-ONLY.
    2014-04-03 14:14:28.01 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
    2014-04-03 14:14:28.01 Server      The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.
    2014-04-03 14:14:28.01 Server      Registry startup parameters: 
    -d C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\master.mdf
    -e C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG
    -l C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
    2014-04-03 14:14:28.01 Server      Command Line Startup Parameters:
    -s "MSSQLSERVER"
    -m "SqlSetup"
    -Q
    -q "Hebrew_CI_AS"
    -T 4022
    -T 4010
    -T 3659
    -T 3610
    -T 8015
    2014-04-03 14:14:28.28 Server      SQL Server detected 1 sockets with 4 cores per socket and 8 logical processors per socket, 8 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message;
    no user action is required.
    2014-04-03 14:14:28.28 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2014-04-03 14:14:28.28 Server      Detected 8099 MB of RAM. This is an informational message; no user action is required.
    2014-04-03 14:14:28.28 Server      Using conventional memory in the memory manager.
    2014-04-03 14:14:28.31 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
    2014-04-03 14:14:28.34 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
    2014-04-03 14:14:28.36 Server      Query Store settings initialized with enabled = 1, 
    2014-04-03 14:14:28.36 Server      The maximum number of dedicated administrator connections for this instance is '1'
    2014-04-03 14:14:28.36 Server      Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
    only. No user action is required.
    2014-04-03 14:14:28.38 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2014-04-03 14:14:28.39 Server      Database Mirroring Transport is disabled in the endpoint configuration.
    2014-04-03 14:14:28.39 spid8s      Warning ******************
    2014-04-03 14:14:28.39 spid8s      SQL Server started in single-user mode. This an informational message only. No user action is required.
    2014-04-03 14:14:28.40 spid8s      Starting up database 'master'.
    2014-04-03 14:14:28.42 Server      Software Usage Metrics is disabled.
    2014-04-03 14:14:28.48 Server      CLR version v4.0.30319 loaded.
    2014-04-03 14:14:28.56 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
    2014-04-03 14:14:28.62 spid8s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
    2014-04-03 14:14:28.63 spid8s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
    2014-04-03 14:14:28.64 spid8s      SQL Trace ID 1 was started by login "sa".
    2014-04-03 14:14:28.64 spid8s      Server name is 'ARIELUBA-PC'. This is an informational message only. No user action is required.
    2014-04-03 14:14:28.65 spid16s     Password policy update was successful.
    2014-04-03 14:14:28.66 spid16s     Error: 17190, Severity: 16, State: 1.
    2014-04-03 14:14:28.66 spid16s     Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
    2014-04-03 14:14:28.66 spid16s     Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
    2014-04-03 14:14:28.66 spid16s     Error: 17182, Severity: 16, State: 1.
    2014-04-03 14:14:28.66 spid16s     TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property. 
    2014-04-03 14:14:28.66 spid16s     Error: 17182, Severity: 16, State: 1.
    2014-04-03 14:14:28.66 spid16s     TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property. 
    2014-04-03 14:14:28.66 spid16s     Error: 17826, Severity: 18, State: 3.
    2014-04-03 14:14:28.66 spid16s     Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
    2014-04-03 14:14:28.67 spid16s     Error: 17120, Severity: 16, State: 1.
    2014-04-03 14:14:28.67 spid16s     SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
    ________________________________________________________________________________________________

    Is it okay? (see below)
    ;SQL Server 2014 Configuration File
    [OPTIONS]
    ; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter. 
    ACTION="Install"
    ; Detailed help for command line argument ROLE has not been defined yet. 
    ROLE="AllFeatures_WithDefaults"
    ; Use the /ENU parameter to install the English version of SQL Server on your localized Windows operating system. 
    ENU="True"
    ; Parameter that controls the user interface behavior. Valid values are Normal for the full UI,AutoAdvance for a simplied UI, and EnableUIOnServerCore for bypassing Server Core setup GUI block. 
    UIMODE="Normal"
    ; Setup will not display any user interface. 
    QUIET="False"
    ; Setup will display progress only, without any user interaction. 
    QUIETSIMPLE="False"
    ; Specify whether SQL Server Setup should discover and include product updates. The valid values are True and False or 1 and 0. By default SQL Server Setup will include updates that are found. 
    UpdateEnabled="True"
    ; Specify if errors can be reported to Microsoft to improve future SQL Server releases. Specify 1 or True to enable and 0 or False to disable this feature. 
    ERRORREPORTING="False"
    ; If this parameter is provided, then this computer will use Microsoft Update to check for updates. 
    USEMICROSOFTUPDATE="False"
    ; Specifies features to install, uninstall, or upgrade. The list of top-level features include SQL, AS, RS, IS, MDS, and Tools. The SQL feature will install the Database Engine, Replication, Full-Text, and Data Quality Services (DQS) server. The Tools feature
    will install Management Tools, Books online components, SQL Server Data Tools, and other shared components. 
    FEATURES=SQLENGINE,REPLICATION,FULLTEXT,DQ,AS,RS,RS_SHP,RS_SHPWFE,DQC,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,DREPLAY_CTLR,DREPLAY_CLT,MDS
    ; Specify the location where SQL Server Setup will obtain product updates. The valid values are "MU" to search Microsoft Update, a valid folder path, a relative path such as .\MyUpdates or a UNC share. By default SQL Server Setup will search Microsoft Update
    or a Windows Update service through the Window Server Update Services. 
    UpdateSource="MU"
    ; Displays the command line parameters usage 
    HELP="False"
    ; Specifies that the detailed Setup log should be piped to the console. 
    INDICATEPROGRESS="False"
    ; Specifies that Setup should install into WOW64. This command line argument is not supported on an IA64 or a 32-bit system. 
    X86="False"
    ; Specify the root installation directory for shared components.  This directory remains unchanged after shared components are already installed. 
    INSTALLSHAREDDIR="C:\Program Files\Microsoft SQL Server"
    ; Specify the root installation directory for the WOW64 shared components.  This directory remains unchanged after WOW64 shared components are already installed. 
    INSTALLSHAREDWOWDIR="C:\Program Files (x86)\Microsoft SQL Server"
    ; Specify a default or named instance. MSSQLSERVER is the default instance for non-Express editions and SQLExpress for Express editions. This parameter is required when installing the SQL Server Database Engine (SQL), Analysis Services (AS), or Reporting Services
    (RS). 
    INSTANCENAME="MSSQLSERVER"
    ; Specify that SQL Server feature usage data can be collected and sent to Microsoft. Specify 1 or True to enable and 0 or False to disable this feature. 
    SQMREPORTING="False"
    ; Specify the Instance ID for the SQL Server features you have specified. SQL Server directory structure, registry structure, and service names will incorporate the instance ID of the SQL Server instance. 
    INSTANCEID="MSSQLSERVER"
    ; The computer name that the client communicates with for the Distributed Replay Controller service. 
    CLTCTLRNAME="SQLDRC"
    ; The Windows account(s) used to grant permission to the Distributed Replay Controller service. 
    CTLRUSERS="ARIELUBA-PC\Arie Luba"
    ; The account used by the Distributed Replay Controller service. 
    CTLRSVCACCOUNT="NT Service\SQL Server Distributed Replay Controller"
    ; The startup type for the Distributed Replay Controller service. 
    CTLRSTARTUPTYPE="Manual"
    ; The account used by the Distributed Replay Client service. 
    CLTSVCACCOUNT="NT Service\SQL Server Distributed Replay Client"
    ; The startup type for the Distributed Replay Client service. 
    CLTSTARTUPTYPE="Manual"
    ; The result directory for the Distributed Replay Client service. 
    CLTRESULTDIR="C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir"
    ; The working directory for the Distributed Replay Client service. 
    CLTWORKINGDIR="C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir"
    ; RSInputSettings_RSInstallMode_Description 
    RSINSTALLMODE="DefaultNativeMode"
    ; RSInputSettings_RSInstallMode_Description 
    RSSHPINSTALLMODE="SharePointFilesOnlyMode"
    ; Specify the installation directory. 
    INSTANCEDIR="C:\Program Files\Microsoft SQL Server"
    ; Agent account name 
    AGTSVCACCOUNT="NT Service\SQLSERVERAGENT"
    ; Auto-start service after installation.  
    AGTSVCSTARTUPTYPE="Manual"
    ; Startup type for Integration Services. 
    ISSVCSTARTUPTYPE="Automatic"
    ; Account for Integration Services: Domain\User or system account. 
    ISSVCACCOUNT="NT Service\MsDtsServer120"
    ; The name of the account that the Analysis Services service runs under. 
    ASSVCACCOUNT="NT Service\MSSQLServerOLAPService"
    ; Controls the service startup type setting after the service has been created. 
    ASSVCSTARTUPTYPE="Automatic"
    ; The collation to be used by Analysis Services. 
    ASCOLLATION="Hebrew_CI_AS"
    ; The location for the Analysis Services data files. 
    ASDATADIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Data"
    ; The location for the Analysis Services log files. 
    ASLOGDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Log"
    ; The location for the Analysis Services backup files. 
    ASBACKUPDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Backup"
    ; The location for the Analysis Services temporary files. 
    ASTEMPDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Temp"
    ; The location for the Analysis Services configuration files. 
    ASCONFIGDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Config"
    ; Specifies whether or not the MSOLAP provider is allowed to run in process. 
    ASPROVIDERMSOLAP="1"
    ; Specifies the list of administrator accounts that need to be provisioned. 
    ASSYSADMINACCOUNTS="ARIELUBA-PC\Arie Luba"
    ; Specifies the server mode of the Analysis Services instance. Valid values are MULTIDIMENSIONAL and TABULAR. The default value is MULTIDIMENSIONAL. 
    ASSERVERMODE="MULTIDIMENSIONAL"
    ; CM brick TCP communication port 
    COMMFABRICPORT="0"
    ; How matrix will use private networks 
    COMMFABRICNETWORKLEVEL="0"
    ; How inter brick communication will be protected 
    COMMFABRICENCRYPTION="0"
    ; TCP port used by the CM brick 
    MATRIXCMBRICKCOMMPORT="0"
    ; Startup type for the SQL Server service. 
    SQLSVCSTARTUPTYPE="Automatic"
    ; Level to enable FILESTREAM feature at (0, 1, 2 or 3). 
    FILESTREAMLEVEL="0"
    ; Set to "1" to enable RANU for SQL Server Express. 
    ENABLERANU="False"
    ; Specifies a Windows collation or an SQL collation to use for the Database Engine. 
    SQLCOLLATION="Hebrew_CI_AS"
    ; Account for SQL Server service: Domain\User or system account. 
    SQLSVCACCOUNT="NT Service\MSSQLSERVER"
    ; Windows account(s) to provision as SQL Server system administrators. 
    SQLSYSADMINACCOUNTS="ARIELUBA-PC\Arie Luba"
    ; Provision current user as a Database Engine system administrator for %SQL_PRODUCT_SHORT_NAME% Express. 
    ADDCURRENTUSERASSQLADMIN="True"
    ; Specify 0 to disable or 1 to enable the TCP/IP protocol. 
    TCPENABLED="1"
    ; Specify 0 to disable or 1 to enable the Named Pipes protocol. 
    NPENABLED="0"
    ; Startup type for Browser Service. 
    BROWSERSVCSTARTUPTYPE="Automatic"
    ; Specifies which account the report server NT service should execute under.  When omitted or when the value is empty string, the default built-in account for the current operating system.
    ; The username part of RSSVCACCOUNT is a maximum of 20 characters long and
    ; The domain part of RSSVCACCOUNT is a maximum of 254 characters long. 
    RSSVCACCOUNT="NT Service\ReportServer"
    ; Specifies how the startup mode of the report server NT service.  When 
    ; Manual - Service startup is manual mode (default).
    ; Automatic - Service startup is automatic mode.
    ; Disabled - Service is disabled 
    RSSVCSTARTUPTYPE="Automatic"
    ; Add description of input argument FTSVCACCOUNT 
    FTSVCACCOUNT="NT Service\MSSQLFDLauncher"

  • How to create and add a logon/logoff script to populate last user into the computer field in AD

    Hi All,
    Bit stuck here,
    Not sure what forum to put this is as it involves different subjects,
    I work in a Server 2008 RT environment and have access to Active Directory etc.
    I saw this a few weeks ago - http://ivan.dretvic.com/2012/10/automatically-generate-description-field-for-computers-in-active-directory/
    Now, I'm not particularly sure what to do here, I don't know how to create a group policy etc. How to implement it in a test environment etc. Never done this before.
    Can somebody give me a step by step guide on literally everything that would be involved in this?
    Or any links that may be able to help?
    I basically want the AD to show who was the last user that logged into a specific client when the client named is searched for in the Computers OU, and if possible being able to pull the make/model and serial number from the client aswell.
    If possible there should be a way of including this with the existing login script that we already have, how can I do this?
    I've tried a few so far and got stuck, I have domain admin priveledges also.
    Thanks,
    Regards, Max.

    Hi Max,
    Please refer to the following article to learn how to create a logon/logoff script via GPO:
    Assign User Logon Scripts
    Assign User Logoff Scripts
    As for the issues about script, this is the forum to discuss questions about driectory service, better to post your question to the forum for Script:
    http://social.msdn.microsoft.com/Forums/en-US/home?forum=scripting
    The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or
    learn from your interaction with us.
    Thank you for your understanding.
    Regards,
    Lany Zhang

  • Prevention of Labor Risks IS-EHS

    Good morning. 
    We have the vertical solution for the Prevention of Labor Risks IS-EHS and according to requirements of the client, we have been ourselves forced to modify the standard provided by you, to automate a series of processes, which we have obtained after several headaches.  On the other hand, we have created descriptions to size for the preventive measures, which are going to be contained in the evaluation of labor risks, that have been created as well in standard transaction SE61 like texts of the type documentation (DOKU). 
    One of the automatizations that we have had to make, is that when an evaluation is created on a labor risk, automatically it loaded its preventive measures, in such a way that automatically the descriptions of these preventive measures are loaded, but one of those headaches before mentioned, is that when these preventive measures were loaded, when pressing on the position and showing the additional text, it showed not only the text of the first position of preventive measure but that also showed the text of the second position of preventive measure and that we have been able to separate it based on the noticeable position. 
    Another requirement of the client, is to be able to modify for that position of preventive measure in the treatment of labor risks, for a risk in particular, the descriptive text, in such a way that it is not updated for all the risks that contain this preventive measure. When trying to modify it or simply to add additional lines, in the publisher of SAPscript appears this blocked text, for that reason we cannot unblock it and therefore we cannot modify it. What we do not know is to unblock it, we have the risk of which this text is modified for all the risks that contain this preventive measure and we wanted to know how to be able to do it or what measures to take for being able to carry out it, since in that point we are blocked. 
    We have tried to create in the SAPscript for the description of that preventive measure, other formulas, but they have not been feasible. Between the used or taken measures we emphasized the following ones: 
    - To make include of text, but at no moment shows that include to us of text when displaying it, printing it to treat it in later modifications. 
    - To include clipboard of user for the text of the preventive measure, but when making it, they do not appear either unless we show them by menu and to make matters worse, that file of user is not unique for the treated preventive measure, but that appears for all the preventive measures and all the created risks and to create, due to we are limited five clipboards of user for all the application, unless there is a method to be able to separate them by evaluation or labor risk or preventive measure and that they always appear with the introduced text.
    - To create other texts standard of another type (TEXT), but that doesn´t leave possibility any to the user to be able to modify it, reason due to we return again to the same position where we were and would be necessary to use include to be able to introduce it in the text loaded for the preventive measure.
    - We don´t know if the object of authorization C_EHSI_DOC for the profiles of user authorization, will help in something, but in the existing documentation in the SPRO it indicates that single it is possible to assign these objects to the area of work and in the log of Accidents  
    Best regards.
    Guillermo P. Richter

    Hello Geuillermo,
    I am not the expert for solving your particular issues, but my employer Technidata AG is developing the EH&S solution as development partner of SAP. So if you need professional advice (consulting) or custom developments, this is the best shot.
    I hope this does not come across as advertising.
    Best regards,
    Frank.

  • Adobe from dropdown using internal table

    Hi Experts,
                 I am new to adobe forms. I have a dropdown in table. The table has two rows & four colums. Each row contains one dropdown.I have mapped the internal table for dropdown using dynamic properties.
    Say for example,
    The dropdown internal table has three fields such as Material,Material description & Material group.
    col1    Material -dd   
    col2
    col3   Material group-text field   
    col4   bla
    My requiement is when choose material it automatically fills Material group.I don't know how to do?
    Can you please tell me?
    Note: Material group is text field.
    Thanks.
    Mathi

    Hi Mathi,
    could you tell me, How did you resolv this Task.
    I have an internal table with tow field value and decription.
    My requiement is when i choose the value field it automatically fills description.
    May be could you send me your coding.
    Thank you in advance.
    mishak

  • Need help! Printer printing garbage characters and non stop until out of paper

    Hi,
    I have a computer lab that has 25 workstations. The workstations are installed with Adobe CS5 suite. Sometimes when trying to print Indesign files, the printer started to go haywire. It will print out garbage character and printing non stop until ran out of paper.
    Any help will be great. Thanks in advance.
    Network printer: HP colorjet CP4525
    OS: Win XP SP3
    Software: Indesign CS5

    There is no such thing as a Generic Adobe PostScript driver. What is posted on the adobe.com website is a driver installer that simply associates PPD files with the standards Windows PostScript driver that comes with Windows itself. That installer only works with versions of Windows up to and an including Windows XP 32-bit. It does not work with Windows Vista, Windows 7, Windows Server, or any 64-bit version of Windows.
    Also note that although the HP CP4525 “supports PostScript” it is not a printer with Adobe PostScript 3, but rather, CloneScript from a third party.
    Having said that and understanding that you are currently using a PCL6 driver, I would recommend the following:
    (1)     Try using the PCL5C driver for the printer. PCL6 and its drivers was always dodgy anyway.
    (2)     Turn off the printer's automatic page description language sensing. That feature attempts to guess as to whether PCL or PostScript is currently being sent to the device and switch language processors. It really isn't necessary because HP's drivers prepend the print job with information as to which page description language is being used.
    Given the unreliable nature of HP's emulation of PostScript, I would not recommend using any HP LaserJet's PostScript mode for any model of LaserJet in recent memory.
              - Dov

  • Auto-filling proceeding fields from user's initial input - Possible? How?

    Hi there,
    I'm quite new to LiveCycle (and scripting). That being said, I'm trying to create some automation in forms for work.
    I've been asked to create a product order form in which the Order Administrator would choose the product from a list of Product Codes. Once s/he chooses the Product Code [numeric field] from this list, the Product Description [text field] appears right next to it, and then the Product Price [numeric field] would populate the last field. I will duplicate this over multiple rows into a table, then autosum the last column which should be filled with various product prices, taxes, S&H, etc. (autosumming the Price field is easy enough - this is not my issue so let's just focus on the major concern of auto-filling descriptions and prices for now...)
    For e.g.
    Product Code
    Description
    Price
    6759-85746-098 [Order Admin chooses from list]
    Large textbook (x1) [Automatically inputs based on Product Code]
    $30.00 [Auto-inputs from Product Code]
    5864-98723-124  
    Black pens (x10/set)
    $5.25
    I've tried for days to figure out how to script this, going through numerous forums, printing off reams of Adobe help documents, trying to learn Java and/or FormCalc in solitude, and yet I still can't figure this out. To explain, I'm not a coder/developer but a print-focused graphic designer.
    If anyone knows how I can solve this I'd be very grateful. I'm now wondering if a) I need to somehow connect (bind?) the information in an external database or sheet (Excel?), b) figure out some elaborate script that would automate these descriptions and prices, and/or c) bang my head against the wall in fruitless frustration.
    Thanks for any help anyone can offer.

    A simple example.  May not meet your needs depending on the number of products.
    Droplist named ProductCode
    Text Fields named Description and Price
    Java Script the droplist on the change event
    if (xfa.event.newText=="5864-98723-124")
    {Description.rawValue="Black Pens"
    Price.rawValue="$5.25"

Maybe you are looking for