Classifications

• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
  • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
  • G06F16/24—Querying
  • G06F16/248—Presentation of query results
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F17/00—Digital computing or data processing equipment or methods, specially adapted for specific functions
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
  • G06F3/14—Digital output to display device ; Cooperation and interconnection of the display device with other functional units

Definitions

• a database is an organized collection of data.
• a database management system (DBMS) is a computer program (or more typically, a suite of them) designed to manage a database and run operations on the data requested by numerous clients.
• a DBMS allows queries to be written and executed to retrieve the data.
• a DBMS may also allow creation of forms or reports. More refined queries may also be executed from the DBMS.
• These customized queries/reports/forms may require that certain parameters be provided before a query/report/form is exec ⁇ ted against the database. Such customized queries/reports/forms typically involve several complicated steps and the result is typically difficult to understand or modify.
• a customizable user interface for entering requested parameters related to a database query.
• the customized parameter user interface provides parameter entry dialogs/windows in correlation to a data view (e.g., form or report) that is produced according to a database query.
• the parameters entered may provide for modification of the data view.
• the manager of the database may structure data views of a database to automatically include prompts for parameters before results are returned by the database. These prompts may be customized by the manager and may be provided according to dialogs such as pop-ups, pull-down menus, fly-outs, or a variety of other user interface components. Accordingly, an intuitive, efficient and modifiable data view is provided.
• FIGURE 1 illustrates an exemplary computing architecture for a computer
• FIGURE 2 illustrates a functional block diagram of an exemplary system for providing a customized parameter user interface within a database management system
• FIGURE 3 is an operational flow diagram of a process for providing a customized parameter entry form in association with a database query
• FIGURE 4 illustrates an operational flow diagram for adding a parameter to a customized parameter form
• FIGURE 5 illustrates an exemplary report before being modified by entry of an additional parameter to the query that generated the form
• FIGURE 6 illustrates the exemplary report of FIGURE 5 with a selection being made to filter the query results corresponding to the report
• FIGURE 7 illustrates an exemplary parameter generation form
• FIGURE 8 illustrates an exemplary parameter entry form that has not been customized
• FIGURE 9 illustrates an exemplary customized parameter entry form
• FIGURE 10 illustrates the report of FIGURES 5 and 6 with the results modified according the entered parameters.
• Embodiments are herein described more fully below with reference to the accompanying drawings, which form a part hereof, and which show specific examples for practicing the embodiments.
• embodiments may be implemented in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the subject matter to those skilled in the art.
• Embodiments disclosed may be practiced as methods, systems or devices. Accordingly, embodiments disclosed may take the form of an entirely hardware implementation, an entirely software implementation or an implementation combining software and hardware aspects. The following detailed description is, therefore, not to be taken in a limiting sense.
• program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types.
• Other computer system configurations may also be used, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like.
• Distributed computing environments may also be used where tasks are performed by remote processing devices that are linked through a communications network.
• program modules may be located in both local and remote memory storage devices.
• computing device 100 includes a central processing unit 102 ("CPU"), a system memory 104, including a random access memory 106 (“RAM”) and a read-only memory (“ROM”) 108, and a system bus 116 that couples the memory to the CPU 102.
• CPU central processing unit
• RAM random access memory
• ROM read-only memory
• system bus 116 that couples the memory to the CPU 102.
• the computing device 100 further includes a mass storage device 120 for storing an operating system 122, application programs, and other program modules, which will be described in greater detail below.
• the mass storage device 120 and its associated computer-readable media provide volatile and non- volatile storage for the computing device 100.
• the computer readable media may include any type of removable and/or non-removable media.
• the computing device 100 operates in a networked environment using logical connections to remote computers through a network 112, such as the Internet.
• the computing device 100 may connect to the network 112 through a network interface unit 110 connected to the bus 116.
• the computing device 100 may also include an input/output controller 114 for receiving and processing input from a number of devices, such as: a keyboard, mouse, electronic stylus and the like. Similarly, the input/output controller 114 may provide output to a display screen, a printer, or some other type of device (not shown).
• a number of program modules and data files may be stored in the mass storage device 120 and RAM 106 of the computing device 100, including an operating system 122 suitable for controlling the operation of a networked computer.
• the mass storage device 120 and RAM 106 may also store one or more program modules.
• the mass storage device 120 and the RAM 106 may store a local component of a Database Management System (DBMS) 124.
• DBMS Database Management System
• the local component of the DBMS 124 includes functionality for presenting a customized parameter user interface for entering parameters in relation to a database search query.
• the customized parameter user interface provides parameter entry dialogs/windows in correlation to a data view (e.g., form or report) that is produced according to a database query.
• the parameters entered may allow for modification of the data view.
• the modification may occur without altering the original query statement.
• the modification may also occur by directly modifying the query statement.
• the persistence of the modification may be associated with the record source, a query object, and/or a parameter property.
• the manager of the database may structure data views of a database to automatically include prompts for parameters before results are returned by the database. These prompts may be customized by the manager and may be provided according to dialogs such as pop-ups, pull-down menus, fly-outs, or a variety of other user interface components. Accordingly, an intuitive, efficient and modifiable data view is provided.
• Control generally refers to a child display frame an application uses in conjunction with another display frame to perform simple input and output (I/O) tasks. Controls are most often used within dialog boxes, but may also be used in other display frames. Controls within dialog boxes provide the user with the means to type text, choose options, and direct a dialog box to complete its action. Controls in other display frames provide a variety of services, such as letting the user choose commands, view status, and view and edit text. One example of a control is a right-click selection menu that presents a child display frame of an application's user interface.
• Data view generally refers to a form, report and/or table that represents a collection of data from a database.
• the collection of data from the database may be provided in the form or report according to a database search query.
• the data view may be modified by the entry of any parameters according to the customized parameter user interface.
• Parameter generally refers to any data value or set of data values associated with the data included in a data view. Entered parameters may modify a particular data view when entered according to the customized parameter user interface.
• Parameter entry prompt generally refers to a user interface dialog that is provided for entry of a parameter in association with a data view.
• the user interface dialog may take the form of a display frame, pop-up, pull-down menu, fly-out, or a variety of other user interface components. Entry of the parameter in the parameter entry prompt may be provided as a text box entry, a pull-down selection box, or other types of data entry user interface components.
• Parameter filter property generally refers to a property that corresponds to an entered parameter associated with a data view.
• the parameter filter property is added to the query statement according to a Boolean AND operation to modify the results included in the data view.
• Parameter form property generally refers to a property that when activated indicates that a customized parameter form is associated with a particular data view.
• Record source generally refers to a stored property corresponding to the query statement that represents the data view.
• the parameter may be added according to a Boolean AND operation to the record source.
• Query statement corresponds to the statement used for a query to the database that produces the data view.
• SQL structured query language
• the query statement corresponds to the SQL statement passed to the database engine for retrieving the database results corresponding to the data view.
• FIGURE 2 illustrates a functional block diagram of an exemplary system for providing a customized parameter user interface within a database management system (DBMS), in accordance with the present disclosure.
• DBMS interface 124 includes data view browser 202, parameter prompt module 204, customized parameter UI module 206, and property manager 208.
• Data view browser 202 further includes statement generator 210 and is coupled to database engine 230.
• Database engine 230 is coupled to database 240.
• Property manager 208 is coupled to storage 212.
• Storage 212 includes entries for a record source 214, a parameter filter property 216, and a parameter form property 220.
• data view browser 202 communicates between database engine 230 and the other functional blocks of DBMS 124 to provide a data view (e.g., a form or report, see FIGURE 5) of data contained within database 240.
• Statement generator 210 included in data view browser 202, generates query statement 232 that is passed to database engine 230. If query statement 232 is executable in its present form, database engine 230 returns query results 236 to data view browser 202. If instead, query statement 232 is not executable because it requires identification of an additional parameter not included in query statement 232, then database engine 230 returns any necessary parameter requests to data view browser 202.
• Data view browser 202 communicates any parameter requests 234 to parameter prompt module 204.
• Parameter prompt module 204 consults with property manager 208 to determine if a customized parameter form is associated with current data view.
• Property manager 208 accesses a list of properties (e.g., 214-220) in storage 212 to make the determination.
• Storage 212 may be a temporary or permanent storage and may correspond to system memory 104 or mass storage device 120 shown in FIGURE 1.
• the properties (e.g., 214-220) in mass storage device indicate that a customized parameter form is associated with the data view, functionality provided by customized parameter UI module 206 is used to display the customized parameter form in association with the data view. If however, the properties (e.g., 214-220) indicate that no customized parameter form is associated with the data view, a general parameter form is provided by parameter prompt module 204 to solicit entry of the requested parameter from the user.
• the functional blocks described in FIGURE 2 are not an exhaustive representation of the functional blocks possibly associated with a DBMS. Additional or fewer functional blocks may be included and the DBMS still operates for its intended purpose. For example, in an alternative embodiment, it may be that customized parameter UI module 206 communicates directly with data view browser 202 rather than communicating through parameter prompt module 204. In another alternative embodiment, a decision may be made by a database manager that every form or report to be produced for a particular database requires a customized parameter form. In this embodiment, parameter prompt module 204 and certain of the properties (e.g., 214-220) of storage 212 may be unnecessary since each data view will have an associated customized parameter form.
• FIGURE 3 is an operational flow diagram of a process for providing customized parameter entry form in association with a database query, in accordance with the present disclosure. Processing starts when a query has been generated for a database that does not include all the parameters necessary for execution of the query such that parameters are required to be entered. Processing continues with operation 302. [0039] At operation 302, an object/view is being opened (e.g., a form or report) that returns the response to the query in a readily understandable format. While the report is being opened, processing continues with decision operation 304. [0040] At decision operation 304, a determination is made whether a PFilter property is specified for the query.
• an object/view e.g., a form or report
• the PFilter property indicates a WHERE clause in the query, such that an additional filtering of the query is being requested. If no PFilter property is being specified, processing advances to operation 308. However, if a PFilter property is specified, processing continues to operation 306.
• a PFilter clause corresponding to the specificed PFilter property is added to the query statement. For example, if the PFilter property is one that indicates an alphabet limitation of results beginning with the letter "A”, and the original query was for current customers, then a clause is added such that the resulting query is for customers that start with the letter "A”. Processing continues at operation 308. [0042] At operation 308, the query statement is executed. While the query statement is executed, processing continues with decision operation 310. [0043] At decision operation 310, a determination is made whether execution of the query statement requires a parameter for completion. If no parameter is required, then processing advances to operation 322. However, if a parameter is required to be entered, then processing moves to decision operation 312.
• a parameter form is specified when indicated by a PForm property. If no form is specified, processing moves to operation 314.
• a prompt is provided for entering the parameter that does not include the customizations available in a parameter form generated according to the present disclosure. Once the prompt is displayed, processing continues with decision operation 316.
• processing continues with operation 318.
• the specified form is displayed for entry of the parameter.
• processing continues with decision operation 316.
• the query can be canceled at any time at the user's selection.
• processing moves to operation 318.
• operation 318 the opening of the object/view of the data is canceled, and processing ends.
• the execution of the statement, modified with the entries of the parameters, is executed.
• the modification may occur without altering the original query statement.
• the modification may also occur by directly modifying the query statement.
• the persistence of the modification may be associated with the record source, a query object, and/or a parameter property. Processing continues at operation 322.
• the results of the query are bound to the object/view and the results are shown as modified by the entered parameters. Once the object/view is displayed, process 300 ends, and processing move on to other tasks.
• FIGURE 4 illustrates an operational flow diagram for adding a parameter to a customized parameter form, in accordance with the present disclosure. Processing starts where a developer desires to add a parameter to a customized parameter form. Processing continues with operation 402. [0051] At operation 402, a command is received to add a parameter to a customized parameter form. The command may come from a pull down menu selection or other edit selection by the developer of the customized form. Processing continues with decision operation 404.
• PFilter property If the PFilter property was already populated with the parameter or once the PFilter property is populated with the parameter, processing moves to decision operation 408.
• processing continues to operation 416.
• the object/view of the data with the added parameter may be displayed after execution of the query statement. Once the object/view is displayed, process 400 ends, and processing moves to other tasks.
• FIGURE 5 illustrates an exemplary report before being modified by entry of an additional parameter to the query that generated the form, in accordance with the present disclosure.
• Report 500 includes a listing of sales by year for a product, the product numbers, when the products shipped and the sales amounts.
• FIGURE 6 illustrates the exemplary report of FIGURE 5 with a selection being made to filter the query results corresponding to the report, in accordance with the present disclosure.
• the selection being made in report 600 is to filter the results according to date filters that indicate to limit the result to those occurring between two dates specified.
• FIGURE 7 illustrates an exemplary parameter generation form, in accordance with the present disclosure.
• Parameter generation form 700 allows the developer of the parameter form to select to customize the parameter prompts for entry of the parameters. Selecting to create the parameters places the prompt in an edit mode for designing the prompts and control for the parameters.
• FIGURE 8 illustrates an exemplary parameter entry form that has not been customized according to the present disclosure.
• Parameter entry form 800 has no specified information for the report to which the prompt is associated.
• FIGURE 9 illustrates an exemplary customized parameter entry form, in accordance with the present disclosure.
• Customized parameter entry form 900 shows marked difference from the parameter entry form of FIGURE 8.
• Customized parameter entry form 900 includes information that illustrates its related to the form for which it has been generated.
• the prompt for the form instead of merely describing a start and end date, illustrates an "oldest ship date" and "newest ship date".
• the title of the form has also changed.
• the customized parameter entry form 900 may include additional logic for populating a drop down display frame with distinct values. As an example, depending on authoring needs, default values may be obtained from a database setting or calculated for a particular year.
• the customizations of the form allow for more seamless user experience when entering parameters for search queries of a database.
• FIGURE 10 illustrates the report of FIGURES 5 and 6 with the results modified according the entered parameters, in accordance with the present disclosure.
• Report 1000 illustrates a display frame having ship dates for the query results as modified by ship dates entered into a customized parameter form.

Landscapes

• Engineering & Computer Science (AREA)
• Theoretical Computer Science (AREA)
• Physics & Mathematics (AREA)
• General Engineering & Computer Science (AREA)
• General Physics & Mathematics (AREA)
• Data Mining & Analysis (AREA)
• Databases & Information Systems (AREA)
• Computational Linguistics (AREA)
• Mathematical Physics (AREA)
• Software Systems (AREA)
• Human Computer Interaction (AREA)
• Stored Programmes (AREA)
• User Interface Of Digital Computer (AREA)
• Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
• Digital Computer Display Output (AREA)
• Input From Keyboards Or The Like (AREA)

Priority Applications (11)

Applications Claiming Priority (2)

Publications (2)

Family

ID=38846257

Family Applications (1)

Country Status (15)

Families Citing this family (22)

Family Cites Families (25)

• 2006
  • 2006-06-26 US US11/475,401 patent/US8396848B2/en not_active Expired - Fee Related
• 2007
  • 2007-06-25 CN CN2007800238728A patent/CN101484874B/zh not_active Expired - Fee Related
  • 2007-06-25 WO PCT/US2007/014793 patent/WO2008002552A2/en not_active Ceased
  • 2007-06-25 CA CA2651894A patent/CA2651894C/en not_active Expired - Fee Related
  • 2007-06-25 MY MYPI20084801 patent/MY150911A/en unknown
  • 2007-06-25 EP EP07796453A patent/EP2035913A4/en not_active Ceased
  • 2007-06-25 MX MX2008015237A patent/MX2008015237A/es active IP Right Grant
  • 2007-06-25 AU AU2007265527A patent/AU2007265527B2/en not_active Ceased
  • 2007-06-25 JP JP2009518216A patent/JP5211046B2/ja not_active Expired - Fee Related
  • 2007-06-25 RU RU2008151786/08A patent/RU2447483C2/ru active
  • 2007-06-25 BR BRPI0712604-2A patent/BRPI0712604A2/pt not_active Application Discontinuation
  • 2007-06-25 KR KR1020087031481A patent/KR101322975B1/ko not_active Expired - Fee Related
• 2008
  • 2008-10-28 IL IL194963A patent/IL194963A/en active IP Right Grant
  • 2008-10-30 ZA ZA2008/09319A patent/ZA200809319B/en unknown
  • 2008-11-26 NO NO20084962A patent/NO20084962L/no not_active Application Discontinuation

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events