WO2006080913A1 - Systemes et procedes de generation de rapports - Google Patents

Systemes et procedes de generation de rapports Download PDF

Info

Publication number
WO2006080913A1
WO2006080913A1 PCT/US2005/002386 US2005002386W WO2006080913A1 WO 2006080913 A1 WO2006080913 A1 WO 2006080913A1 US 2005002386 W US2005002386 W US 2005002386W WO 2006080913 A1 WO2006080913 A1 WO 2006080913A1
Authority
WO
WIPO (PCT)
Prior art keywords
report
program code
data
generating program
pic
Prior art date
Application number
PCT/US2005/002386
Other languages
English (en)
Inventor
Sanjay Kumar Pandey
Original Assignee
Efunds Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Efunds Corporation filed Critical Efunds Corporation
Priority to PCT/US2005/002386 priority Critical patent/WO2006080913A1/fr
Publication of WO2006080913A1 publication Critical patent/WO2006080913A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/30—Creation or generation of source code
    • G06F8/34—Graphical or visual programming

Definitions

  • the present invention relates to methods and systems for automatically generating a report based on user input.
  • embodiments of the invention relate to generating program code (i.e., "instructions") that when executed generate a report based on data and formats provided by a user.
  • Some embodiments of the invention therefore provide a method of producing report- generating program code.
  • the method can include obtaining an indication as to a source of data to be included in a report generated by the execution of the report-generating program code; retrieving data from the source; obtaining formatting instructions for the data to be included in Attorney Docket No: 025213-9117
  • Another embodiment provides a system for producing report-generating program code.
  • the system can include interfacing means for obtaining an indication as to a source of data to be included in the report-generating program code and for obtaining formatting instructions for the data to be included in the report-generating program code.
  • the system can include retrieving means for retrieving the data from the source and producing means for producing the report-generating program code.
  • Additional embodiments provide a computer readable medium containing instructions for producing report-generating program code.
  • the instructions can include obtaining an indication as to a source of data to be included in the report-generating program code; retrieving data from the source; obtaining formatting instructions for the data to be included in the report- generating program code; and producing the report-generating program code based on the data and the formatting instructions.
  • FIG. 1 is a schematic illustration of a report generating system according to one embodiment of the invention.
  • FIG. 2 is a flow chart illustrating a method of producing report-generating program code according to one embodiment of the invention.
  • FIGS. 3-27 illustrate screen shots related to the steps of the method of FIG. 2.
  • embodiments of the invention include both hardware and electronic components or modules that, for purposes of discussion, may be illustrated and described as if the majority of the components were implemented solely in hardware.
  • the electronic based aspects of the invention may be implemented in software.
  • a plurality of hardware and software based devices, as well as a plurality of different structural components may be utilized to implement the invention.
  • the specific configurations illustrated in the drawings are intended to exemplify embodiments of the invention and that other alternative configurations are possible.
  • FIG. 1 is a schematic illustration of a report generating system 10 according to one embodiment of the invention.
  • the system 10 can include a report generator tool (hereinafter “tool") 20, a tool access point 30 (e.g., a workstation or a terminal), a report data storage medium (hereinafter “input medium”) 40, and a report-generating program code storage medium (hereinafter “output medium”) 50.
  • the tool 20 can be connected to the tool access point 30 by a connection 60.
  • the tool 20 can also be connected to the input medium 40 and the output medium 50 by connections 70 and 80, respectively. It should be understood that the connections 60, 70, and 80 can include wired and/or wireless connections.
  • connections 60, 70, and 80 can be part of a network, such as a local area network or the Internet. It should also be understood that, although shown as separate components, the tool access point 30 can be combined with tool 20. The tool access point 30 can also be combined with the input medium 40 and/or the output medium 50. The input medium 40 and the output medium 50 can also be Attorney Docket No: 025213-9117 WO
  • the input medium 40 and the output medium 50 can also each include multiple discrete storage mediums.
  • a user can use the tool access point 30 to request the production of report-generating program code from the tool 20.
  • the tool access point 30 (and any input devices included in the tool access point 30) obtains data source indications and formatting instructions from the user.
  • the tool access point 30 can display visual forms or prompts for requesting and obtaining data source indications and formatting instructions from the user. Visual screens that can be displayed by the tool access point 30 are illustrated in FIGS. 3-28 and described below.
  • the tool access point 30 can transmit the data source indications and the formatting instructions to the tool 20 via the connection 60.
  • the tool 20 can produce report-generating program code based on the data source indications and the formatting instructions.
  • the report- generating program code when executed, can generate a report including the data indicated by the data source.
  • the data included in the report can also be formatted based on the formatting instructions.
  • the tool 20 can also obtain the data indicated by the data source.
  • the tool 20 can access the input medium 40 to obtain the data.
  • the input medium 40 includes a database or a file.
  • the input medium 40 can also include a control card previously generated by the tool 20.
  • the control card can include the data.
  • the control card can also include formatting instructions, in some embodiments.
  • the formatting instructions can include instructions for configuring a report length. For example, the tool 20 can generate a report with up to approximately 9999 bytes.
  • the formatting instructions can also include instructions for configuring lines per page of the report. In some embodiments, 59 lines per page are generated by default if no specific lines per page formatting instructions are obtained.
  • the formatting instructions can include instructions specifying control breaks. For example, the tool 20 can provide 9 levels of control breaks.
  • the formatting instructions can include instructions for performing internal sorting. In some embodiments, the tool 20 can sort up to a maximum of approximately 9 keys.
  • instructions can include instructions for specifying the summation of field for control total, page total, and end of report total.
  • the formatting instructions can also include instructions for suppressing duplicate details fields and/or suppressing a summary at control.
  • the formatting instructions can include customization instructions.
  • the customization instructions can specify customized page heads with variables and text, customized control headings with variables and text, customized control footers, and customized end-of-the-report headers with variables and text.
  • the tool 20 can provide system fields that are associated with variables included in customizations.
  • the tool 20 can include system date and time fields that can be associated with variables included in customizations.
  • the tool 20 can include a restructured, extended executor configured to write an optimized, formatted and engineered program that, when executed, generates a report.
  • the tool 20 generates common business-orientated language ("COBOL") program code.
  • COBOL common business-orientated language
  • the tool 20 can provide the additional functionality of compiling and executing of the generated program code.
  • the tool 20 can also provide field level help and tutorials.
  • the tool 20 can also provide an on-line tool execution monitor.
  • the tool 20 can transmit the program code to the output medium 50.
  • the tool 20 can transmit the program code to the output medium 50 via the connection 80.
  • the user can retrieve the stored program code from the output medium 50 and can modify the program code.
  • the tool 20 can be configured to compile the program code to generate executable report-generating program code.
  • the tool 20 can be configured to store the executable report- generating program code in the output medium 50.
  • the tool 20 can also execute the executable report-generating program code and can store a generated report in the output medium 50.
  • FIG. 3 illustrates a "MAIN MENU" screen 105 according to one embodiment of the invention.
  • the tool 20 can include one or more tools Attorney Docket No: 025213-9117 WO
  • selecting the 'TOOL F option can provide a first tool that produces program code that generates reports of length up to approximately 132 pages.
  • Selecting 'TOOL IF option can provide a second tool that produces program code that generates more complex or lengthy reports.
  • the first tool can generate default program code to generate default reports and the second tool can generate customized program code.
  • the user can specify the report length and the number of lines per page. The user can also select the 'Tutorials' option to receive help with operating the tool 20.
  • the user can select (at 110) an indication of a source or type of data.
  • the data will be included in the report generated by executing the program code produced by the tool 20.
  • the tool access point 30 displays an input type specification menu that allows the user to select an indication of the source or type of data to be input to the program code.
  • FIG. 4 illustrates an "Input Type Specification Menu" screen 115 according to one embodiment of the invention.
  • the type of data can include a file, such as a virtual storage access method (“VSAM”) file or a queued sequential access method (“QSAM”) file.
  • the type of data can also include a query that, when executed, retrieves data from a database.
  • the type of data can also include a control card generated by the tool 20.
  • FIG. 5 illustrates a "Query Panel” screen 125 according to one embodiment of the invention.
  • the user can also enter a database table declaration generator.
  • the input medium 40 includes a database management system, such as DB2, and the user can input a description generator ("DCLGEN") of the specified SQL query that generates DB2 SQL data structures in COBOL programs.
  • DCLGEN description generator
  • the host variables must be selected serially (numeric) depending on the SQL query column sequence.
  • the user can also enter the dataset name (“DSN”) system name.
  • the tool 20 can execute the query to retrieve data from a database.
  • the tool 20 can transmit the results of executing the Attorney Docket No: 025213-9117 WO
  • FIG. 6 illustrates a "QUERY RESULT" screen 135 according to one embodiment of the invention.
  • the user can review the query results and can determine if the results include the intended report data.
  • FIG. 7 illustrates a "Host Variable and Other Specifications" screen 145 according to one embodiment of the invention.
  • the user can enter the DSN and member name where the previously-entered DCLGEN is stored.
  • the user can enter a program name and a source code DSN.
  • the program name will be assigned to the program code produced by the tool 20.
  • the source code DSN specifies the library name where source code is to be stored.
  • a user identification may be prefixed to the DSN to distinguish one user's code from another.
  • the user can specify whether he or she wants to add a record number. Entering a "Y" can add a sequence number in each detail record of the report. In some embodiments, size bytes are reserved for sequence number and only remaining bytes are available for details columns.
  • the user can specify whether the tool 20 should optimize the column headings and details. In some embodiments, the tool 20 can optimize the headings by automatically positioning the start and end positions of the column headings and detail. Entering 'N' for this option can allow the user to specify the start position and length of the column headings and details.
  • the user can specify whether the report should include a summary at the end of each page.
  • a separate screen or prompt is displayed to allow the user to write text and variables for the summary.
  • the user can also specify whether he or she wants to format an end-of-report summary.
  • a separate screen or prompt can be displayed for the user to specify text and variables to appear in the end-of-report summary.
  • the user can specify whether he or she wants to compile the source code or if he or she wants to compile the source code and run the related execution. If the user enters "Y" for the "Do You Want to Compile only” option or the "Do You Want to Compile & Run” option, as Attorney Docket No: 025213-9117 WO
  • FIG. 7 illustrates a "Compile and Run Specifications" screen 155 according to one embodiment of the invention.
  • the compilation related inputs can include a load library specification.
  • the user can specify the load library name where the load module is to be stored.
  • the compilation related input can include a database request module ("DBRM") library name where the DBRM is to be stored.
  • DBRM database request module
  • a user identification can be prefixed before the name.
  • the compilation related inputs can also include a plan name, hi some embodiments, if the plan name is blank, the program name will be assumed the same as the plan name.
  • the "Compile and Run Specifications" screen 155 can also obtain execution related inputs.
  • a separate screen can also be provided to obtain execution related inputs if the user enters "Y" for the "Do You Want to Compile & Run” option shown in FIG. 7.
  • FIG. 9 illustrates a "Field Selection Panel" screen 165 according to one embodiment of the invention.
  • the sequence numbers associated with each data field can be assigned based on the order that the data fields where selected by the query.
  • the user can use the screen 165 to make sure that the field order is the same as defined in the query. For not "NOT NULL" columns, the user can enter an "I” in an indicator field ("IND") with the same sequence number as the original data field.
  • IND indicator field
  • FIGS. 10- 13 illustrate a "Report Specifications" screen 175 according to one embodiment of the invention.
  • the report specifications can include a sequence number (“SN") that specifies the sequence number in which columns are to be displayed in the report.
  • the tool 20 can provide heading formatting options.
  • the user can specify standard text and variables in a heading.
  • the user can Attorney Docket No: 025213-9117 WO
  • the tool 20 can provide current date and time variables that the user can use in headings.
  • the user can enter one or more column headings for each data field. As shown in FIGS. 10-13, the user can specify a first, second, and third column heading. In some embodiments, if the first column heading is blank and the data field is selected to be included in the report, then a variable name will be inserted in the column heading.
  • the user can specify a sort key sequence number for each data filed.
  • the user can also specify a sort order of the key.
  • the sort order can be set to "A" ascending or "D" descending. In some embodiments, sort order is set to ascending by default.
  • the user can specify page break definitions for control breaks.
  • the user can set a page break with a new serial number and a new page number, a page break with a new page number only, a page break with no renumbering of page number or serial number, or no page break (only a control break).
  • the user can also specify a control order that specifies the control order in which fields are to be controlled. In some embodiments, the control order is a numeric number.
  • Control break heading entry space is also provided on the screen 175. The user can write text in the space.
  • the tool 20 can attach the data field name to the text in source code.
  • the user can specify the suppression of duplicate values in the report and the suppression of a summary on a control break when the report is printed.
  • the user can specify whether he or she wants a page break sum ("PBS") and/or a control break sum (“CBS”) printed on the report.
  • PBS page break sum
  • CBS control break sum
  • the user can enter a 'Y' to have an end of report sum (“ERS”) printed at the end of the report.
  • the tool will only generate sums when the data field is a numeric type data field.
  • the user can specify an edited picture clause to be displayed in the report.
  • the edited picture clause is in a COBOL format. In some embodiments, if an Attorney Docket No: 025213-9117 WO
  • the tool 20 assumes the field picture clause as specified in the file layout.
  • FIG. 14 illustrates another "Report Specifications" screen 185 that allows the user to specify the start position and the length of a column heading and details.
  • the tool 20 determines the length of the specified column heading and details, and places the value in the length field. In some embodiments, the tool 20 prohibits overlapping between column headings and/or details.
  • FIG. 15 illustrates a "Heading Layout Specifications" screen 195 according to one embodiment of the invention.
  • the user can mix text and variables.
  • all text (including spaces) start with a "+” sign and all variables start with a "&" sign.
  • All text and variables can end with a "+” sign or a "&” sign.
  • Each heading line can end with a "+” sign.
  • Variables in the heading can also be numbered.
  • the tool 20 can display a preview screen.
  • FIG. 16 illustrates a preview screen 205 according to one embodiment of the invention.
  • the user can view the preview screen 205 and can make adjustments to the text and variables included in the heading.
  • the preview screen 205 displays the heading as it will look in the actual report when generated.
  • FIG. 17 illustrates a "Header Field Selection Panel" screen 215 according to one embodiment of the invention.
  • the user can enter a variable number to relate with a specified variable.
  • the user can also enter a display picture clause for each variable.
  • the tool 20 assigns the display picture clause of the data field as defined in the file layout.
  • the user can also specify an end-of-report layout.
  • FIG. 18 illustrates a "End of Report Layout" screen 235 according to one embodiment of the invention.
  • the user can specify an end-of- report layout that includes text and variables.
  • the layout follows the same rules as specified above for distinguishing text from variables.
  • the tool 20 can generate a preview of the end of the report as specified in the layout.
  • FIG. 19 illustrates a "End of Report Summary Preview" screen 235.
  • the user can return to the "End of Report Layout" screen 225 to make changes to the layout based on the preview screen 235.
  • the user can also specify variable numbers and display picture clauses if the end-of- report layout specified by the user contains the variables, as described and illustrated above.
  • the tool 20 produces (at 240) the program code.
  • Sample program code according to one embodiment of the invention follows.
  • 502 IS LCP-P02. INPUT-OUTPUT SECTION. FILE-CONTROL .
  • EXEC SQL INCLUDE MYTEST END-EXEC .
  • EXEC SQL INCLUDE SQLCA END-EXEC .
  • INPUT PROCEDURE IS 25000-GENERATE-WORK-RCD OUTPUT PROCEDURE IS 30000 - PRODUCE-REPORT .
  • the tool 20 produces a control file in addition to the program code based on the entered values.
  • the tool 20 can store the control file in the output medium 50.
  • the program code is stored according to a program name specified by the user. If the program code is compiled and executed, the generated report can be stored in a Attorney Docket No: 025213-9117 WO
  • FIG. 20 illustrates an "Online Status" screen 245 according to one embodiment of the invention.
  • the screen 245 can display a time elapsed and a percent completed for preparing and processing the program code.
  • FIG. 22 illustrates a "Input File Layout Specification" screen 255 according to one embodiment of the invention.
  • the user can use the screen 255 to enter a DSN and member name that specifies the DSN and member where a file layout is stored.
  • the user can also enter a program name and a source code DSN.
  • the source code DSN can specify the library name where source code is to be stored. If the DSN does not have quotes, a user identification can be prefixed to the DSN name.
  • the user can also specify a file mode and VSAM file details.
  • the file mode specifies the file mode of the input file.
  • the default mode can be a fixed file mode.
  • the file mode specification can only be applicable to particular file types, such as QSAM file.
  • FIG. 23 illustrates an "Input FILE-CONTROL Specification" screen 265 according to one embodiment of the invention. The user can use the screen 265 to specify the organization, the access mode, the relative keys, and the alternate keys.
  • the user can use the screen 255 to specify whether he or she wants to add a record number. Entering a "Y" can add a sequence number in each detail record of the report. In some embodiments, size bytes are reserved for sequence number and only remaining bytes are available for details columns.
  • the user can specify whether the tool 20 should optimize the column headings and details. In some embodiments, the tool 20 can optimize the headings by automatically positioning the start and end positions of the column headings and detail. Entering "N" for this option can allow the user to specify the start position and length of the column headings and details.
  • the user can specify whether the report should include a summary at the end of each page.
  • a separate screen or prompt is displayed to allow the user to write text and variables for the summary.
  • the user can also specify whether he or she wants to format an end-of-report summary.
  • a separate screen or prompt can be displayed for the user to specify text and variables to appear in the end-of-report summary.
  • the user can specify whether he or she wants to compile the source code, or if he or she wants to compile the source code and run the related execution. If the user enters "Y" for the "Do You Want to Compile only” option or the "Do You Want to Compile & Run” option, as shown in FIG. 22, the user enters (at 150) compilation related inputs.
  • FIG. 24 illustrates a "Compile and Run Specifications" screen 275 according to one embodiment of the invention.
  • the compilation related inputs can include a load library specification. The user can specify the load library name where the load module is to be stored. In some embodiments, if the user entered 'Y' for the 'Do You Want to Compile & Run' option, the user specifies an input DSN.
  • FIG. 25 illustrates a "Field Selection Panel" screen 285 according to one embodiment of the invention. As shown in FIG. 25, to select a field, an "S" is entered next to the data field.
  • the user can specify report specifications (at 170) and a heading layout (at 180) as shown and described with respect to FIGS. 10-19.
  • the user can also specify an end-of-report layout.
  • the tool 20 then produces (at 240) the program code and stores the program code (and the compiled code and execution results). In some embodiments, the tool 20 displays the on-line monitoring screen, as shown in FIG. 20.
  • a third data type option can include a "3 CONTROL CARD AS INPUT” option.
  • the user can select the "3 CONTROL CARD AS INPUT” option from the "Input Type Specification Menu” screen 115 (as shown in FIG. 26). Selecting the "3 CONTROL CARD AS INPUT” allows the user to input the DSN of a previously-generated control card.
  • FIG. 27 illustrates a "Control Card Specifications" screen 295 according to one embodiment of the invention.
  • the user can use the screen 295 to specify the control card name.
  • the control card name is set or prepared by tool 20 when it is generated.
  • the user can also specify a control card DSN. If the DSN does not include quotes, a user identification is prefixed to the name.
  • the tool 20 After the user specifies the control card name and the control card DSN, the tool 20 produces (at 300) the program code and stores the program code (and the compiled code and execution results).
  • the tool 20 can also display the on-line monitoring screen as shown in FIG. 20.
  • the user can specify report specifications, a heading layout, and/or a report layout as shown and described with respect to FIGS. 10-20.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

La présente invention a trait à des procédés et des systèmes pour la production de code de programme de génération de rapports. Un procédé peut comprendre l'obtention d'une indication concernant une source de données à être incluse dans un rapport généré par l'exécution du code de programme de génération de rapports; la récupération de données à partir de la source; l'obtention d'instructions de formatage pour les données à inclure dans le code de programme de génération de rapports; et la production du code de programme de génération de rapports sur la base des données et des instructions de formatage.
PCT/US2005/002386 2005-01-26 2005-01-26 Systemes et procedes de generation de rapports WO2006080913A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/US2005/002386 WO2006080913A1 (fr) 2005-01-26 2005-01-26 Systemes et procedes de generation de rapports

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2005/002386 WO2006080913A1 (fr) 2005-01-26 2005-01-26 Systemes et procedes de generation de rapports

Publications (1)

Publication Number Publication Date
WO2006080913A1 true WO2006080913A1 (fr) 2006-08-03

Family

ID=36740823

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2005/002386 WO2006080913A1 (fr) 2005-01-26 2005-01-26 Systemes et procedes de generation de rapports

Country Status (1)

Country Link
WO (1) WO2006080913A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11377622B2 (en) 2018-01-19 2022-07-05 The Procter & Gamble Company Liquid detergent compositions comprising alkyl ethoxylated sulfate surfactant

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6055369A (en) * 1997-05-06 2000-04-25 Hitachi Software Engineering Co., Ltd. Apparatus for visual programming with screen flow
US6233583B1 (en) * 1998-09-10 2001-05-15 International Business Machines Corporation Report generator for use within a lotus notes database system
US6467079B1 (en) * 1999-03-30 2002-10-15 International Business Machines Corporation Report program language source code translation to object-oriented language source code which emulates report program language behavior
US6801229B1 (en) * 2001-04-06 2004-10-05 Plumbdesign System for creation of visual representation of data
US6817010B2 (en) * 2000-12-27 2004-11-09 International Business Machines Corporation Monitoring messages during execution of a message flow
US6829348B1 (en) * 1999-07-30 2004-12-07 Convergys Cmg Utah, Inc. System for customer contact information management and methods for using same
US20050149617A1 (en) * 2001-11-26 2005-07-07 Objectworld Communications Corp. Graphical interface based software for creating communication service agents
US20050273420A1 (en) * 2004-04-16 2005-12-08 Lenin Subramanian Method and system for customizable homepages for network-based auctions

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6055369A (en) * 1997-05-06 2000-04-25 Hitachi Software Engineering Co., Ltd. Apparatus for visual programming with screen flow
US6233583B1 (en) * 1998-09-10 2001-05-15 International Business Machines Corporation Report generator for use within a lotus notes database system
US6467079B1 (en) * 1999-03-30 2002-10-15 International Business Machines Corporation Report program language source code translation to object-oriented language source code which emulates report program language behavior
US6829348B1 (en) * 1999-07-30 2004-12-07 Convergys Cmg Utah, Inc. System for customer contact information management and methods for using same
US6817010B2 (en) * 2000-12-27 2004-11-09 International Business Machines Corporation Monitoring messages during execution of a message flow
US6801229B1 (en) * 2001-04-06 2004-10-05 Plumbdesign System for creation of visual representation of data
US20050149617A1 (en) * 2001-11-26 2005-07-07 Objectworld Communications Corp. Graphical interface based software for creating communication service agents
US20050273420A1 (en) * 2004-04-16 2005-12-08 Lenin Subramanian Method and system for customizable homepages for network-based auctions

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11377622B2 (en) 2018-01-19 2022-07-05 The Procter & Gamble Company Liquid detergent compositions comprising alkyl ethoxylated sulfate surfactant

Similar Documents

Publication Publication Date Title
US6434554B1 (en) Method for querying a database in which a query statement is issued to a database management system for which data types can be defined
US5634121A (en) System for identifying and linking domain information using a parsing process to identify keywords and phrases
US7725501B1 (en) System and method for rapid database application deployment and use
US6658622B1 (en) Self-diagnosing and self-correcting data entry components with dependency behavior
US5950190A (en) Dynamic, self-modifying graphical user interface for relational database applications
US6502233B1 (en) Automated help system for reference information
US6305008B1 (en) Automatic statement completion
US5732274A (en) Method for compilation using a database for target language independence
DE19900500A1 (de) Die Erzeugung einer kompatiblen Bestellung für ein Computersystem
US7523077B2 (en) Knowledge repository using configuration and document templates
US6341359B1 (en) Self-diagnosing and self correcting data entry components
US20020029377A1 (en) System and method for developing test cases using a test object library
US8555263B2 (en) System and method for code automation
US20070283325A1 (en) Quality inspector tool
US5933634A (en) Mock-up method and mock-up control system for displaying pseudo operation
US20100145985A1 (en) Document management apparatus, method, and program
US6570591B1 (en) Visual syntax builder for space vehicle control
US6907434B2 (en) Message analysis tool
US20030182287A1 (en) Interface for an electronic spreadsheet and a database management system
US6993518B2 (en) Method and system for systematically diagnosing data problems in a database
US20080281455A1 (en) Materials, Operations and Tooling Interface and Methods for Managing a Remote Production Facility
JP3606484B2 (ja) データベース装置
US7305411B2 (en) Methods, systems, and storage mediums for expanding the functionality of database applications
JPH08503568A (ja) 複数のプログラムモジュールとコンピュータの記憶装置との間にファイルまたは他のデータエンティティの転送を集積するための順次情報集積サービス
US7100126B2 (en) Electrical form design and management method, and recording medium

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
122 Ep: pct application non-entry in european phase

Ref document number: 05712027

Country of ref document: EP

Kind code of ref document: A1