JPH08241337A - Data base device - Google Patents

Abstract

PURPOSE: To obtain a data base device which enables a user to relate data optionally irrelevantly to the relation between data at the time of data base retrieval and also enables the user to set retrieval conditions when the retrieval conditions are set by selecting an optional filed in a data base and displaying only the selected field on a retrieval condition setting screen. CONSTITUTION: The user sets a table to be retrieved among plural tables stored in a data base 7 by using a screen design part 3, and specifies a field to be used on a retrieval condition input screen among the fields having the set table. Further, the screen design part 3 sets the retrieval condition input screen based the specified field prior to retrieval execution. The user inputs retrieval conditions on the retrieval condition input screen and a retrieval part 4 performs the retrieval under the inputted conditions.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a database device 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 for searching relational databases include BORLAND INTERNAT
Paradox for Win by IONAL, INC
There are dows. 66: Paradox for W
It is a figure which shows an example of the designation screen of the search condition in Windows. Note that FIG. 66 cites the diagram described on page 73 of the introductory manual. In addition, FIG. 67 shows Para.
FIG. 67 is a diagram showing a result of searching according to the search condition of FIG. 66 in dox for Windows. Note that FIG. 67 cites the diagram described in P73 of the input manual. In FIG. 66, customer. Although the conditions for searching for records in which the prefecture of the DB is "Okinawa prefecture" are specified, this search screen is a screen displayed when the [Search item value] button on the speed bar is clicked. As shown in FIG. 66, specify the search condition and click [OK] at the bottom left of the screen.
Click the button, and the customer. The first record in the DB in which the prefecture is “Okinawa prefecture” is searched and displayed in FIG. 67. Paradox as described above
In for Windows, when searching for records by item value, a screen for specifying the item value is prepared separately, and the user performs the operation to display the "Search for value" screen and then , Specify the item name to be searched. Also, Paradox for Windo
When inquiring about the information in the relational database in ws, the inquiry content is defined and the defined inquiry is executed. Figure 68 is Par
It is a figure which shows an example of the screen which selects the file made into the object of an inquiry in adox for Windows. Figure 69: Paradox for Windows
It is a figure which shows an example of the screen which defines the inquiry in ws. Figure 70: Paradox for Wind
FIG. 70 is a diagram showing a result of executing the inquiry defined in FIG. 69 in ows. 68 is an introduction manual P162, FIG. 69 is an introduction manual P166, FIG.
Refers to the diagram described on page 167 of the introductory manual. When the user makes an inquiry, right-clicks the [Open inquiry] button on the speed bar on the desktop and selects [New (N)]. When the selection is made, a "select file" dialog box as shown in FIG. 68 is displayed. For example, when the user makes an inquiry to the “orders database”, “orders.DB” is clicked on the file selection screen of FIG. 68 and the [OK] button is clicked. When you select the file,
The inquiry definition screen of FIG. 69 is displayed. For example, when inquiring about customers whose unpaid amount is 0 yen or more, and setting the items to be displayed as "order number, customer number, order date, shipping date, shipping method, billing amount, paid amount, unpaid amount" 69, check the above eight items and specify the condition that the unpaid amount is larger than 0 yen. When the inquiry specified as shown in FIG. 69 is executed, the Answ as shown in FIG.
The er table is displayed. As described above, in Paradox for Windows, when making an inquiry to extract a specific value for information in a relational database, the specific value is also specified on the screen for defining an inquiry.

Conventional example 2. Also, as a tool that can search a relational database, for example, Microsoft
Corporation's Microsoft Ac
There is cess. Figure 71 is a Microsoft Acc
It is a figure which shows the query which combined the goods table and goods classification table in ess using the classification code. (A query is an Access object that asks questions and defines extraction conditions for table data.) Note that FIG. 71 cites the diagram described in P92 of the Access introduction manual. Also, FIG.
FIG. 2 is a diagram showing an example of a screen for designating query extraction conditions in Microsoft Access.
Note that FIG. 72 cites the diagram described on page 92 of the Access introductory manual. If you want to search for records whose category name is "confectionery" or "soft drink" from the query shown in Fig. 71, click the "Design View" button on the toolbar, which is not shown in Fig. 72. The screen for specifying the extraction conditions is displayed. The condition to be extracted is "confectionery" or "soft drink", so move to the "extraction condition" cell for the "category name" field, enter "confectionery" in the cell and press the enter key. Move to the bottom of the cell where you entered "sweets", enter "soft drink", and press the enter key. The screen in which the extraction conditions are specified is shown in FIG. As described above, in Microsoft Access, the extraction condition specification frame that has all the items displayed in the query as fields is displayed, so specify the extraction condition for the field to be extracted and execute this to search results Can be obtained.

Conventional example 3. Further, as a method of searching the relational database and editing and outputting the search result, there is, for example, “Relational database search / output method” in “Japanese Patent Laid-Open No. 4-310183”. According to the above method, only the internal management number is read and stored in the user file when searching. Then, the reading and editing process of the actual data and the form output process are configured to be executed by a program independent of the search through the user file. FIG. 73 shows an embodiment of a relational database search / output method. FIG. 73
In the above, 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 sub program 500, and the main process and the sub process 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. Main program 2
00 receives various operation instructions such as search, display, and form output from the screen 100 of the terminal as commands. When the search instruction is received, the record to be searched and the record number are output to the record number file 400, and the subprogram 5
00 is started, and the processing ends. This part is the main processing. When the subprogram is started, screen 1 of the terminal
00 becomes available.

The subprogram 500 activated by the main program 200 reads the actual data from the relational database 300 using the record numbers stored in the record number file 400, edits the data, and forms 6
00 is output. This part is the sub process.

[0006]

Since the conventional database device is configured as described above, even items not included in the search target are displayed on the screen for specifying the conditions for searching the database as shown in FIGS. 69 and 72. It will be displayed. Therefore, there is a problem that unnecessary information is displayed, the screen is complicated, and it takes time to input and search the necessary information. Also, there is a tool that has a screen for specifying the search conditions separately as shown in FIG. 66, but since only one item can be specified as the search target on this screen, when selecting multiple items as the search target Must specify the same number of search conditions as the number of search target items on the screen of FIG. 66. Therefore, there is a problem that the operation is complicated for the user. Further, as shown in FIG. 73, the processing from the database search to the output is divided into the main processing and the sub processing, but the sub processing is only editing the search result. Therefore, when starting another program based on the search result, there is a problem that a program having a necessary function must be coded in a system environment having a database. (FIG. 74 shows a flow chart of activating the next process based on the conventional search result. According to FIG. 74, the user executes the programs of process A, process B, and process C activated based on the result determination. In a system environment equipped with a database such as the one described above, if the process to be started differs depending on the search result for each system user, it will take time and effort to customize the corresponding program for each user. was there. There is also a problem that it is difficult to expand the processing repertoire.

The present invention has been made to solve the above problems, and enables the following. The user arbitrarily sets the items to be searched among the items that the database has, and creates a screen for setting search conditions based on the settings. Further, the user can arbitrarily design the result display screen for displaying the search result. Further, the user can easily set the process to be started next interactively based on the search result without coding the program.

[0008]

The database device according to the first aspect of the present invention has the following elements. (A) The database stores data, (b) the screen design unit arbitrarily designs a search condition input screen for inputting conditions for searching the data in the database, and (c) the search unit designs in the screen design unit. Using the search condition input screen of the specified format, the search condition is input and the data is searched.

Further, the database device according to the second invention is characterized in that the screen designing unit further arbitrarily designs a search result display screen for displaying the search result searched by the searching unit.

Further, the database device according to the third invention is characterized in that the screen designing unit selects an arbitrary field from the fields forming the data.

The database device according to a fourth aspect of the present invention is characterized in that the screen designing unit specifies a display order of the selected fields.

The database device according to a fifth aspect of the present invention is characterized in that the screen designing unit presets search conditions that may be used in the field selected for the search condition input screen.

Further, the database device according to the sixth invention is characterized in that the screen designing unit specifies a display format of a field selected for the search result display screen.

The database device according to the seventh invention has the following elements. (A) The database stores data, (b) the search unit searches the data in the database, and (c) the process definition unit predefines executable processes based on the search result of the search unit. Then, (d) the process execution unit executes the process defined by the process definition unit.

In the database apparatus according to the eighth aspect of the present 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. It is characterized by doing.

The database device according to a ninth aspect of the present invention is characterized in that the process definition unit includes an interactive definition support unit that defines a process using an interactive interface.

In the database apparatus according to the tenth aspect of the 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. A command generating unit for generating a command required for processing is provided.

Further, the database device according to the eleventh invention is characterized in that the command is an SQL command.

The database device according to the twelfth aspect of the invention is characterized in that the command is a system call.

The database device according to the thirteenth invention defines and stores data used for a guideline, which is a list of candidate data referred to in order to set a recommended condition for a search condition input screen in the screen design unit. It is characterized by having a guideline definition section that

Further, the database apparatus according to the fourteenth invention is characterized in that the guideline defining section defines, as the candidate data, at least one of the actual data of the search target table and the data of the arbitrary table.

The database device according to the fifteenth invention is characterized in that the guideline defining section defines an annotation for the candidate data.

The database device according to the 16th aspect of the present invention is characterized in that the guideline defining section defines a font of a display character of data.

Further, the database device according to the seventeenth invention is characterized in that the guideline defining section defines a data highlighting method.

Further, the database apparatus according to the eighteenth invention is characterized in that the guideline defining section specifies a condition for further narrowing down the candidate data from the defined candidate data.

[0026]

BEST MODE FOR CARRYING OUT THE INVENTION

Embodiment 1. In this embodiment, the search condition input screen design and the search result display screen design in the screen design unit will be described below.

First, the drawings will be described. FIG. 1 is a system configuration diagram for realizing the database device according to the present invention. In FIG. 1, 1 is a database device, 2 is a CRT which 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 inputting conditions for searching a database. ,
And a screen design unit including a search result display screen design 3b for designing a display format for displaying the result of searching the database based on the search condition. Reference numeral 4 is a search unit for searching a database based on search conditions, 5 is a mouse, 6 is a keyboard, and 7 is a database storing a plurality of tables. In the database used in this embodiment, the structure of data is represented using a tree, and each element of the tree is represented using a node. A node has a hierarchical structure of a top node, an intermediate node, and an end node. A top node is a top node, and an end node is a node that has no other nodes below it. The node is an intermediate node. And, in the end node, the database table,
Alternatively, the views are in one-to-one correspondence. When searching, the type is narrowed down from the top node to the intermediate node, and by specifying the end node, the corresponding database table can be accessed. Further, the tree includes a shared tree and a user tree, and a tree that can be commonly used by users who use the system is called a shared tree. The shared tree is created by the system administrator. on the other hand,
What is personally created and used by a user is called a user tree.

FIG. 2 is a diagram showing tree information stored in the database and accessible by the user. FIG.
FIG. 3 is a diagram showing nodes stored in the tree information selected by the user from the tree information shown in FIG. 2. In FIG. 3, “parts information” indicates the top node, and “parts information” indicates “connector relay switch”.
To the "peripheral device", there is an intermediate node, and the intermediate node "IC" has a "bipolar IC (LS.
S) indicates that there is a terminal node of "MOS memory IC (DRAM)". FIG. 4 is a diagram showing a “screen” menu. The "screen" menu is a menu that is displayed by clicking "screen" in the menu bar of FIG.

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 the display position of each screen can be moved vertically and horizontally by using the scroll bar 13. . The search condition input screen setting 10 includes a switch 10a and an order 10b.
There are setting items of the field name 10c and the recommended condition definition 10d. The switch 10a sets whether to display the field in the search condition input window. When selected (when the square is displayed in black is selected), the field is displayed on the search condition input screen displayed when the search is executed. Order 10
b sets the order in which the field is displayed in the search condition input window. For the setting method, click in the square frame and enter the order by numbers, and the numbers are displayed from the top in order. The field name 10c displays a title (hereinafter referred to as a field name) that is given to the field of the table to be set so that the user can easily understand it. However, only the fields for which the user has the reference right are displayed. The table to be set is the table on which the search condition input screen is to be set, and 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 candidates for input conditions (recommended conditions) to be displayed in the drop-down list when inputting search conditions. A plurality of candidates can be specified, and input is performed by delimiting with “,” or “_”. When entering the recommended conditions, the guidelines set in the field can be used. If you click on the field name,
A list menu of candidate data or a window showing a range of data that can be set is displayed (FIG. 6 shows the list menu and window). When data is selected from the list of candidate data, the selected data is added to the recommended condition definition field.

Next, the search result display screen setting 11 will be described. Switch to the search result display screen setting 11
a, order 11b, field name 11c, sort order 11
There are setting items such as d, lift 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 another window (Fig. 7 shows a window display example). The sort order 11d specifies which field has priority in sorting when records are to be sorted and displayed in the search result display window. Click the frame of the sort order 11d in descending order of priority. To cancel the sort, click again. The lift 11e sets the sort type. Clicking on the ascending / descending column will switch between "ascending order" and "descending order". The processing designation 11f is designated when processing and outputting data when displaying the search result. Set the format for processing the search result in the processing specification frame. Refer to FIG. 8 for the method of designating processing. The display size 11g sets the number of display bytes of the field name.
Set the display byte count to a value that is greater than or equal to the length of the field name. If a value shorter than the field name is set, the display size is set according to 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, clicking the field name displays the size in another window (FIG. 7). Details of the action list 12 are omitted here because they will be described in detail in later embodiments.

FIG. 6 is a diagram showing an example of guidelines set in each field in inputting recommended conditions. FIG. 6A is a diagram showing an example of a numerical type / date type guideline. This guideline is, for example,
This is a guideline that indicates the range of data that can be set when the field name of the data type is numeric type / date type is clicked from the field name 10c of the search condition input screen setting 10 of, and the displayed data is the field. It is necessary to set each in advance. Users can refer to the guidelines when setting the recommended conditions. Further, FIG. 6B is a diagram showing an example of the guideline of the candidate data list. For example, the field name 10c in FIG.
It is a guideline that is displayed by clicking the "part name" in, and introduces a part of the actual data stored in the table "KP11P". When selecting data from these guidelines as a recommended condition for "part name", you can select it by placing the cursor on the data you want to select and clicking.

FIG. 7 is a diagram showing an example of a window displaying the field type and size. For example, in FIG.
By clicking "P / N part number", the type and size of the set field can be referred to as shown in FIG. FIG. 8 is a diagram illustrating a format of processing designation. 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 for the "$$" or "&&" part. For example, when the retrieval result is substituted for the processing designation of "total $$", the processing is processed as "total 100". Also, “&& × 100” is an example of calculation processing.
If "0.01" is input for the processing formula of "0.01
× 100 ”, and the search result is displayed as“ 1.0 ”. Further, when the processing designation type is money, if "MONEY" is designated in the format, a comma is inserted every three digits and displayed. In case of date, "DATE
If you specify "1" as the format, "year""month""day"
When / is inserted between and the format is "DATE2", "year", "month" and "day" are inserted between the data and displayed. FIG. 9 is a diagram showing a “setting” menu. The “setting” menu is a menu displayed when “setting” is clicked on the menu bar of the screen setting of FIG. FIG. 10 is a flowchart showing the procedure for setting the search condition input window and the search result display window.

Next, 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. 1 to 9 according to the flowchart of FIG. First, in order to select an end node to be searched, as shown in FIG.
The tree box at is displayed (S1). Note that the search condition input window can be set only for the end node, and if the user does not have the reference right to the information among the end nodes, the screen setting for the end node cannot be set. To do. Therefore, the tree displayed in the tree box in FIG. 2 is a tree for which the user has a reference right. Next, a tree to be searched is selected from the displayed tree box (S2).
In this embodiment, "part information" in the tree box displayed in FIG. 2 is selected as a search target by clicking. When a tree is selected, the 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 to display the screen setting window in Fig. 5. (S6). Then, the search condition input window and the search result display window are respectively set (S7).

First, the search condition input screen setting 10 shown in FIG. 5 is set as follows. First, the switch 10a is clicked to select the field name to be displayed on the search condition input screen when executing the search. According to FIG. 5, since the frame of the switching 10a is all black, the "P / N part number", "product code", "part name", "specification", and "part standard category 1" are selected. There is. Further, although not shown in FIG. 5, the scroll bar 13 is moved to select “manufacturer model name”, “DB registration date” and “part shape name” under “part standard category 1”. To do. next,
The order 10b to be displayed in the search condition input window is specified. 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 "," parts standard division 1 "has the order" 4 ", and although not shown in FIG. 5, the" maker model name "has the order" 6 "," DB registration date "
The order is "7", and the order "8" is specified for "part shape name". Finally, the recommended condition definition 10d is defined. Figure 5
According to the document, recommended conditions of "A, B, C" are defined in "Parts Standard Category 1". This is a condition for retrieving records in which the value of "parts standard category 1" is "A", "B", or "C". The above is the setting contents of the search condition input screen setting in the first embodiment.

Next, the search result display screen setting 11 of FIG. 5 is set as follows. First, the switch 11a is clicked to set the field name displayed in the search result display window. According to FIG. 5, "P / N part number", "part name", "specification", and "latest order date 1", although not shown in FIG. 5, the screen is scrolled by using the scroll bar 13, "Manufacturer model name" under "Parts 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 specified. According to FIG. 5, the “P / N part number” is the order “1”,
Order "2" for "part name", order "3" for "specification",
Further, although not shown in FIG. 5, 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 which field is to be prioritized in the search result display window is specified. 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 ascending / descending 11e is set, and the sort type of the sort order set previously is set to be ascending or descending. According to FIG. 5, "P / N part number" is "ascending order",
The "part name" is also set to "ascending order" and the "latest order date 1" is also set to "ascending order". Next, the processing designation 11f is set. Specify "DATE1" as the processing specification for "latest order date 1". This designation is a processing designation for separating the date with a slash (/). Next, the display size 11g is set. According to FIG. 5, "15" is added to the "P / N part number".
Is set, "20" is specified for "Part name", and "Specification" is set.
Is specified as "20". Further, although not shown in FIG. 5, "18" is designated for "maker model name" and nothing is designated for "latest order date 1". "Latest order date 1" does not specify the display size.
This is because the length of the data to be displayed is smaller than the length of the title, so there is no need to set it. The display size 11g is specified when the length of the data is longer than the number of display bytes of the field name as the title. The above is the setting contents of the search result display screen setting in the first embodiment.

As described above, after setting the search condition input window and the search result display window, click the "Set" button on the menu bar in FIG. Select "End save" from the setting menu of 9 to save the setting contents (S8). Save
In order to recognize that it is the search condition input setting and the search result display screen setting for the table name "KP11P",
The saved name is automatically assigned by the system. Further, the “user ID” is also used as a part of the saved name in order to distinguish the users. This completes the description of the search condition input screen setting and the search result display screen setting.

As described above, the search condition input screen setting and the search result display screen setting can be performed for each table prior to executing the search and registered for each table. Therefore, the table search can be designed separately from the execution. it can. Once designed, the same search condition and the same search result edit are performed each time the search is executed. Further, even when the setting is changed, the user only needs to customize the contents that have already been set, so that the setting is easier than making a new setting.

Embodiment 2. 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.

First, the drawings will be described. FIG. 11 is a flowchart showing a procedure for searching the table. 12
FIG. 14 is a diagram showing a “search” menu. FIG. 13 is a diagram showing a search condition input screen. In FIG. 13, 14 is an AND / OR, and after setting the search condition for one field, it specifies whether the relation with the condition set in the other field is the AND condition or the OR condition. It is a button for. For example, according to FIG. 13, the condition "* 74HC *" is set in the "manufacturer model name".
If the user clicks while "D" is displayed, the search condition for "maker model name" is an AND condition. Reference numeral 15 is a NOT button used when searching for data other than those that match the set conditions (a black frame is set if set), for example, the search condition “> =” specified in “DB registration date”. When the NOT button 15 is clicked after the condition "1900/01/01" is set, the setting is to search for data whose "DB registration date" is other than "> = 1900/01/01". 16 is the field name,
The field name set as the display target in the search condition input screen setting is displayed. When the field name 16 is clicked, when the guideline is designated, the input data candidates or the input data range (reference value) are displayed in the menu. Reference numeral 17 is 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, when the search condition column is clicked, a recommended condition list menu is displayed (see FIG. 18), and data is selected from the displayed recommended condition list menu. The selected data is added to the search condition 17. The recommended condition can be used as a search condition as it is, but it is also possible to customize it and create another condition. Reference numeral 18 is a storage of setting conditions. By clicking this button, the search conditions set in the window can be stored. A search condition name input window is displayed (see FIG. 19), and the user inputs the name from the keyboard 6. Reference numeral 19 is a search condition call. When the 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 the window. Reference numeral 20 denotes deletion of search conditions. By clicking this button, the search conditions selected from the search condition list 21 can be deleted. Reference numeral 21 is a search condition list in which a list of search condition names stored for the search target table is displayed. 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 referenced regardless of the field. FIG. 14 is a diagram showing a search result display screen. Based on the search conditions set in FIG. 13, the terminal node “MOS digital IC (C-MOS logic)” of the tree name “component information” is displayed.
Is displayed, and the search result is displayed based on the search result display screen setting made in the first embodiment.
According to FIG. 14, there are 174 records that meet the search condition.
There are 4 screens in total.

FIG. 15 is a diagram showing a search result output menu. This menu is displayed when "output" is selected from the menu bar in FIG. FIG. 16 is a diagram showing a screen for making settings for outputting search results 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. Output formats include text format and spreadsheet format. An example of the case of outputting in a spreadsheet format is shown in FIG. Also, in the output field specification, it is selected whether to output all the fields of the search target table or only the fields displayed in the window. Further, in the output record designation, either all records corresponding to the search condition are output, or a record to be output is selected from the search result display window and only that record is output.
FIG. 17 is a diagram showing a screen for making settings for outputting search results to a 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. The settings of "output field designation" and "output record designation" are the same as when outputting the output result to the file of FIG. 16 described above.

FIG. 18 is a diagram showing a screen displaying an example of the recommended conditions. In FIG. 18, “1829 × *”,
"* 1219 x 2438", "* 900 x 1800 M
“M” is registered as a recommended condition 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 it. Unlike the search condition list,
It is unique to the field and is displayed when you click the field name.

Next, the procedure for executing the search will be described with reference to the flowchart of FIG. In the flowchart of FIG. 11, the processing of S1 to S3 is the same as the processing 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, since the terminal node "MOS digital IC (C-MOS logic)" is searched, the terminal node is selected by clicking with the mouse. Then, "search" is selected from the menu bar of FIG. 3, and "search execution" is selected from the displayed "search" menu of FIG. When "Search execution" is selected, the tree display window shown in FIG. 3 disappears and the search condition input window of FIG. 13 is displayed (S10). A method of setting search conditions will be described with reference to FIG. According to FIG. 13, the search conditions are set for "maker model name" and "DB registration date". First, "maker model name" is clicked, and a wild card (*) is used to set a condition for searching for a record including "74HC" in the data of the manufacturer model name. next,
Set the search condition of "DB registration date", but before that, A
Click ND / OR14 and set the condition connection for "Manufacturer model name". In this example, AND / OR is used to search for records that satisfy both the search conditions set in "Maker model name" and "DB registration date".
Confirm that "AND" is displayed in 14. If a record satisfying any one of them is to be searched, it is confirmed that "OR" is displayed in AND / OR14 (if AND is displayed, click to change to "OR"). Then, the search condition is set to "DB registration date". According to FIG. 13, the condition "DB registration date" is "after January 1, 1990" (S11). After setting the conditions as described above, select "Search" in the menu bar and then click "Search".
From the menu (Fig. 12), click "Search". When "Search" is clicked, records corresponding to the search conditions are displayed in order as shown in FIG.
The search result displayed in FIG. 14 is 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 "latest order date 1" is set to "DATE1" in the processing designation 11f, the date is edited by dividing it by "/".

As described above, according to the first and second embodiments, the screen for inputting the search condition to be set when executing the search is the search condition input screen design 3a.
Since it is set in advance, it is possible to prevent the fields in which the search condition is not designated from being displayed, and the user can easily set the search condition. In addition, since recommended conditions can also be set, search conditions can be set using preset recommended conditions without entering new search conditions when performing a search, and errors in specified conditions due to input errors can be reduced. be able to.

Embodiment 3. In this embodiment, a database device that starts the next process based on the information stored in the action management table based on the result of the search in the first and second embodiments will be described below. I will explain.

First, the drawings will be described. FIG. 20 is a diagram showing the system configuration of the database device in this embodiment. In FIG. 20, reference numeral 50 is a process definition unit for defining and storing an executable process based on the search result by the search unit 4. Process definition part 5
0 includes an interactive definition support unit 50a, and the interactive definition support unit 50a can define processing 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 required for the process to be activated next. The command generation unit 52a generates the command. Other reference numerals in FIG. 20 are the same as those in FIG. 1 described in the first embodiment, and description thereof will be omitted.

FIG. 21 is a diagram showing a management tool. FIG. 22 is a flowchart showing the 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 the action setting. FIG. 25 is a diagram showing a screen for setting a table name in the action setting. FIG. 26 is a diagram showing a “list” menu. If you click "List" in the menu bar of the action management screen in Fig. 24,
This is the menu displayed. FIG. 27 is a screen for setting an action title. FIG. 28 is a diagram showing the “edit” menu. This menu is displayed when "Edit" is clicked on the menu bar of the action management screen of FIG. FIG. 29 is a diagram showing a script selection screen.

Next, the procedure for setting the definition information in the action management table will be described with reference to FIGS. 20 to 29 according to the flowchart of FIG. 21. Select "action management" from the management tool shown in FIG. 21 and click the "execute" button (S20, S21). When the action management is selected, the search type selection screen of FIG. 23 is displayed (S2
2). The search method of the 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 designated and part information is searched from a plurality of tables below the node. Also, "parameter search"
Specifies the terminal node and retrieves the component information from the table corresponding to the node. In this embodiment, the terminal node “M” which is the end node searched in the second embodiment is used.
In order to set the action to be started next based on the result of searching "OS digital IC", "parameter search" is selected from the search type selection screen of FIG. When "parameter search" is selected, the action management screen shown in FIG. 24 is displayed (S24). In FIG. 24, the tablespace name (database name) that includes the target table for activating an action is selected from the list of tablespace names displayed on the action management screen. In this embodiment, "PNDB" is selected. When the tablespace name is selected, the selected "PNDB" and the tablespace name are displayed on the left side of the tablespace name, as shown in FIG. Further, in order to register the target table for activating the action, click “List” in the menu bar of FIG. 25 to display the “List” menu in FIG. 26, and select “Table list” from the “List” menu. Is selected (S25), and the 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, set the title name of the action you are about to set. To create 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 relevant action from the displayed action list.
Then, the defined action information can be changed (S26).

When newly registering an action, the process shown in FIG.
When "Edit" in the menu bar of 7 is selected, "New registration" is selected from the edit menu shown in FIG. 28, and an action is newly registered (S27). When registering a new action, first set a script. The script is set on the script selection screen shown in FIG. 29, which is displayed by selecting "New registration" from the "Edit" menu. The script indicates an action type, and the database device according to the present invention has three scripts. The three scripts are "Display all fields", "Search other databases",
It is "command activation". What is "display all fields"?
It is a function that displays the values of all fields in the searched table. The record for which all the fields are displayed is executed for one record arbitrarily selected by the user from the records displayed on the search result display screen. "Other database search"
The user arbitrarily selects a record from the screen on which the search results are displayed, 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 another table to be searched (hereinafter, this relationship is referred to as a correlation). “Command activation” defines a command to be executed with the data of the record 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 select screen of FIG. 29, select one target script,
After inputting the title of the action, click the "execute" button (S28). When you click the "Execute" button, each setting window is displayed depending on the type of action. The user sets necessary definition information in the displayed setting window (S29, S3).
0, S31).

Next, a detailed setting method will be described according to the type of script set in S28. First, the setting of "display all fields" will be described. FIG. 30 is a flowchart showing the procedure for setting display of all fields. FIG. 31 is a screen for setting an action execution right.

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. Set the execution right on this screen and click "Execute" from the action menu (action menu is not shown) that appears when you select "Action" in the menu bar 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, and in this embodiment, the execution right A gives the execution right E. You can set the execution right by clicking the frame of the execution right you want to set. In FIG. 31, the execution rights A, B, and C indicate that the action can be executed (black frames indicate that the execution rights are set). The above is the method of setting the action for displaying all fields.

Next, the procedure for setting the action of "search for another database" 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 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.
FIG. 7 is a diagram showing a screen for setting a correlation. Fig. 36
FIG. 6 is a diagram showing a screen for setting execution rights.

Next, the procedure for setting an action for searching another database will be described with reference to the flowchart of FIG. In the setting of "search for other database", first, a table to be searched is set (S50). Setting of the table is performed by clicking the corresponding table space name and table name in the selection window of FIG. 34 which is displayed when the “target table” shown in FIG. 33 is clicked. In this embodiment, the selection window table space name “PNDB” and the table name “KATAMEIM” in FIG. 34 are used.
Click. The table space name and the table name that are clicked are displayed as "PND" as the "target table" in FIG.
B. "KATAMEIM" is displayed. Next, the field correlation is set (S51). From the correlation setting window of FIG. 35 that is displayed by clicking “Correlation setting” in FIG. 33, define the correspondence between the search result field and the field of the table of another database searched using the search result. To do. The method of setting is to select the field name displayed in the extraction side field list of FIG. 35 and the field name of the search result to be associated with the mouse and click “Set”. A plurality of correlations can be designated, and repeated setting is performed for the number of corresponding fields (S52). For example, in this embodiment, “PK_
PN ”and“ P_BUHI in the substitution side field list.
Select "N" and click "Set" to set the correlation. When "Set" is clicked, the set correlation "PK_PN → P_BUHIN" is displayed as shown in FIG. Next, set the access right to the action in the other database search action window. To set the access right, one of the execution right settings A to E shown in FIG. 36 is clicked. When this access right is set, the square frame of the execution right setting in FIG. 36 is changed from white display to black display. Fig. 36 after setting the access right
Click "Action" in the menu bar of, and select "Execute" from the displayed action menu to set the other database search action that has been set up to now in the table. The above is the procedure for setting the action for database search.

Next, the procedure for setting the action of "command activation" will be described. FIG. 37 is a flowchart showing the processing procedure for setting command activation. FIG. 38 shows
It is a figure which shows the screen which sets a script in action definition. FIG. 39 is a diagram showing a screen for setting arguments.

Next, the procedure for setting an action for command activation will be described with reference to the flowchart of FIG. First, a command script to be activated is input in the script field on the action creation screen of FIG. 38 (S60).
In the command script, a command for displaying the file in which the image data to be displayed when the action is activated is input. In this embodiment, a command "mtiff_sh" for displaying a file storing a parts catalog which is one of "MOS digital ICs" is specified. Next, the argument is set (S61). The argument is set by clicking the “argument setting” in FIG. 38 and displaying the field name that is the file name in which the image data is stored from the list of field names displayed in the argument setting window in FIG. Select. Since a plurality of fields can be set as an argument, the field names are selected in order and click “Set” (S62). In this embodiment, “K_
Select "PATH". After selecting, clicking “Set” in FIG. 39 displays the set arguments in the action creation screen in FIG. 38. Next, the access right to the action is set on the action creation screen of FIG. The setting of the access right is the same as the setting of the access right of the other database search described above. In this embodiment, access rights are set for execution rights A, B, and C.
After the access right is set, "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.

The action definition described above must be defined for each table. 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, and the process generation unit 52a.
Generates the required command and executes the action. The action management method will be described below.
In order to manage actions, a table management table (FIG. 40 (B)) that stores a table name and an action ID for a table in the database, and an action management table that manages a process derived from a database search result ( FIG. 40 (A)) is provided with the database device according to the present invention. In this database device, when the table is created, the action ID is numbered and the table name and the action ID are registered in the table management table. Further, for the action derived from the search result, the process definition unit 50 registers an attribute such as an action ID or a data transfer sequence to the action in the action management table. At this time, it is assumed that the actions for the same table are numbered with the same ID.

FIG. 40 shows an image of the record of the action management table and the table management table. The action definition information described above is registered in the action management table of FIG. The action title is "acttitl"
e "is set. And the script is "script
t ". "FIE" for all fields
"LD" is set, and in case of other database search, "DB
ACCESS ”, the command input to the script of FIG. 38 is set to“ script ”in the case of command activation. In this embodiment, "mtiff_sh" is set. Then, as for the correlation of the fields set in the case of the other database search, the arguments are set in "srcfids" and "dstfids". As for the correlation of the fields set in this embodiment, as shown in FIG. 41, the extraction side field name "PK_PN" is set in "srcfids" and the substitution side field name "P_BUHIN" is set in "dstfids". Is set. Further, in the case of command activation, as shown in FIG.
“K_PATH” is set in “rcfids”. 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 set. Then, when the action is started, if the started action is another database search, an 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.

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 following SQL is displayed.
The command generation unit 52a automatically generates a sentence. In addition, "fldA, f" is added to "scrfids" of the action management table.
ldB, fldC "is set, and" dstfld
It is assumed that "fld3, fld2, fld1" is stored in "s". select fld1, fld2, fld3 ...
from db_1. table_1 where fld3 = 'data1' and fld
2 = 123 andfld1 = '1994/12/1
2 '

If the activated action is command activation, a command for performing a system call such as vfork or system is issued to the command generation unit 52a.
Produces. For example, when the retrieval result as shown in FIG. 44 is displayed and the record at the top is selected and the action for command activation is activated, the following command is issued. In addition, "M" is added to "script" of the action management table.
“TIFF” is stored, and “fl” is stored in “srcflds”.
dA ”is stored. MTIFF tiff_data

As described above, by providing the action management table, it becomes possible to separate the definition of the process derived from the search result from the database system. If a user ID is provided in the action management table, the action definition for the table can be defined for each user.

Fourth Embodiment In this embodiment, an example of executing the action defined in the third embodiment based on the search result performed in the second embodiment will be described below. To start the action, do the following 3
There are two ways. The first is to select one action to execute from the action list as shown in FIG. 14, select one record from the records displayed as the search result, and select it from the menu bar. Click Take Action. The second is FIG.
Select one record from the search results as shown in, select one action to execute from the action list, and double-click. Thirdly, 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,
Double click The action can be activated by the above three methods.

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 of FIG. 14, "catalog display 1" which is a command activation is selected (S70). It is assumed that "P / N part number" is specified as the argument of "catalog display 1". Next, from the records displayed as the search results, click the record whose NO is "1" and click "Execute action" in the menu bar.
The “P / N part number” as shown in FIG. 46 is “KP41P
The catalog of parts of "200H06" is displayed (S7
1).

Next, the action activation for displaying all fields will be described. Select "Display all fields" from the action list shown in FIG. 14, select the record with NO "4" from the records displayed as the search result, and click "Execute action" on 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.

Next, execution of another database search will be described with reference to the flowchart of FIG. According to FIG. 48,
First, from the action list of FIG. 14, an action of another database search, “search for another database 1”.
Is selected (S80). "Other database search 1"
In the third embodiment, the set action title is the same action as the “quality information search”. Next, from the records displayed as the search result, the record to be input as the condition of the other database search is double-clicked (S81). Then, in the other database search action, a window for inquiring whether to set the search result display screen for displaying the result of the database search to be performed is displayed as shown in FIG. 49. Therefore, in response to the inquiry shown in FIG. 49, the user selects “Screen setting required” if screen setting is necessary, clicks “Execute”, and sets search conditions and search result display screen. To do. The field information of the selected record is entered in the displayed search condition input screen. When changing the displayed search conditions, the changed contents are set (S83), the search conditions are set (S84), and "search" on the menu bar is clicked to execute the search.

As described above, by defining the action in advance, it is possible to use it by simply selecting the process from the action list without creating a program for executing the action to be started next from the screen displaying the search result. The person can easily execute the process to be started next based on the search result.

Embodiment 5. In this embodiment, a method of changing the action definition information once defined will be described below.

FIG. 50 is a flow chart showing the procedure for changing the action activation information. According to FIG. 50, the action whose start 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.
Click and select "Change Action" from the edit menu shown in FIG. When “Change Action” is selected, the action creation screen of FIG. 33, the action creation screen of FIG. 38, and the action creation screen of FIG. 31 are displayed corresponding to the script type.
The displayed definition information is reset to the information to be changed (S92). The resetting method is the same as the method of setting each definition information described in the third embodiment, and the description thereof is omitted in this embodiment.

Next, the deletion of actions will be described. According to the flow chart showing the procedure for deleting actions in FIG. 51, the action to be deleted is selected from the action list in FIG. 27 (S100). Then, by clicking "Edit" on the menu bar, "Delete" is selected from the edit menu shown in FIG. When "Delete" is selected, a deletion confirmation window as shown in FIG. 51B is displayed (S101). To delete, click "Execute" to delete the action (S102).

When changing the title of an action, according to the flowchart showing the procedure for changing the title of the action shown in FIG. 52, the action whose title is to be changed is selected from the action list window shown in FIG. 27 (S11).
0). 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 title of the action (S112).

When setting a default action, from the action list window shown in FIG. 27,
The default action is selected (S120).
Then, "edit" is clicked and "default setting" is selected from the edit menu of FIG. 28 displayed.
When "default setting" is selected, the menu of FIG. 55 is displayed. When setting, select "setting" and click. To cancel the setting, click “Cancel setting” (S121). Then, a confirmation screen is displayed, so that "default" is set by clicking "execute" (S122). When "default setting" is selected from the edit menu, the confirmation screen of FIG. 56 (A) is displayed. Further, when “cancel setting” is selected, the setting cancellation confirmation screen of FIG. 56B is displayed. When the default is set, “*” is displayed in the default setting field of the action list window shown in FIG. The default setting is for setting an action that can be executed by clicking "execute action" on the title menu bar without selecting anything from the action list when executing the action. Actions for which default settings have been set are highlighted in the action list.

Next, the privilege change of the action will be described. According to the flow chart of the action privilege changing procedure of FIG. 57, the action for which the privilege is changed is selected from the action title list displayed on the action management screen of FIG. 27 (S130). Next, by clicking "Edit" on the title bar and selecting "Change Privilege" from the edit menu shown in FIG. 28 (S131).
When the "privilege change" is selected, the privilege change screen of FIG. 58 is displayed. Therefore, the changed privilege is set, and "execute" is clicked to change the access right (S132). Note that in FIG. 58, the setting of the execution right is a black square, indicating that there is an access right.

As described above, since it is possible to change even the action definition that has been performed once, even if the user sets a new action, the action definition information that has already been set is used to make the change. By doing so, it is possible to easily define a new action.

Sixth Embodiment In this embodiment, the setting of guidelines will be described. FIG. 59 shows
It is a system block diagram which implement | achieves the database apparatus in this invention. In FIG. 59, reference numeral 53 is a guideline defining section for defining and storing candidate data to be displayed by the screen designing section 3. Other reference numerals are the same as those in FIG. 1 described above. FIG. 60 is a screen for defining a guideline activated from “table management” of the management tool shown in FIG. Numerical type / Date type (NUMBER / DATE) as the data type in the search guideline 56
When is selected, a guideline as shown in FIG. 6A is displayed when the field name on the screen setting screen is clicked. Further, when “GROUP” is selected in the search guideline 56, the guideline as shown in FIG. 6B is displayed.

The guideline of the candidate data list in FIG. 6B shows a part of the data in the database to be searched, but when the database becomes large, it takes time to extract the data to be displayed. Requires. In such a case, it is possible to create a database in which only the data to be displayed in the guideline is registered and to design to display the data in that database. The setting method is shown in FIG. 6 when "MASTER" is selected in the search guideline 56 of FIG. 60 and the MASTER setting 57 is clicked.
On the MASTER setting screen of No. 1, the table space 58 for guideline, the table 59, and the setting value field 60 are designated. It is assumed that there are only seven types of candidate data displayed by clicking "part name" in the field name 10c of FIG. 5 and displayed in FIG. 6B, and the actual number of data is 100,000. . If you create a guideline database and set it to refer to the seven types of data registered in it, the time required to extract the data can be greatly reduced.

When the comment field 61 is designated on the MASTER setting screen shown in FIG. 61, the candidate data can be annotated. The comment field 61 is created in the same table as the table in which the guideline data is stored. FIG. 62 is a diagram showing an example of a guideline of a candidate data list with annotations. For example, it is a guideline that is displayed by clicking "parts standard category 1" in the field name 10c in FIG. 5, and the data of the guideline database corresponding to the recommended conditions of "parts standard category 1" is displayed. The set value 67 in FIG. 62 displays the candidate data of the recommended condition, and the comment 68 displays the annotation corresponding to the candidate data. As a recommended condition, when selecting data from these guidelines, you can select it by placing the cursor on the data or annotation you want to select and clicking.

FIG. 63 is a character attribute setting screen displayed when the character attribute setting 63 on the MASTER setting screen of FIG. 70 is clicked. In the font 65 of the character attribute setting screen, the font of the data displayed on the guideline can be specified.
When the character attribute setting screen is displayed, the data in the table designated on the MASTER setting screen is displayed as data 64. From this, select the data whose font you want to change, and press the button next to font 65 to select the font you want to set from the menu that appears. Fonts are "Mincho" and "Gothic"
There are four types: "bold" and "italic". FIG. 64 is a guideline displayed by clicking “Parts 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. 63.

In the character decoration 66 of the character attribute setting screen shown in FIG. 63, "underline", "overline" and "strikethrough" to be added to the data displayed in the guideline can be designated. From the data 64, select the data to which you want to add a character decoration, and click one of the "underline", "overline" and "strikethrough" buttons. To change the linetype or type, select the one you want to display from the linetype or type menu to the right of the clicked button. FIG. 65 is displayed by clicking "part standard division 1" in the field name 10c of FIG. 5 when "strikethrough" is set as the character decoration of the data "G" on the character attribute setting screen shown in FIG. It is a guideline.

Search conditions 62 on the MASTER setting screen shown in FIG.
If you want to further narrow down the data from the data in the guideline database and display it in the guideline, specify the narrowing condition. The condition specification format is the same as the search condition input in the search condition input screen described above. By designating the narrowing-down condition, it is possible to devise such as not displaying the data that the user does not want to set as the recommended condition on the guideline.

[0078]

As described above, according to the first aspect of the present invention, the screen design unit arbitrarily designs the search condition input screen for inputting the conditions for searching the data in the database. Therefore, in the conventional database search tool, the screen for entering the search condition is fixed, but by using the database device of the present invention, it is possible to design not to display unnecessary information for the user, and the search condition This has the effect of making it easy to input.

According to the second aspect of the invention, the screen designing unit further designs the search result display screen for displaying the search results. For this reason, it is possible to separately design the search result display screen for inputting search conditions and designating the display order and fields to be displayed, which makes it easier for the user to design and reduces the possibility of setting mistakes. There is.

Further, according to the third invention, the screen setting section selects an arbitrary field. Therefore, the user can easily specify the necessary fields when designing the search condition input screen and when designing the search result display screen, and the unnecessary fields are not displayed, which has the effect of reducing design mistakes due to input errors.

According to the fourth invention, the display order of the fields selected by the screen designing unit is designated. Therefore, the user can easily specify the display order when designing the search condition input screen and when designing the search result display screen. Further, since the order of fields displayed on the search condition input screen and the order of fields specified on the search result display screen can be specified in different orders, there is an effect that a user can provide a convenient database search environment.

According to the fifth aspect of the invention, the screen design unit presets the search condition. Therefore, 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 the condition rather than newly specifying the condition. is there. Also, if you customize this based on preset conditions and specify new conditions, you can easily specify conditions.
This has the effect of reducing mistakes in specifying conditions.

According to the sixth aspect, the screen designing unit specifies the display format. For this reason, it is possible to easily specify the display format such as comma edit, \ edit, and expansion of the display frame for the field selected for the search result display screen, making the search result easy to see and convenient for the user. It is effective in providing a good database search environment.

According to the seventh aspect of the 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 conventionally confirmed the search result, and the user again designated the process to be activated based on the result, but by using this database device, the process is activated next based on the search result. 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 an effect that the trouble of designating again can be eliminated and a convenient database search environment for the user can be provided.

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. To do. Therefore, even if there is a plurality of processes to be started next depending on the pattern of the search result, the database device according to the present invention can be easily used.

According to the ninth invention, the definition of the process in the seventh invention is defined by using the interactive definition support unit provided in the process definition unit. Therefore, there is an effect that the process to be activated next can be easily defined, and the process can be easily defined even for the first-time user.

According to the tenth invention, the process to be activated next, which has been defined in the seventh to ninth inventions, is stored as an action management table and is processed by the command correction unit provided in the process execution unit. , The definition information stored in the action management table is analyzed, and necessary commands are generated. Therefore, when the user defines the process to be started next, 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.

According to the eleventh invention, the tenth aspect described above is provided.
The command in the invention is a SQL command. Therefore, the database device according to the present invention can be used in the existing database and the system environment surrounding the database, and when a new database device is introduced, it can be realized at low cost.

According to the twelfth aspect, the above command is a system call. Therefore, the same effect as the eleventh aspect can be obtained.

In the thirteenth invention, by displaying the candidate data used as the search condition, the user can easily obtain the data which can be specified in the condition without knowing the data in the database. According to the fifth aspect of the invention, the conditions can be more easily specified, and the number of specified errors can be further reduced.

In addition, the fourteenth invention has an effect that a guideline having better operability can be provided by selecting candidate data from an arbitrary table.

Further, in the fifteenth invention, by adding a comment to the candidate data, the user can know the meaning of the symbolized value registered in the database in the operation of database search, and the value can be This has the effect of eliminating the need to separately investigate the meaning of.

Further, in the sixteenth invention, if the data of the guideline is classified by the font, the user can visually classify the data and it is easy to select.

In the seventeenth invention, the data can be classified by highlighting the data, and the same effect as the sixteenth invention can be obtained.

In the eighteenth aspect of the invention, the condition for narrowing down the candidate data is given, and the data that should not be selected is excluded from the candidate data, so that the user can easily select more appropriate data. is there.

[Brief description of drawings]

FIG. 1 is a system configuration diagram for realizing a database device 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 showing nodes stored in tree information according to 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.

FIG. 6 is a diagram showing guidelines for fields in inputting recommended conditions in the first embodiment.

FIG. 7 is a diagram showing field guidelines in the first embodiment.

FIG. 8 is a diagram showing a format of processing designation 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.

FIG. 14 is a diagram showing a search result display screen in the second embodiment.

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 according to the second embodiment.

FIG. 17 is a diagram showing a screen for designating output of search results to a printer in the second embodiment.

FIG. 18 is a diagram showing an example in which contents set as recommended conditions on the search condition input screen are displayed in the second embodiment.

FIG. 19 is a diagram showing a screen for saving the search conditions set in the second embodiment.

FIG. 20 is a system configuration diagram showing an example of a database device according to the present invention.

FIG. 21 is a diagram showing a management tool according to the third embodiment.

FIG. 22 is a flowchart showing a procedure for performing action definition 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 tablespace 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 designating an action title on the action management screen in the third embodiment.

FIG. 28 is a diagram showing an “edit” menu in 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 an execution right in the action creation screen in the third embodiment.

FIG. 32 is a flowchart showing a procedure for defining an action for searching another database in the third embodiment.

FIG. 33 is a diagram showing a screen for defining an action for searching another database in the third embodiment.

FIG. 34 is a diagram showing a list of table space names and a list of table names of databases to be searched in the third embodiment.

FIG. 35 is a diagram showing a screen on which a fetch side field list and a substitution side field list are displayed on a screen for setting a correlation in the third embodiment.

FIG. 36 is a diagram showing a screen for setting an execution right in the action creation screen according to the third embodiment.

FIG. 37 is a flowchart showing a procedure for defining a command activation action in the third embodiment.

FIG. 38 is a diagram showing a screen for setting a script on the action creation screen in the third embodiment.

FIG. 39 is a diagram showing a screen for setting arguments 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 the action management table for searching another database in the third embodiment.

42 is a diagram showing a search result in which the action of FIG. 41 is defined.

FIG. 43 is a diagram showing data in an action management table storing a command activation action definition in the third embodiment.

FIG. 44 is a diagram showing a search result in which the action of FIG. 43 is defined.

FIG. 45 is a diagram showing a procedure for 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 showing a result of activating an action for displaying all fields in the fourth embodiment.

FIG. 48 is a flowchart showing a procedure for activating an action of another database search in the fourth embodiment.

FIG. 49 is a diagram showing screen setting selection displayed when an action of another database search is executed in the fourth embodiment.

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.

FIG. 53 is a diagram showing a screen for changing a title in the fifth embodiment.

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 the privilege of an action in the fifth embodiment.

FIG. 58 is a diagram showing a screen for changing privileges in the fifth embodiment.

FIG. 59 is a system configuration diagram for realizing the database device according to the present invention.

FIG. 60 is a diagram showing a screen for defining a guideline according to 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 a guideline of a candidate data list with annotations in the sixth embodiment.

FIG. 63 is a diagram showing a character attribute setting screen according to the sixth embodiment.

[Fig. 64] 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.

[Fig. 67] Fig. 67 is a diagram illustrating an example in which search results are displayed on a screen in Conventional Example 1.

FIG. 68 is a diagram showing a screen for selecting a file to make an inquiry in Conventional Example 1.

FIG. 69 is a diagram showing a screen for defining an inquiry in Conventional Example 1.

[Fig. 70] Fig. 70 is a diagram showing, on a screen, the result of executing an inquiry in Conventional Example 1.

71 is a diagram showing a selection query in Conventional Example 2. FIG.

72 is a diagram for setting extraction conditions in Conventional Example 2. FIG.

FIG. 73 is a system configuration diagram of a database device in Conventional Example 4.

FIG. 74 is a diagram illustrating a flow of determining the result of a search and activating the next process in the conventional example.

[Explanation of symbols]

1 database device, 2 CRT, 3 screen design department,
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 lifting, 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 delete, 21
Search condition list, 50 processing definition section, 50a interactive definition support section, 51 action management table, 52 processing execution section, 52a command generation section, 53 guideline definition section, 54 setting content list, 55 selection field name, 5
6 Search guidelines, 58 tablespaces, 5
9 tables, 60 set value fields, 61 comment fields, 62 search conditions, 63 character attribute settings.

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Takashi Yamamoto 2-3, Marunouchi, Chiyoda-ku, Tokyo Sanryo Electric Co., Ltd. (72) Ryoji Igushi 2-3-2, Marunouchi, Chiyoda-ku, Tokyo 3 Ryoden Co., Ltd. (72) Inventor Shunsuke Mimura 2-3-3 Marunouchi, Chiyoda-ku, Tokyo Sanryo Denki Co., Ltd. (72) Yuka Ishikura 2-3-2 Marunouchi, Chiyoda-ku, Tokyo Sanryo Denki Incorporated (72) Inventor Hirohiko Mori 2-3-3 Marunouchi, Chiyoda-ku, Tokyo Sanryo Electric Co., Ltd.

Claims (18)

[Claims] 1. A database device having the following elements: (a) a database for storing data, (b) a screen design unit for arbitrarily designing a search condition input screen for inputting conditions for searching data in the database, (c) ) A search section for inputting search conditions using the search condition input screen of a predetermined format designed in the screen design section and searching for data. 2. The database device according to claim 1, wherein the screen designing unit further designs a search result display screen for displaying a search result searched by the searching unit. 3. The database device according to claim 1, wherein the screen designing unit selects an arbitrary field from fields constituting data. 4. The database device according to claim 3, wherein the screen designing unit specifies a display order of the selected fields. 5. The database device according to claim 3, wherein the screen designing unit presets search conditions that may be used in the field selected for the search condition input screen. 6. The database device according to claim 3, wherein the screen designing unit specifies a display format of a field selected for the search result display screen. 7. A database device comprising the following elements: (a) a database for storing data; (b) a search unit for searching the data in the database; (c) executable based on the search result of the search unit. A process definition unit that predefines and stores various processes, and (d) a process execution unit that executes the process defined by the process definition unit. 8. 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. The database device described. 9. The database device according to claim 7, wherein the process definition unit includes an interactive definition support unit that defines a process using an interactive interface. 10. 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 to generate a command required for the process. The database device according to claim 7, 8 or 9, further comprising a generation unit. 11. The database device according to claim 10, wherein the command is an SQL command. 12. The database device according to claim 10, wherein the command is a system call. 13. The database device includes a guideline defining section for defining and storing data used for a guideline, which is a list of candidate data to be referred to for setting a recommended condition for a search condition input screen in the screen designing unit. The database device according to claim 5, comprising: 14. The database device according to claim 13, wherein the guideline defining unit defines, as candidate data, at least one of actual data of a search target table and data of an arbitrary table. 15. The guideline defining unit defines an annotation for candidate data.
The database device described. 16. The guideline defining unit defines a font of a display character of data.
The database device described. 17. The database device according to claim 13, wherein the guideline defining unit defines a data highlighting method. 18. The database device according to claim 13, wherein the guideline defining unit specifies a condition for further narrowing down candidate data from the defined candidate data.