JP3606484B2 - Database device - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a database apparatus for searching a relational database type database, outputting a search result, and starting another process based on the search result.
[0002]
[Prior art]
Conventional Example 1
Conventional tools that can search a relational database include, for example, BORLAND INTERNATIONAL, INC. Paradox for Windows. FIG. 66 is a diagram showing an example of a search condition designation screen in Paradox for Windows. In addition, FIG. 66 quotes the figure described in P73 of the introductory manual.
FIG. 67 is a diagram showing a search result in accordance with the search condition of FIG. 66 in Paradox for Windows. In addition, FIG. 67 quotes the figure described in P73 of the input manual.
In FIG. 66, the customer. A condition for searching for a record in which the prefecture of the DB is “Okinawa” is specified. This search screen is a screen that is displayed when the “Search item value” button in the speed bar is clicked. As shown in FIG. 66, when the search condition is specified and the [OK] button at the lower left of the screen is clicked, the customer. The first record in the DB where the prefecture is “Okinawa” is retrieved and displayed in FIG.
As described above, in Paradox for Windows, when searching for a record by item value, a screen for specifying the item value is prepared separately, and the user displays the “value search” screen. Specify the item value and the item name to be searched after performing the operation.
Further, when making an inquiry about information in a relational database in Paradox for Windows, the inquiry content is defined and the defined inquiry is executed.
FIG. 68 is a diagram showing an example of a screen for selecting a file to be inquired in Paradox for Windows.
FIG. 69 is a diagram showing an example of a screen for defining an inquiry in Paradox for Windows.
FIG. 70 is a diagram showing a result of executing the inquiry defined in FIG. 69 in Paradox for Windows.
68 quotes P162 of the introductory manual, FIG. 69 quotes P166 of the introductory manual, and FIG. 70 quotes P167 of the introductory manual.
When the user makes an inquiry, right-click the [Open inquiry] button in the speed bar on the desktop, and select [New (N)]. When the selection is made, a “file selection” dialog box as shown in FIG. 68 is displayed. For example, when the user makes an inquiry to the “order database”, on the file selection screen of FIG. 68, click “Order. DB” and click the [OK] button. When a file is selected, an inquiry definition screen shown in FIG. 69 is displayed. For example, when inquiring about a customer whose receivable amount is 0 yen or more, and the item to be displayed is "order number, customer number, order date, shipping date, transportation method, billing amount, payment amount, receivable amount" 69, check the above eight items as shown in FIG. 69, and specify the condition that the unaccrued amount is larger than 0 yen. When an inquiry specified as shown in FIG. 69 is executed, an Answer table as shown in FIG. 70 is displayed.
As described above, in Paradox for Windows, when a query for extracting a specific value for information in a relational database is performed, the specific value is also specified on the screen for query definition.
[0003]
Conventional Example 2
As a tool that can search a relational database, there is, for example, Microsoft Access of Microsoft Corporation. FIG. 71 is a diagram showing a query in which a product table and a product category table in Microsoft Access are combined using a category code. (A query is an Access object that asks a question or defines an extraction condition for data in a table.) FIG. 71 quotes a diagram described in P92 of the Access introductory manual.
FIG. 72 is a diagram showing an example of a screen for designating query extraction conditions in Microsoft Access. In addition, FIG. 72 quotes the figure described in P92 of the Access introduction manual.
If you want to search for a record whose category name is “confectionery” or “soft drink” from the query shown in FIG. 71, clicking the “Design View” button on the toolbar (not shown) will display the record in FIG. The extraction condition specification screen is displayed. Since the category name is “confectionery” or “soft drink”, the extraction condition is moved to the “extraction condition” cell for the “category name” field, “confectionery” is entered in the cell, and the enter key is pressed. Move to the bottom of the cell where “confectionery” is entered, enter “soft drink”, and press the enter key. FIG. 72 shows a screen in which the extraction condition is specified.
As described above, in Microsoft Access, an extraction condition designation frame having all items displayed in the query as fields is displayed. Therefore, by specifying an extraction condition for a field to be extracted and executing this, a search result is displayed. Can be obtained.
[0004]
Conventional Example 3
Further, as a method of searching a relational database and editing and outputting a search result, there is a “relational database search / output method” disclosed in, for example, “JP-A-4-310183”. According to the above method, only the internal management number is read and stored in the user file at the time of retrieval. The actual data reading and editing process and the form output process are executed by a program independent of the search using the user file as a medium.
FIG. 73 shows an embodiment of a relational database search / output method. In FIG. 73, the relational database search / output method is divided into a main process centered on the main program 200 and a sub process centered on the subprogram 500, and the main process and the subprocess are executed independently. In FIG. 73, 100 is a terminal screen, 300 is a relational database, 400 is a record number file, and 600 is a form.
The main program 200 receives various operation instructions such as search, display, form output, and the like as commands from the screen 100 of the terminal. When a search instruction is received, the record to be searched and the record number are output to the record number file 400, the subprogram 500 is started, and the process is terminated. This part is the main process. When the subprogram is activated, the screen 100 of the terminal can be used.
[0005]
The subprogram 500 started from the main program 200 reads the actual data from the relational database 300 using the record number stored in the record number file 400, edits it, and outputs a form 600. This part is sub-processing.
[0006]
[Problems to be solved by the invention]
Since the conventional database apparatus is configured as described above, items that are not to be searched are displayed on the screen for specifying the conditions for searching the database as shown in FIGS. For this reason, even unnecessary information is displayed, the screen is complicated, and there is a problem that it takes time to input and search necessary information. In addition, there is a separate tool for specifying search conditions as shown in FIG. 66. However, since only one item can be specified as a search target on this screen, a plurality of items are selected as search targets. The search condition must be specified on the screen of FIG. 66 by the same number as the number of items to be searched. For this reason, there has been a problem that the operation is complicated for the user.
Further, as shown in FIG. 73, the processing from database search to output is divided into main processing and sub-processing, but the sub-processing only edits the search result. For this reason, when another program is started based on the search result, there is a problem that a program having a necessary function must be coded in a system environment including a database. (FIG. 74 shows a flowchart for starting the next processing based on the conventional search result. According to FIG. 74, the user can download the programs of processing A, processing B, and processing C that are started based on the result determination. In a system environment with a database such as the one described above, there is a problem that it takes time and effort to customize the corresponding program for each user if the processing to be started differs depending on the search result for each user of the system. was there. There is also a problem that it is difficult to expand the processing repertoire.
[0007]
The present invention has been made to solve the above problems, and enables the following.
The user arbitrarily sets items to be searched among the items of the database, and creates a search condition setting screen based on the settings.
In addition, the user can arbitrarily design a result display screen for displaying the search result.
Furthermore, based on the search result, the process to be started next can be easily set interactively without the user coding a program.
[0008]
[Means for Solving the Problems]
The database apparatus according to the first aspect of the present invention has the following elements.
(A) the database stores the data;
(B) The screen design unit arbitrarily designs a search condition input screen for inputting conditions for searching the data in the database,
(C) The search unit inputs a search condition using a search condition input screen of a predetermined format designed by the screen design unit, and searches for data.
[0009]
The database device according to the second invention is characterized in that the screen design unit further arbitrarily designs a search result display screen for displaying a search result searched by the search unit.
[0010]
In the database device according to the third aspect of the invention, the screen design unit selects an arbitrary field from the fields constituting the data.
[0011]
The database device according to a fourth aspect is characterized in that the screen design unit designates the display order of the selected field.
[0012]
The database device according to a fifth aspect of the present invention is characterized in that the screen design unit sets in advance a search condition that may be used for the field selected for the search condition input screen.
[0013]
The database device according to the sixth invention is characterized in that the screen design unit designates the display format of the field selected for the search result display screen.
[0014]
The database device according to the seventh invention has the following elements.
(A) the database stores the data;
(B) The search unit searches the data in the database,
(C) The process definition unit predefines and stores an executable process based on the search result of the search unit,
(D) The process execution unit executes the process defined by the process definition unit.
[0015]
In the database device according to the eighth aspect of the invention, the process definition unit defines a plurality of processes, and the process execution unit selects and executes at least one process from the plurality of processes. Features.
[0016]
The database apparatus according to a ninth aspect is characterized in that the process definition unit includes an interactive definition support unit that defines a process using an interactive interface.
[0017]
Further, in the database device according to the tenth invention, the process definition unit stores the definition information as an action management table, and the process execution unit analyzes the definition information stored in the action management table and performs processing. A command generation unit that generates a necessary command is provided.
[0018]
The database device according to an eleventh aspect is characterized in that the command is an SQL command.
[0019]
The database apparatus according to a twelfth aspect is characterized in that the command is a system call.
[0020]
A database device according to a thirteenth aspect of the invention is a guideline definition for defining and storing data used for a guideline that is a list of candidate data to be referred to in order to set a recommended condition for a search condition input screen in the screen design unit. It has the part.
[0021]
Further, the database device according to the fourteenth invention is characterized in that the guideline definition unit defines at least one of actual data of a search target table and data of an arbitrary table as candidate data.
[0022]
The database apparatus according to the fifteenth aspect is characterized in that the guideline definition unit defines an annotation for candidate data.
[0023]
Further, the database device according to the sixteenth invention is characterized in that the guideline definition unit defines a font of display characters of data.
[0024]
The database device according to the seventeenth invention is characterized in that the guideline definition unit defines a data highlighting method.
[0025]
Further, the database device according to the eighteenth invention is characterized in that the guideline definition unit specifies a condition for further narrowing down candidate data from the defined candidate data.
[0026]
DETAILED DESCRIPTION OF THE INVENTION
Embodiment 1 FIG.
In this embodiment, search condition input screen design and search result display screen design in the screen design unit will be described below.
[0027]
First, the drawings will be described.
FIG. 1 is a system configuration diagram for realizing a database apparatus according to the present invention.
In FIG. 1, 1 is a database device, 2 is a CRT that displays a screen such as a search condition input screen or a search result display screen, and 3 is a search condition input screen design 3a for performing a condition input for searching a database. And a screen design unit including a search result display screen design 3b for designing a display format for displaying a result of searching the database based on the search condition. Reference numeral 4 denotes a search unit that searches a database based on search conditions, 5 is a mouse, 6 is a keyboard, and 7 is a database that stores a plurality of tables.
In the database used in this embodiment, the data structure is represented by using a tree, and each element of the tree is represented by using a node. The node has a hierarchical structure of a top node, an intermediate node, and an end node. The top node is a top node and the end node has no other nodes below it. The node is an intermediate node. A database table or view is associated with the end node on a one-to-one basis. When searching, it is possible to access the corresponding database table by narrowing down the type from the top node to the intermediate node and specifying the end node. Furthermore, the tree includes a shared tree and a user tree, and a tree that can be commonly used by users using the system is called a shared tree. The shared tree is created by the system administrator. On the other hand, what a user personally creates and uses is called a user tree.
[0028]
FIG. 2 is a diagram showing tree information that can be accessed by the user and stored in the database.
FIG. 3 is a diagram showing nodes stored in the tree information selected by the user from the tree information shown in FIG.
In FIG. 3, “component information” indicates a top node, “component information” includes intermediate nodes from “connector / relay / switch” to “peripheral device”, and “IC” as an intermediate node. It shows that there is a terminal node from “bipolar IC (LS · S) to“ MOS memory IC (DRAM) ”.
FIG. 4 is a diagram showing a “screen” menu.
The “screen” menu is a menu displayed when “screen” in the menu bar of FIG. 3 is clicked.
[0029]
FIG. 5 is a diagram showing a screen setting window.
In the screen setting window of FIG. 5, a search condition input screen setting 10, a search result display screen setting 11 and an action list 12 are displayed, and each screen can be moved up, down, left and right using the scroll bar 13. .
The search condition input screen setting 10 includes setting items for switching 10a, order 10b, field name 10c, and recommended condition definition 10d.
The switch 10a sets whether or not to display the field in the search condition input window. When it is selected (when the square 升 is displayed in black), the field is displayed on the search condition input screen displayed when executing the search.
The order 10b sets the order in which the field is displayed in the search condition input window. To set, click in the square frame and enter the order in numbers.
The field name 10c displays a title (hereinafter referred to as a field name) given to the field of the table to be set so as to be easily understood by the user. However, only the fields for which the user has reference rights are displayed. The table to be set is a table for which the search condition input screen is to be set. According to FIG. 5, the table name “KP11P” is the table to be set. The name displayed in the field name 10c is the field name stored in “KP11P”.
The recommended condition definition 10d sets input condition candidates (recommended conditions) to be displayed in a drop-down list when a search condition is input. A plurality of candidates can be designated, and input is performed by separating them with “,” or “_”.
Moreover, the guideline set to the field can be used in the input of recommended conditions. When a field name is clicked, a list menu of candidate data or a window indicating a range of data that can be set is displayed (the list menu and window are shown in FIG. 6). When data is selected from the candidate data list menu, the selected data is added to the recommended condition definition column.
[0030]
Next, the search result display screen setting 11 will be described.
The search result display screen setting 11 includes setting items of switching 11a, order 11b, field name 11c, sort order 11d, elevation 11e, processing designation 11f, and display size 11g.
The switching 11a and the order 11b are set by the same method as the switching 10a and the order 10b described above.
The field name 11c displays the field name of the table to be searched. When the field name is clicked, the field type and size are displayed in a separate window (FIG. 7 shows a display example of the window).
The sort order 11d designates which field has priority for sorting when it is desired to sort and display records in the search result display window. Click the frame of the sort order 11d in descending order of priority. To cancel sorting, click again to cancel.
The elevating / lowering 11e sets the sort type. Clicking on the up / down column switches between "ascending order" and "descending order".
The process specification 11f is specified when data is processed and output when displaying the search result. A format for processing the search result is set in the processing specification frame. Refer to FIG. 8 for the processing designation method.
The display size 11g sets the number of display bytes of the field name. Set the number of display bytes to a value greater than the length of the field name. When a value shorter than the field name is set, the display size is set by the length of the field name. If the actual value of the record obtained by the search is larger than the display size, only the display size is displayed. When confirming the size set in the field name, as described in the field name 110, when the field name is clicked, the size is displayed in another window (FIG. 7).
Since the details of the action list 12 will be described in a later embodiment, the description is omitted here.
[0031]
FIG. 6 is a diagram illustrating an example of guidelines set in each field in the recommended condition input.
FIG. 6A is a diagram illustrating an example of numerical / date-type guidelines. This guideline is, for example, a guideline indicating the range of data that can be set, which is displayed when the field name 10c of the search condition input screen setting 10 in FIG. Yes, the data to be displayed must be preset for each field. Users can refer to the guidelines when setting recommended conditions.
FIG. 6B is a diagram illustrating an example of a guideline for a candidate data list. For example, it is a guideline displayed by clicking “part name” in the field name 10c of FIG. 5 and introduces part of actual data stored in the table “KP11P”. When selecting data from this guideline as a recommended condition for “Part Name”, you can select by selecting the data you want to select and clicking.
[0032]
FIG. 7 is a diagram showing an example of a window displaying field types and sizes.
For example, when the “P / N part number” in FIG. 5 is clicked, the type and size of the set field can be referred as shown in FIG.
FIG. 8 is a diagram illustrating a format for specifying processing.
According to FIG. 8, there are four types of processing designation types: character string addition, calculation processing, amount processing, and date processing. When adding a character string, the search result is substituted into the “$$” or “&&” part. For example, if the search result is assigned to the processing designation of “total $$ pieces”, “total 100 pieces” are processed. As an example of calculation processing, when “0.01” is input to the processing formula “&& × 100”, “0.01 × 100” is displayed, and the search result is displayed as “1.0”. In addition, when the processing designation type is an amount, if “MONEY” is designated in the format, a comma is inserted every three digits and displayed. In the case of a date, if “DATE1” is specified as a format, “/” is inserted between “year”, “month”, and “day”, and if “DATE2” is specified as a format, “year”, “month”, and “day” are changed. It is inserted and displayed between data.
FIG. 9 is a diagram showing a “setting” menu.
The “setting” menu is a menu displayed when “setting” in the menu bar of the screen setting in FIG. 5 is clicked.
FIG. 10 is a flowchart showing a procedure for setting a search condition input window and a search result display window.
[0033]
Next, according to the flowchart of FIG. 10, the setting of the search condition input window and the setting of the search result display window will be described below with reference to FIGS.
First, in order to select a terminal node to be searched, the tree box shown in FIG. 2 is displayed (S1).
The search condition input window can only be set at the end node, and if the user does not have access to the information among the end nodes, the screen setting for that end node cannot be performed. To do. For this reason, the tree displayed in the tree box in FIG. 2 is a tree to which the user has a reference right. Next, a tree to be searched is selected from the displayed tree boxes (S2). In this embodiment, “part information” in the tree box displayed in FIG. 2 is clicked and selected as a search target. When a tree is selected, nodes of the selected tree are displayed on the tree display screen of FIG. Further, a table for screen setting is selected from the tree display window of FIG. 3 (S4). In this embodiment, “MOS digital IC (C-MOS logic)” is clicked and selected from the tree display screen of FIG. Select “MOS Digital IC” in FIG. 3, click “Screen” in the menu bar, and select “Screen Settings” from the “Screen” menu in FIG. 4. The screen setting window in FIG. 5 is displayed. (S6). Then, a search condition input window and a search result display window are set (S7).
[0034]
First, the search condition input screen setting 10 shown in FIG. 5 is set as follows.
First, the switch 10a is clicked to select a field name to be displayed on the search condition input screen when executing the search. According to FIG. 5, all the frames of the switching 10a are black frames, so that “P / N part number”, “product code”, “part name”, “specification”, and “part standard classification 1” are selected. Yes. Further, although not shown in FIG. 5, by moving the scroll bar 13, the “Manufacturer model name”, “DB registration date”, and “Part shape name” under the “Part standard category 1” are selected. To do.
Next, the order 10b to be displayed in the search condition input window is designated. According to FIG. 5, the order “1” is set for the “P / N product number”, the order “2” for the “product code”, the order “3” for the “part name”, and the order “3” for the “specification”. 5 ”and“ part standard category 1 ”, the order“ 4 ”, and although not shown in FIG. 5,“ maker model name ”is the order“ 6 ”, and“ DB registration date ”is the order“ 7 ”. The order “8” is designated for “part shape name”.
Finally, the recommended condition definition 10d is defined. According to FIG. 5, “A, B, C” recommended conditions are defined in “Parts Standard Category 1”. This is a condition for searching for records in which the value of “part standard category 1” is “A”, “B”, or “C”.
The above is the setting content of the search condition input screen setting in the first embodiment.
[0035]
Next, the search result display screen setting 11 of FIG. 5 is set as follows.
First, the switch 11a is clicked to set a field name to be displayed in the search result display window. According to FIG. 5, “P / N part number”, “part name”, “specification”, and “latest order date 1”, which are not shown in FIG. “Manufacturer model name” under “Part standard category 1” is set to be displayed in the search result display window.
Next, the order 11b is set, and the display order of the fields displayed in the search result display window is designated. According to FIG. 5, the “P / N part number” is the order “1”, the “part name” is the order “2”, the “specification” is the order “3”, and not shown in FIG. The order “4” is set for the “maker model name”, and the order “5” is set for the “latest order date 1”.
Next, the sort order 11d is set, and it is designated for which field the sorting is prioritized in the search result display window. According to FIG. 5, “P / N part number” is set as the sort order “1”, “part name” is set as the sort order “2”, and “latest order date 1” is set as the sort order “3”.
Next, the elevating / lowering 11e is set, and the sort type of the sort order set previously is set to be in ascending order or descending order. According to FIG. 5, “P / N part number” is set to “ascending order”, “part name” is set to “ascending order”, and “latest order date 1” is also set to “ascending order”.
Next, the processing designation 11f is set. “DATE1” is designated as the processing designation of “latest order date 1”. This specification is a processing specification for separating the date with a slash (/).
Next, the display size 11g is set. According to FIG. 5, “15” is set for “P / N part number”, “20” is designated for “part name”, and “20” is designated for “specification”. Further, although not shown in FIG. 5, “18” is designated for “maker model name”, and nothing is designated for “latest order date 1”. The reason why the display size is not specified for “latest order date 1” is that the length of the data to be displayed is smaller than the length of the title “latest order date 1”, so that setting is not necessary.
The display size 11g is specified when the data length is longer than the display byte count of the field name as the title.
The above is the setting content of the search result display screen setting in the first embodiment.
[0036]
As described above, after setting the search condition input window and the search result display window, click the “Setting” button in the menu bar of FIG. 5 to display the settings of FIG. “Save end” is selected from the menu to save the setting contents (S8). The storage name is automatically assigned by the system so that the storage is recognized as the search condition input setting and the search result display screen setting for the table name “KP11P”. Furthermore, in order to distinguish users, “user ID” is also used as part of the stored name.
This completes the description of the search condition input screen setting and search result display screen setting.
[0037]
As described above, the search condition input screen setting and the search result display screen setting can be performed for each table prior to the execution of the search and are registered for each table, so that the table search can be designed separately from the execution. Once designed, the same search conditions and the same search result are edited each time a search is executed. Even when the setting is changed, the user can customize the already set contents, so that the setting is easier than the new setting.
[0038]
Embodiment 2. FIG.
In this embodiment, an example in which a search is executed based on the setting contents of the search condition input screen and the search result display screen set in the first embodiment will be described below.
[0039]
First, the drawings will be described.
FIG. 11 is a flowchart showing a procedure for searching a table.
FIG. 12 is a diagram showing a “search” menu.
FIG. 13 is a diagram showing a search condition input screen.
In FIG. 13, reference numeral 14 denotes AND / OR, which specifies whether a relationship with a condition set in another field is an AND condition or an OR condition after setting a search condition for one field. It is a button for. For example, according to FIG. 13, the condition “* 74HC *” is set in the “manufacturer model name”, but after setting the above condition, click is performed in a state where “AND” is displayed in the AND / OR 14. And the search condition for “maker model name” is an AND condition. Reference numeral 15 denotes a NOT button used when searching for data other than those that match the set condition (when set, a black frame appears). For example, the search condition specified for “DB registration date” “> = After setting the condition “1900/01/01”, clicking the NOT button 15 sets the search for data other than “DB registration date” “> = 1900/01/01”. Reference numeral 16 denotes a field name, which displays a field name set to be displayed in the search condition input screen setting. When the field name 16 is clicked, if a guideline is specified, a candidate for input data or a range (reference value) of the input data is displayed on the menu. Reference numeral 17 denotes a search condition, and the search condition for the field name 16 is input. Separate multiple conditions with commas. A plurality of conditions separated by commas are OR conditions, and records that meet any of the conditions are searched. In inputting the search condition, the recommended condition 10d defined in the setting of the search condition input screen described in the first embodiment can be used. To use the recommended condition 10d, clicking the search condition column displays a list menu of recommended conditions (see FIG. 18), and data is selected from the displayed list of recommended conditions. The selected data is added to the search condition 17. The recommended conditions can be used as search conditions as they are, but it is also possible to create and set other conditions by customizing them. Reference numeral 18 denotes storage of setting conditions. When this button is clicked, the search conditions set in the window can be stored. Since the search condition name input window is displayed (see FIG. 19), the user inputs the name from the keyboard 6. 19 is a search condition call. When a search condition to be called is selected from the search condition list 21 and this button is clicked, the set search condition is read and displayed in a window. Reference numeral 20 denotes deletion of a search condition. When this button is clicked, the search condition selected from the search condition list 21 can be deleted. A search condition list 21 displays a list of search condition names stored in the search target table. However, only those saved by the running user are displayed. The search condition list can be used when the user sets the search condition separately from the recommended condition. The recommended condition was set for the field, but the search condition list can be set for the table. It is a condition. Therefore, various conditions can be set and referred to regardless of the field.
FIG. 14 is a diagram showing a search result display screen. Based on the search condition set in FIG. 13, the terminal node “MOS digital IC (C-MOS logic)” of the tree name “part information” is searched. The search result is displayed based on the search result display screen setting set in the first embodiment.
According to FIG. 14, there are 174 records corresponding to the search condition, and there are a total of 4 screens.
[0040]
FIG. 15 is a diagram showing a search result output menu. This menu is displayed when “Output” is selected from the menu bar of FIG.
FIG. 16 is a diagram illustrating a screen for performing settings for outputting the search result to a file.
This screen is displayed when “file output” is selected from the output menu of FIG.
In order to output the search result to a file, “output file name”, “output format”, “output field designation”, and “output record designation” are designated on the screen of FIG.
There are two types of output formats: text format and spreadsheet format. An example in the case of outputting in a spreadsheet format is shown in FIG. In the output field designation, it is selected whether to output all the fields of the search target table or only the fields displayed in the window. Furthermore, in the output record designation, all records corresponding to the search condition are output, or a record to be output is selected from the search result display window, and whether only the record is output is selected.
FIG. 17 is a diagram illustrating a screen for performing settings for outputting the search result to the printer.
This screen is displayed when "Printer output" is selected from the output menu of FIG.
In order to output the search result to the printer, “output printer name”, “output field designation”, and “output record designation” are designated on the screen of FIG.
Note that the settings for “output field designation” and “output record designation” are the same as when the output result is output to the file of FIG. 16 described above.
[0041]
FIG. 18 is a diagram illustrating a screen displaying an example of recommended conditions.
In FIG. 18, “1829 × *”, “* 1219 × 2438”, and “* 900 × 1800 MM” are registered as recommended conditions in the search condition input screen setting. To select a search condition, place the cursor on the condition you want to select from the displayed search conditions and click to select it. Unlike the search condition list, it is unique to the field and is displayed when you click the field name.
[0042]
Next, a procedure for executing a search will be described with reference to the flowchart of FIG.
In the flowchart of FIG. 11, the processes of S1 to S3 are the same as the processes of S1 to S3 of FIG. 10 described in the first embodiment, and the description thereof is omitted in this embodiment.
From the tree display screen of FIG. 3, the terminal node in which the table to be searched is set is selected (S9). In this embodiment, in order to search for “MOS digital IC (C-MOS logic)” which is a terminal node, the terminal node is selected by clicking with the mouse.
Further, “Search” is selected from the menu bar of FIG. 3, and “Search” is selected from the “Search” menu of FIG. 12 displayed. When “execute search” is selected, the tree display window shown in FIG. 3 disappears, and the search condition input window shown in FIG. 13 is displayed (S10).
A method for setting search conditions will be described with reference to FIG. According to FIG. 13, the search conditions are set for “manufacturer model name” and “DB registration date”. First, “maker model name” is clicked, and a wild card (*) is used to set a condition for searching records including “74HC” in the data of the manufacturer model name.
Next, the search condition for “DB registration date” is set, but before that, the AND / OR 14 is clicked, and the connection of the condition for “maker model name” is set. Here, it is confirmed that “AND” is displayed in the AND / OR 14 in order to search records that satisfy both of the search conditions set in the “maker model name” and “DB registration date”. If a record satisfying either one is to be searched, it is confirmed that “OR” is displayed in AND / OR 14 (if AND is displayed, click to change to “OR”).
Then, a search condition is set for “DB registration date”. According to FIG. 13, the condition “DB registration date” is set to “after January 1, 1990” (S11).
After the conditions are set as described above, “Search” in the menu bar is selected, and “Search” is clicked from the displayed “Search” menu (FIG. 12). When “Search” is clicked, records corresponding to the search condition are displayed in order as shown in FIG.
The search results displayed in FIG. 14 are edited according to the setting contents of the search result display screen setting 11 of FIG. 5 set in the first embodiment. For example, since “DATE1” is set in the process designation 11f for “latest order date 1”, editing is performed so that the date is separated by “/”.
[0043]
As described above, according to the first embodiment and the second embodiment, the screen for inputting the search condition to be set when performing the search is set in advance by the search condition input screen design 3a. Fields that are not scheduled to be specified can be prevented from being displayed, and the user can easily set search conditions. In addition, since recommended conditions can be set, search conditions can be set using recommended conditions that have been set in advance without entering new search conditions during search execution, and errors in specified conditions due to input errors can be reduced. be able to.
[0044]
Embodiment 3 FIG.
In this embodiment, a database device that starts the next process based on the information stored in the action management table based on the results of the search in the first and second embodiments will be described below. Give an explanation.
[0045]
First, the drawings will be described.
FIG. 20 is a diagram showing a system configuration of the database apparatus in this embodiment.
In FIG. 20, reference numeral 50 denotes a process definition unit for defining and storing executable processes based on the search result of the search unit 4. The process definition unit 50 includes an interactive definition support unit 50a, and the interactive definition support unit 50a can define a process in an interactive format. An action management table 51 manages definition information defined in the process definition unit 50. A process execution unit 52 analyzes the definition information stored in the action management table 51, and generates a command necessary for the process to be activated next.
The command generation unit 52a generates the command. The other reference numerals in FIG. 20 are the same as those in FIG. 1 described in the first embodiment, and a description thereof will be omitted.
[0046]
FIG. 21 is a diagram illustrating a management tool.
FIG. 22 is a flowchart showing a procedure for defining a process in the action management table.
FIG. 23 is a diagram showing a search type selection screen.
FIG. 24 is a diagram showing a screen for setting a table space name (database name) in action setting.
FIG. 25 is a diagram showing a screen for setting a table name in action setting.
FIG. 26 is a diagram showing a “list” menu. This menu is displayed when “list” in the menu bar of the action management screen in FIG. 24 is clicked.
FIG. 27 is a screen for setting an action title.
FIG. 28 is a diagram showing an “edit” menu. This menu is displayed when “Edit” in the menu bar of the action management screen in FIG. 24 is clicked.
FIG. 29 is a diagram showing a script selection screen.
[0047]
Next, the procedure for setting the definition information in the action management table will be described with reference to the flowchart of FIG.
“Action management” is selected from the management tool shown in FIG. 21, and the “execute” button is clicked (S20, S21). When the action management is selected, the search type selection screen shown in FIG. 23 is displayed (S22). A search method for an action to be defined is selected and clicked from “common item search” and “parameter search” displayed on the search type selection screen shown in FIG. 23 (S23). “Common item search” is selected when an intermediate node is specified and component information is searched from a plurality of tables below the node. “Parameter search” searches for component information from a table corresponding to a node by designating a terminal node.
In this embodiment, since the action to be activated next is set based on the result of searching for “MOS digital IC” which is the terminal node that has been searched in the second embodiment, the search type of FIG. Select “Parameter Search” from the selection screen. When “parameter search” is selected, the action management screen shown in FIG. 24 is displayed (S24). In FIG. 24, the table space name (database name) including the target table for starting the action is selected from the list of table space names displayed on the action management screen. In this embodiment, “PNDB” is selected. When the table space name is selected, the selected “PNDB” and the table space name are displayed on the left side of the table space name as shown in FIG. Further, in order to register the target table for starting the action, the “list” in the menu bar of FIG. 25 is clicked to display the “list” menu in FIG. 26. From the “list” menu, the “table list” is displayed. "Is selected (S25), and a table name is selected. In this embodiment, “KA21M” is selected as the table name from the list of table names shown in FIG. When the table name is selected, “KA21M” is displayed as the table name as shown in FIG. Furthermore, the title name of the action to be set is set. When creating another action based on an already registered action, select “List” in the menu bar of FIG. 27 and select “Action List” from the displayed “List” menu. Select the appropriate action from the displayed action list. Then, the predefined action information can be changed (S26).
[0048]
In the case of newly registering an action, “New” is selected from the edit menu of FIG. 28 displayed when “Edit” in the menu bar of FIG. 27 is selected, and an action is newly registered (S27). . When registering a new action, first set the script. The script is set on the script selection screen shown in FIG. 29 displayed when “new registration” is selected from the “edit” menu. The script indicates an action type. In the database apparatus according to the present invention, there are three scripts. The three scripts are “all field display”, “other database search”, and “command activation”. “Display all fields” is a function for displaying the values of all fields in the searched table.
It should be noted that the record for which all fields are displayed is executed for one record arbitrarily selected by the user from the records displayed on the search result display screen.
In “other database search”, the user arbitrarily selects a record from the screen displaying the search result, and searches other tables using the data of the record as a search condition. The action setting defines the relationship between the field of the search result and the field of the other table to be searched (this relationship is hereinafter referred to as correlation).
“Command activation” defines a command to be executed with the record data of the search result as an argument. For example, the result of searching for “MOS digital IC” in the second embodiment is displayed on the search result display screen of FIG. 14, but the parts catalog is displayed based on the displayed “P / N part number”. be able to.
From the script selection screen shown in FIG. 29, one target script is selected, an action title is input, and then an “execute” button is clicked (S28). Clicking the “Execute” button displays each setting window depending on the type of action. The user sets necessary definition information in the displayed setting window (S29, S30, S31).
[0049]
Next, a detailed setting method will be described below in accordance with the script type set in S28.
First, the “all field display” setting will be described.
FIG. 30 is a flowchart showing the procedure for setting the all-field display.
FIG. 31 is a screen for setting an action execution right.
[0050]
According to the flowchart of FIG. 30, when the script type of “display all fields” is selected in S28 described above, the execution right setting screen of FIG. 31 is displayed. On this screen, set the right to execute, and select “Action” in the menu bar. Click “Execute” from the action menu that appears (the action menu is not shown), and set the action for all field display ( S40).
The execution right is an authority provided for each user in order to protect the database. In this embodiment, it is assumed that the execution right A is given by the execution right A. Execution rights can be set by clicking the execution right frame to be set. In FIG. 31, execution rights A, B, and C indicate that an action can be executed (a black frame indicates that an execution right is set).
The above is the method for setting the action for displaying all fields.
[0051]
Next, a procedure for setting the “search for other database” action will be described.
FIG. 32 is a flowchart showing a procedure for setting an action for searching another database.
FIG. 33 is a diagram showing a screen for defining an action for searching for another database.
FIG. 34 is a diagram showing a screen for defining a table space name and a table name of a database to be searched.
FIG. 35 is a diagram showing a screen for setting a correlation.
FIG. 36 is a diagram showing a screen for setting execution rights.
[0052]
Next, a procedure for setting an action for searching for another database will be described with reference to the flowchart of FIG.
In the “other database search” setting, first, a table to be searched is set (S50). The table is set by clicking the corresponding table space name and table name from the selection window shown in FIG. 34 displayed when the “target table” in FIG. 33 is clicked. In this embodiment, the selection window table space name “PNDB” and the table name “KATAMEIM” in FIG. 34 are clicked. The clicked table space name and table name are displayed as “PNDB.KATAMEIM” as “target table” in FIG.
Next, field correlation is set (S51). The correlation setting window shown in FIG. 35, which is displayed when “correlation setting” in FIG. 33 is clicked, defines the correspondence between the search result field and the field of the table of another database searched using the search result. To do. The setting method is to select the field name displayed in the extraction field list of FIG. 35 and the field name of the search result to be matched with the mouse and click “Set”. A plurality of correlations can be specified, and the setting is repeated for the number of fields to be associated (S52). For example, in this embodiment, “PK_PN” in the extraction-side field list and “P_BUHIN” in the substitution-side field list in FIG. 35 are selected, and “Setting” is clicked to set the correlation. When “Setting” is clicked, the set correlation “PK_PN → P_BUHIN” is displayed as shown in FIG.
Next, the access right to the action is set in the other database search action window. To set the access right, click the execution right setting A to E shown in FIG. When this access right is set, the square frame for setting the execution right in FIG. 36 is changed from white display to black display. After setting the access rights, click “Action” in the menu bar of FIG. 36, select “Execute” from the displayed action menu, and set the other database search actions that have been set up in the table to the table. To do.
The above is the procedure for setting the database search action.
[0053]
Next, a procedure for performing the action setting of “command activation” will be described.
FIG. 37 is a flowchart showing a processing procedure for setting command activation.
FIG. 38 is a diagram showing a screen for setting a script in the action definition.
FIG. 39 is a diagram showing a screen for setting an argument.
[0054]
Next, a procedure for setting a command activation action will be described with reference to the flowchart of FIG.
First, a command script to be activated is input to the script field on the action creation screen of FIG. 38 (S60). In the command script, a command for displaying a file storing image data to be displayed when the action is activated is input. In this embodiment, a command “miff_sh” for displaying a file storing a part catalog which is one of “MOS digital ICs” is designated. Next, an argument is set (S61). The argument setting is made by clicking the “argument setting” in FIG. 38 and displaying the field that is the name of the file in which the image data is stored from the list of field names displayed in the argument setting window of FIG. Select. Since a plurality of fields can be set as arguments, field names are selected in order, and “set” is clicked (S62). In this embodiment, “K_PATH” is selected. After selection, when the “setting” in FIG. 39 is clicked, the set arguments are displayed on the action creation screen in FIG. Next, the access right to the action is set from the action creation screen of FIG. The access right is set in the same manner as the access right for searching other databases described above. In this embodiment, access rights are set for execution rights A, B, and C. After setting the access right, "execute" is selected from the action menu displayed by clicking "action" in the menu bar of FIG. 38, and the action is set in the table (S63).
The above is the action setting method for command activation.
[0055]
Note that the action definition described above must be defined for each table.
Further, the action definition information set as described above is stored in the action management table 51, and the process definition unit 50 manages this action management table. When the action is activated, the process execution unit 52 refers to the action management table, analyzes the definition information of the activated action, generates a necessary command by the process generation unit 52a, and executes the action.
The action management method will be described below.
In order to manage actions, for a table in the database, a table management table (FIG. 40B) that stores the table name and action ID, and an action management table that manages processes derived from the database search results ( FIG. 40 (A)) is provided with the database apparatus according to the present invention. In this database device, when a table is created, an action ID is numbered, and the table name and action ID are registered in the table management table.
The action derived from the search result is registered by the process definition unit 50 in the action management table with an attribute such as an action ID or a data delivery sequence to the action. At this time, it is assumed that the same ID is assigned to actions for the same table.
[0056]
FIG. 40 shows an image of the action management table and the records of the table management table.
The action definition information described above is registered in the action management table of FIG. The action title is set to “acttitle”. The script is set to “script”. “FIELD” is set in the case of all field display, “DBACCESS” in the case of other database search, and “script” in the command input in the script of FIG. 38 in the case of command activation. In this embodiment, “miff_sh” is set. The field correlation that has been set in the other database search is set with an argument in “srcfids” and “dstfids”. As shown in FIG. 41, the correlation of the fields set in this embodiment is set to “srcKids” as “PK_PN” as the extraction side field name and “dstfids” as the substitution side field name “P_BUHIN”. Is set. In the case of command activation, “K_PATH” is set in “srcfids” as shown in FIG. In the case of another database search, the target server name is stored in “machine”, the target database name is stored in “dbname”, and the target table name is stored in “tblname”. Further, the execution right is stored in “reatA” to “reatE”. When the execution right is “1”, the execution right is assumed. When the action is activated, if the activated action is another database search, the SQL statement is automatically generated based on the definition information defined in the action management table and the search result, and the action is executed. To do.
[0057]
For example, when the search result as shown in FIG. 42 is displayed and the search result shown at the top is selected and another database search is started, the command generation unit 52a automatically executes the following SQL statement. Generate. In the action management table, “sfrfids” is set to “fldA, fldB, fldC”, and “dstflds” is set to store “fld3, fld2, fld1”.
select fld1, fld2, fld3,..., from db_1. table_1
where fld3 = 'data1' and fld2 = 123 and fld1 = '1994/12/12'
[0058]
Further, when the activated action is command activation, the command generation unit 52a generates a command for performing a system call such as vfork or system.
For example, if a search result as shown in FIG. 44 is displayed, the top record is selected and a command activation action is activated, the following command is issued. In addition, “MTIFF” is stored in “script” of the action management table, and “fldA” is stored in “srcflds”.
MTIFF tiff_data
[0059]
As described above, by providing the action management table, it is possible to separate the process definition derived from the search result from the database system. If a user ID is provided in the action management table, an action definition for the table can be performed for each user.
[0060]
Embodiment 4 FIG.
In this embodiment, an example in which the action defined in the third embodiment is executed based on the search result performed in the second embodiment will be described below.
There are the following three methods for starting an action.
The first is to select one action to be executed from the action list as shown in FIG. 14, select one record from the records displayed as the search result, and it is in the menu bar. Click “Execute Action”.
Second, one record is selected from the search results as shown in FIG. 14, one action to be executed is selected from the action list, and double-clicked.
Third, one action to be executed is selected from the action list as shown in FIG. 14, one record is selected from the records displayed as search results, and double-clicked.
An action can be activated by the above three methods.
[0061]
First, an example of executing a command activation action will be described with reference to the flowchart of FIG.
From the action list displayed in the search result display window shown in FIG. 14, “catalog display 1” for command activation is selected (S70). It is assumed that “P / N part number” is specified as an argument of “catalog display 1”.
Next, click the record whose NO is “1” from the records displayed as search results, and click “Execute Action” in the menu bar. A catalog of parts with the number “KP41P200H06” is displayed (S71).
[0062]
Next, the action activation of all field display will be described.
Select “Display all fields” from the action list shown in FIG. 14, select a record whose NO is “4” from the records displayed as the search results, and select “Execute action” from the menu bar. When is clicked, a screen as shown in FIG. 47 is displayed. In the screen of FIG. 47, all fields of the selected record are displayed.
[0063]
Next, execution of another database search will be described with reference to the flowchart of FIG.
According to FIG. 48, first, “other database search 1”, which is an action for searching for another database, is selected from the action list of FIG. 14 (S80).
It is assumed that “other database search 1” is the same action as “quality information search” with the action title set in the third embodiment.
Next, from the records displayed as search results, double-click the record to be input as the search condition for other databases (S81).
In the other database search action, a window for inquiring whether to set a search result display screen for displaying a result of the database search to be performed is displayed as shown in FIG. Therefore, in response to the inquiry shown in FIG. 49, the user selects “requires screen setting” and clicks “execute” to set the search condition and the search result display screen. Do.
In the search condition input screen that is displayed, field information of the selected record is input. When changing the displayed search condition, the changed contents are set (S83), the search condition is set (S84), and "search" on the menu bar is clicked to execute the search.
[0064]
As described above, by performing action definition in advance, the user can search by simply selecting a process from the action list without creating a program that executes the action to be activated next from the screen on which the search results are displayed. Based on the result, the process to be started next can be easily executed.
[0065]
Embodiment 5. FIG.
In this embodiment, a method for changing action definition information once defined will be described below.
[0066]
FIG. 50 is a flowchart showing a procedure for changing action activation information.
According to FIG. 50, an action whose activation information is to be changed is selected from the action list window as shown in FIG. 27 (S90). After selecting an action, click “Edit” in the menu bar and select “Change Action” from the edit menu shown in FIG. When “Change Action” is selected, the action creation screen shown in FIG. 33, the action creation screen shown in FIG. 38, and the action creation screen shown in FIG. 31 are displayed corresponding to the script type. The information to be changed is reset (S92).
The resetting method is performed in the same manner as the definition information setting method described in the third embodiment, and the description thereof is omitted in this embodiment.
[0067]
Next, the action deletion will be described.
51, the action to be deleted is selected from the action list of FIG. 27 (S100). Then, “Delete” is selected from the edit menu of FIG. 28 displayed by clicking “Edit” on the menu bar. When “Delete” is selected, a deletion confirmation window as shown in FIG. 51B is displayed (S101). When deleting, the user clicks “Execute” to delete the action (S102).
[0068]
Further, when changing the title of the action, according to the flowchart showing the procedure for changing the title of the action shown in FIG. 52, the action whose title is changed is selected from the action list window shown in FIG. 27 (S110). Then, “Edit” is selected from the menu bar, and “Change Title” is selected from the “Edit” menu shown in FIG. When “Change Title” is selected, the title change screen shown in FIG. 53 is displayed. The changed title is set again, and “Execute” is clicked to change the action title (S112).
[0069]
When setting a default action, an action to be a default is selected from the action list window of FIG. 27 (S120). Then, “default setting” is selected from the editing menu of FIG. 28 displayed by clicking “editing”. When “default setting” is selected, the menu of FIG. 55 is displayed. To set, select “setting” and click. To cancel the setting, click “cancel setting” (S121). Then, a confirmation screen is displayed, and “execute” is clicked to set a default (S122). When “default setting” is selected from the edit menu, a confirmation screen shown in FIG. 56A is displayed. If “cancel setting” is selected, a setting cancellation confirmation screen shown in FIG. 56B is displayed. When the default is set, “*” is displayed in the default setting column of the action list window shown in FIG.
The default setting is for setting an action that can be executed by clicking only “execute action” in the title menu bar without selecting anything from the action list when executing an action. The action list is highlighted for actions that have default settings.
[0070]
Next, action privilege change will be described.
According to the flowchart of the privilege change procedure for the action in FIG. 57, the action for changing the privilege is selected from the action title list displayed on the action management screen in FIG. 27 (S130). Next, “Change privilege” is selected from the edit menu of FIG. 28 displayed by clicking “Edit” in the title bar (S131). When “Change Privilege” is selected, the privilege change screen shown in FIG. 58 is displayed. The changed privilege is set, and “Execute” is clicked to change the access right (S132).
In FIG. 58, a black square in the execution right setting indicates that there is an access right.
[0071]
As described above, even if an action definition has been performed once, it can be changed, so even if a user sets a new action, by changing the action definition information that has already been set, New action definitions can be easily made.
[0072]
Embodiment 6 FIG.
In this embodiment, setting of guidelines will be described.
FIG. 59 is a system configuration diagram for realizing the database apparatus according to the present invention.
In FIG. 59, reference numeral 53 denotes a guideline defining unit for defining and storing candidate data to be displayed by the screen design unit 3. Other symbols are the same as those in FIG.
FIG. 60 is a screen for defining a guideline activated from “table management” of the management tool shown in FIG. If the numeric type / date type (NUMER / DATE) is selected as the data type in the search guideline 56, the guideline as shown in FIG. 6A is displayed when the field name on the screen setting screen is clicked. When “GROUP” is selected as the search guideline 56, the guideline as shown in FIG. 6B is displayed.
[0073]
Although the guideline for the candidate data list in FIG. 6B displays a part of the data in the database to be searched, it takes time to extract the data to be displayed when the database becomes large. In such a case, it is possible to create a database in which only data to be displayed in the guideline is registered, and to design the data in the database.
The setting method is such that, when “MASTER” is selected in the search guideline 56 of FIG. 60 and the MASTER setting 57 is clicked, a table space 58 for the guideline, a table 59, and a set value field 60 are displayed on the MASTER setting screen of FIG. Is specified. The candidate data displayed by clicking the “part name” in the field name 10c in FIG. 5 is only the seven types displayed in FIG. 6B, and the actual number of data is 100,000. . If you create a database for guidelines and set it to refer to the seven types of data registered there, the time to extract the data can be greatly reduced.
[0074]
If the comment field 61 is designated on the MASTER setting screen of FIG. 61, the candidate data can be annotated. The comment field 61 is created in the same table as that storing the guideline data. FIG. 62 is a diagram illustrating an example of a guideline for a candidate data list with annotations. For example, it is a guideline displayed by clicking “part standard category 1” in the field name 10c of FIG. 5, and the guideline database data corresponding to the recommended condition of “part standard category 1” is displayed. The setting value 67 in FIG. 62 displays candidate data for recommended conditions, and the comment 68 displays an annotation corresponding to the candidate data. As a recommended condition, when selecting data from these guidelines, you can select by selecting the data or annotation you want to select and clicking.
[0075]
63 is a character attribute setting screen displayed when the character attribute setting 63 in the MASTER setting screen of FIG. 70 is clicked. In the font 65 of the character attribute setting screen, the font of data to be displayed in the guideline can be designated. When the character attribute setting screen is displayed, the data in the table designated on the MASTER setting screen is displayed in the data 64. From here, select the data whose font you want to change, and press the button next to the font 65 to select the font you want to set from the menu that appears. There are four types of fonts: “Mincho”, “Gothic”, “Bold”, and “Italic”. FIG. 64 is a guideline displayed by clicking the “part standard category 1” in the field name 10c of FIG. 5 after changing the font of the data “R” to Gothic on the character attribute setting screen shown in FIG.
[0076]
In addition, in the character modification 66 on the character attribute setting screen in FIG. 63, “underline”, “overline”, and “erasing line” to be added to the data displayed in the guideline can be designated. Select data to be character-modified from the data 64, and click one of the buttons "Underline", "Overline", and "Straight Line". If you want to change the line type or type, select what you want to display from the line type or type menu to the right of the clicked button. FIG. 65 is displayed by clicking “Part Standard Category 1” in the field name 10c of FIG. 5 when “Straight line” is set in the character modification of the data “G” on the character attribute setting screen shown in FIG. It is a guideline.
[0077]
The search condition 62 on the MASTER setting screen in FIG. 61 specifies the narrowing condition when it is desired to further narrow the data from the data in the guideline database and display it in the guideline. The condition specification format is the same as the search condition input on the search condition input screen described above. By specifying the narrowing-down conditions, it is possible to devise measures such as preventing data that the user does not want to set as recommended conditions from being displayed on the guideline.
[0078]
【The invention's effect】
As described above, according to the first invention, the screen design unit arbitrarily designs the search condition input screen for inputting the conditions for searching the data in the database. For this reason, the screen for inputting search conditions is fixed in the conventional database search tool, but by using the database device of the present invention, it can be designed not to display information unnecessary for the user. There is an effect of easy input.
[0079]
Further, according to the second invention, the screen design unit further arbitrarily designs a search result display screen on which the search result is displayed. For this reason, it is possible to design the search result display screen for inputting the search conditions and designating the display order, the field to be displayed, etc. separately, which makes it easier for the user to design and reduces setting errors. There is.
[0080]
According to the third invention, the screen setting unit selects an arbitrary field. For this reason, the user can easily specify necessary fields when designing the search condition input screen and designing the search result display screen, and unnecessary fields are not displayed. Therefore, there is an effect that design errors due to input errors can be reduced.
[0081]
According to the fourth invention, the display order of the field selected by the screen design unit is designated. Therefore, the user can easily specify the display order when designing the search condition input screen and designing the search result display screen. In addition, since the order of the fields displayed on the search condition input screen and the order of the fields specified on the search result display screen can be specified in different orders, there is an effect that a convenient database search environment can be provided by the user.
[0082]
According to the fifth aspect of the invention, the screen design unit sets search conditions in advance. For this reason, if a frequently used search condition is set in advance for the field selected for the search condition input screen, the user can easily specify a condition rather than specifying a new condition. is there. Moreover, if a new condition is specified by customizing it based on a preset condition, it is possible to easily specify the condition and to reduce mistakes in specifying the condition.
[0083]
According to the sixth aspect, the screen design unit designates a display format. For this reason, it is possible to easily specify a display format such as comma editing, ¥ editing, and expansion of the display frame for the field selected for the search result display screen, making it easy to see the search result and convenience for the user. There is an effect that it is possible to provide a good database search environment.
[0084]
According to the seventh invention, the process definition unit stores in advance the process that can be executed based on the search result, and the process execution unit executes the process defined in the process definition unit. For this reason, the user has confirmed the search result in the past, and the user has designated again the process to be started next based on the result, but the next start is performed based on the search result by using this database device. If the process is known in advance, the process to be started next can be defined in advance and the next process can be automatically started after the search process is completed. There is no need to specify it again, and it is possible to provide a database search environment that is convenient for the user.
[0085]
According to the eighth invention, the process definition unit can define a plurality of processes, and the process execution unit selects and executes at least one process from the plurality of processes. Therefore, even when there are a plurality of processes to be activated next depending on the pattern of the search result, there is an effect that can be easily handled by using the database device according to the present invention.
[0086]
According to the ninth invention, the process definition in the seventh invention is defined by using the interactive definition support unit provided in the process definition unit. For this reason, it is possible to easily define the process to be started next, and it is possible to easily define the process even for the first-time user.
[0087]
According to the tenth invention, the process to be started next after the definition in the seventh to ninth inventions is stored as an action management table, and the action correction unit provided in the process execution unit performs the action management. The definition information stored in the table is analyzed, and necessary commands are generated. Therefore, when defining the process to be started next by the user, it is possible to easily define the process to be started next without considering the interface between the database device and the system environment surrounding the database device. There is an effect that the database apparatus according to the present invention can be used without requiring special knowledge.
[0088]
According to the eleventh aspect, the command in the tenth aspect is an SQL command. Therefore, the database apparatus according to the present invention can be used in the existing database and the system environment surrounding the database, and when a new database apparatus is introduced, there is an effect that can be realized at low cost.
[0089]
According to a twelfth aspect, the command is a system call. For this reason, the same effect as the eleventh can be obtained.
[0090]
In the thirteenth invention, by displaying candidate data used as a search condition, the user can easily obtain data that can be specified as a condition without knowing the data in the database. It is possible to easily specify the conditions in, and to further reduce specification mistakes.
[0091]
In the fourteenth invention, there is an effect that a guideline with better operability can be provided by selecting candidate data from an arbitrary table.
[0092]
In the fifteenth aspect, by adding annotations to the candidate data, the user can know the meaning of the symbolized value registered in the database in the database search operation. There is an effect that it is possible to save the trouble of separately checking.
[0093]
In the sixteenth aspect of the invention, if the guideline data is classified according to the font, the user can also visually classify the data, which is easy to select.
[0094]
In the seventeenth invention, data can be classified by highlighting the data, and the same effect as in the sixteenth invention can be obtained.
[0095]
In the eighteenth aspect of the invention, a condition for narrowing down candidate data is provided, and data that should not be selected is excluded from the candidate data, so that the user can easily select more appropriate data.
[Brief description of the drawings]
FIG. 1 is a system configuration diagram for realizing a database apparatus according to the present invention.
FIG. 2 is a diagram showing a screen displaying tree information accessible by a user in the first embodiment.
FIG. 3 is a diagram illustrating nodes stored in tree information in the first embodiment.
FIG. 4 is a diagram showing a “screen” menu.
FIG. 5 is a diagram showing a screen setting window in the first embodiment.
6 is a diagram showing a guideline for a field in a recommended condition input in the first embodiment.
7 is a diagram showing field guidelines in Embodiment 1. FIG.
FIG. 8 is a diagram showing a processing designation format in the first embodiment.
FIG. 9 is a diagram showing a “setting” menu in the first embodiment.
FIG. 10 is a flowchart showing a procedure for setting a search condition input window and a search result display window in the first embodiment.
FIG. 11 is a diagram showing a procedure for executing a search in the second embodiment.
FIG. 12 is a diagram showing a search menu.
FIG. 13 is a diagram showing a search condition input screen in the second embodiment.
14 is a diagram showing a search result display screen in the second embodiment. FIG.
FIG. 15 is a diagram showing an output menu in the second embodiment.
FIG. 16 is a diagram showing a search result file output screen in the second embodiment.
FIG. 17 is a diagram illustrating a screen for designating output of a search result to a printer in the second embodiment.
FIG. 18 is a diagram showing an example in which contents set as recommended conditions on a search condition input screen in the second embodiment are displayed.
FIG. 19 is a diagram showing a screen for storing search conditions set in the second embodiment.
FIG. 20 is a system configuration diagram showing an example of a database apparatus according to the present invention.
FIG. 21 is a diagram showing a management tool in the third embodiment.
FIG. 22 is a flowchart showing a procedure for defining an action in the third embodiment.
FIG. 23 is a diagram showing a search type selection screen in the third embodiment.
FIG. 24 is a diagram showing a screen for setting a table space name in action setting in the third embodiment.
FIG. 25 is a diagram showing a screen for setting a table name in action setting in the third embodiment.
FIG. 26 is a diagram showing a “list” menu in the third embodiment.
FIG. 27 is a diagram showing a screen for specifying an action title on the action management screen in the third embodiment.
FIG. 28 is a diagram illustrating an “edit” menu according to the third embodiment.
FIG. 29 is a diagram showing a script selection screen in the third embodiment.
FIG. 30 is a flowchart showing a setting procedure for displaying all fields in the third embodiment.
FIG. 31 is a diagram showing a screen for setting execution rights on the action creation screen in the third embodiment.
FIG. 32 is a flowchart showing a procedure for performing an action definition of another database search in the third embodiment.
FIG. 33 is a diagram showing a screen for defining an action for searching for another database in the third embodiment.
FIG. 34 is a table showing a list of table space names and a list of table names of a database to be searched in the third embodiment.
FIG. 35 is a diagram showing a screen on which a correlation field is set and a take-out field list and a substitution field list are displayed in the third embodiment.
FIG. 36 is a diagram showing a screen for setting an execution right on the action creation screen in the third embodiment.
FIG. 37 is a flowchart showing a procedure for defining a command activation action in the third embodiment.
38 is a diagram showing a screen for setting a script on the action creation screen in the third embodiment. FIG.
FIG. 39 is a diagram showing a screen for setting an argument on the action creation screen in the third embodiment.
FIG. 40 is a diagram showing an image of an action management table in the third embodiment.
FIG. 41 is a diagram showing data in an action management table for other database search in the third embodiment.
FIG. 42 is a diagram illustrating a search result in which the action of FIG. 41 is defined.
FIG. 43 is a diagram showing data in the action management table storing the definition of the command activation action in the third embodiment.
44 is a diagram showing a search result in which the action of FIG. 43 is defined. FIG.
FIG. 45 is a diagram illustrating a procedure of executing a command activation action in the fourth embodiment.
FIG. 46 is a diagram showing an example of a catalog displayed on the screen as a result of command activation in the fourth embodiment.
FIG. 47 is a diagram illustrating a result of activation of an action for displaying all fields in the fourth embodiment.
FIG. 48 is a flowchart showing a procedure for starting another database search action in the fourth embodiment.
49 is a diagram showing screen setting selection displayed when an action of searching for another database is executed in Embodiment 4. FIG.
FIG. 50 is a flowchart showing a procedure for changing action activation information in the fifth embodiment.
FIG. 51 is a flowchart showing a procedure for deleting an action in the fifth embodiment.
FIG. 52 is a flowchart showing a procedure for changing the title of an action in the fifth embodiment.
53 is a diagram showing a screen for performing a title change in Embodiment 5. FIG.
FIG. 54 is a flowchart showing a procedure for setting a default action in the fifth embodiment.
FIG. 55 is a diagram showing a setting menu.
FIG. 56 is a diagram showing a default action setting screen in the fifth embodiment.
FIG. 57 is a flowchart showing a procedure for changing privilege of an action in the fifth embodiment.
FIG. 58 is a diagram illustrating a screen for performing privilege change in the fifth embodiment.
FIG. 59 is a system configuration diagram for realizing the database device according to the present invention.
60 is a diagram showing a screen for defining guidelines in the sixth embodiment. FIG.
61 is a diagram showing a MASTER setting screen in the sixth embodiment. FIG.
62 is a diagram showing an example of an annotated candidate data list guideline in Embodiment 6. FIG.
FIG. 63 is a diagram showing a character attribute setting screen in the sixth embodiment.
FIG. 64 is a diagram showing guidelines displayed in the sixth embodiment.
FIG. 65 is a diagram showing guidelines displayed in the sixth embodiment.
66 is a diagram showing a screen for inputting search conditions in Conventional Example 1. FIG.
67 is a diagram showing an example in which search results are displayed on the screen in Conventional Example 1. FIG.
FIG. 68 is a diagram showing a screen for selecting a file to be inquired in Conventional Example 1;
FIG. 69 is a diagram showing a screen for defining an inquiry in Conventional Example 1;
FIG. 70 is a view showing a result of executing an inquiry in Conventional Example 1 on a screen.
71 is a diagram showing a selection query in Conventional Example 2. FIG.
FIG. 72 is a diagram for setting extraction conditions in Conventional Example 2;
FIG. 73 is a system configuration diagram of a database apparatus in Conventional Example 4;
FIG. 74 is a diagram illustrating a flow of determining a result of a search in a conventional example and starting the next process.
[Explanation of symbols]
1 database device, 2 CRT, 3 screen design unit, 3a search condition input screen design, 3b search result display screen design, 4 search unit, 5 mouse, 6 keyboard, 7 database, 10 search condition input screen setting, 10a switching, 10b Order, 10c Field name, 10d Recommended condition definition, 11 Search result display screen setting, 11a switching, 11b Order, 11c Field name, 11d Sort order, 11e Elevation, 11f Processing designation, 11g Display size, 12 Action list, 13 Scroll bar , 14 AND / OR, 15 NOT, 16 field name, 17 search condition, 18 save setting condition, 19 search condition call, 20 search condition deletion, 21 search condition list, 50 process definition part, 50a interactive definition support part, 51 action management table, 52 process execution unit, 52a frame De generation unit, 53 guidelines defining unit, 54 settings list, 55 select field names, 56 search for guidelines, 58 table space, 59 tables, 60 set value field, 61 comments field, 62 search criteria, 63 character attribute settings.

Claims (4)

(A) a database for storing data,
(B) a search unit for searching the data of the database,
(C) Based on the search result of the search unit, a process definition unit that allows a user to predefine an executable process and stores the process defined by the user;
(D) a process execution unit that executes the process stored by the process definition unit ;
A database device comprising:
The process definition unit stores definition information including a combination of a command script and a field name of a field set as an argument of the command script as an action management table, and the process execution unit includes a definition stored in the action management table. A command generation unit that analyzes information and generates a command required for processing using the command script stored in the definition information and the field value set as an argument in the definition information among the fields of the search result record A database apparatus characterized by comprising. The said process definition part memorize | stores a some process, and the said process execution part makes a user select at least 1 process from the said some process, and performs it, The process of Claim 1 characterized by the above-mentioned. Database device. The database apparatus according to claim 1, wherein the process definition unit includes an interactive definition support unit that allows a user to define a process using an interactive interface. It said command database apparatus according to claim 1, characterized in that it is a system call.

Images