JP2000082065A - Data access device having history control function - Google Patents

Abstract

PROBLEM TO BE SOLVED: To facilitate the reference to an access history against a table which is linked among plural data bases and also to facilitate the redisplay of a table of the linking side by displaying an access history to a table contained in every data base based on the history information and displaying again the table of the linking side while controlling the history information. SOLUTION: A data base retrieval processing means (a WWW server part 902, etc.), refers to a data base information file when a table contained in a data base is accessed to detect a link set to a table of another data base and then accesses a table contained in a data base of the linked side that is designated by a relevant file. A history display means (a data base retrieval processing part 903, program to be executed by a WWW client 802) displays an access history to the display in every data base based on the history information. A redisplay means (the part 903, program to be executed by the client 802) displays again a table of an optional linking side while controlling the history information.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to a technique for centrally accessing data belonging to a plurality of database servers.

[0002]

2. Description of the Related Art With the development of network computing technology, a technique of storing a database in a server computer and accessing a database on the server computer from a client computer via a network has become general. In particular, by realizing an access interface from a client computer to a server computer by a web (WWW) interface, it is possible to easily connect to a database or the like from a browser application on the client computer. Has become easier to build.

[0003] As a data access system based on a network that can be constructed by a user himself,
WWW for accessing a specific database server
There is a known form that forms a base form on a WWW server on which software for processing a WWW request is installed.

[0004] Such a data access system is called W
It is assumed that the database accessed from the WW server exists on one server computer (database server).

[0005]

However, in a database such as a sales management database, it is often convenient to arrange a database for each office or store in terms of management. In this case, for example, it is necessary to construct a data access system that can access database servers distributed in each business office via a server at the head office.

As a data access system capable of accessing a plurality of database servers arranged in a distributed manner, a database access program with a unique interface is developed and constructed under a network environment using a dedicated client / server system and a dedicated line. Things are known.

Conventionally, however, it has been difficult for ordinary users to independently construct a WWW-based data access system that can access a plurality of database servers arranged in a distributed manner.

[0008] Further, it is more difficult to refer to the access history of the tables linked to each other and to return to the display of the link source table between a plurality of databases distributed and arranged on the network. Met.

An object of the present invention is to make it possible to easily refer to an access history of a table linked to each other among a plurality of databases arranged in a distributed manner and to redisplay a table of a link source.

[0010]

The present invention is based on a data access apparatus for accessing a table in a plurality of databases (databases 805) distributed on a network.

Data link information file definition means (WW
W server unit 902, form definition processing unit 905, and WWW
JAVA downloaded and executed by the browser 901
A applet program) is a network (LAN8
08, WAN 809), a link from a table to a table in another database is defined in a data link information file (data link information file 807) for each table in a plurality of databases distributed and arranged on the WAN.

Database search processing means (WWW server section 902, database search processing section 903, database processing section 904, and JAVA applet program downloaded and executed by WWW browser 901)
Detects a link to a table in another database by referring to the data link information file corresponding to the table when accessing the table in the database, and detects the link destination indicated by the data link information file. Access tables in the database.

A history information holding unit (a database search processing unit 903, a database search client program executed by the WWW client 802) holds history information of access to a table in each database.

History display means (database search processing unit 9)
03, the database search client program executed by the WWW client 802) displays the history of access to the tables in each database based on the history information.

Redisplay means (database search processing unit 90)
3. The database search client program executed by the WWW client 802) redisplays an arbitrary link source table while controlling the history information.

The present invention can be configured as a computer-readable recording medium for causing a computer to perform the same functions as the functions realized by the above-described configuration of the present invention when used by the computer. .

[0017]

Embodiments of the present invention will be described below in detail with reference to the drawings. In the embodiment of the present invention, for example, as shown in FIG. 1, a sales management table for each business unit is stored in the database server of the Tokyo head office site, and a product related to the business site is stored in the database server of the business A site. The sales management table and the sales slip table for each genre and product can be arranged in a distributed manner.

For example, a user in the site of the Tokyo head office connects to a WWW server in the site from a WWW client in the site, and further accesses a sales management table for each item in the database of the site from there. I do.

As a result, the user first enters the WWW browser of his / her own WWW client into FIG. 1 (a) and FIG.
You can display the sales by item as shown in
By drilling down one item A in the display by clicking the mouse with the mouse, it is possible to display the item-by-item sales according to the item as shown in FIGS. 1 (b) and 2 (b). it can. In this case, WWW in the Tokyo head office site
The server accesses the item-by-item sales management table in the database server of the site, and displays the item-by-item sales and the item-by-item sales on the WWW browser of the WWW client. The display method of each item at this time is determined by referring to a meta file called a specification file set in correspondence with the item-by-item sales management table in the database of the site.

Next, the user clicks on one of the establishments A in the display of the sales by the establishment by the item, and the genre by the item as shown in FIGS. 1 (c) and 2 (c). Another sales can be displayed. In this case, the WWW server in the Tokyo head office site refers to a meta-file called a data link information file set in correspondence with the item-by-item sales management table in the database of the site, thereby making the above-mentioned business. By recognizing that a link to the sales management table for each item, genre, and product in the database server of the A business site site is set at the place A (this is called a form link), and by accessing this, Tokyo is accessed. WWW of WWW client in head office site
The browser displays the item-specific genre-based sales.
The display method of each item at this time is determined by referring to the specification file set in correspondence with the item-by-item, genre-by-product, and product-by-product sales management table in the database of the establishment A site.

Next, the user clicks on one genre A in the display of the sales by item and genre by mouse to perform a digging, thereby obtaining the genre as shown in FIGS. 1 (d) and 2 (d). The sales of different products can be displayed.

Further, when the user mouse-clicks one product A in the display of sales by genre and product, a sales slip corresponding to the product A is displayed as shown in FIGS. 1 (e) and 2 (e). Can be displayed. In this case, the WWW server in the Tokyo head office site refers to the data link information file set corresponding to the item-by-item, genre-by-product, and product-by-product sales management table in the database of the site A currently accessed. By recognizing that the product A has a form link to the sales slip table in the database server of the A office site, by accessing it, the WWW browser of the WWW client on the site of the Tokyo head office is recognized. The sales slip is displayed. The display method of each item at this time is determined by referring to the specification file set corresponding to the sales slip supplement in the database of the A office site.

As described above, in the embodiment of the present invention,
Databases can be distributed and arranged at a plurality of sites, and a seamless connection can be made between the databases based on a specification file and a data link information file preset for each database. .

In this case, the user can freely establish the connection relationship between the databases and the display method by setting the specification file and the data link information file for each database.

In addition to the above-described basic operation, the embodiment of the present invention further provides the following access history reference function and link source table redisplay function. That is, for example, in addition to the display screen of item-by-item sales shown in FIG.
An execution state screen (1) as shown in the upper half table of the screen example in FIG. 3 can be displayed. The execution status screen shows that the server name of the currently accessed database server 804 is “DB server A” and the table data file name in the currently accessed database 805 is “sales management by item / business establishment”. And currently,
The user is informed that the values of the “item name” item and the “office name” item are not specified (they are blank).

Next, the user clicks on one item A in the lower half of the table in the screen example of FIG. 3 with a mouse to drill down and displays the sales by item and establishment shown in FIG. 2B. In addition to the above display screen, an execution state screen (2) as shown in the upper half table of the screen example in FIG. 4 can be displayed. This execution status screen indicates that the server name of the currently accessed database server 804 is “DB server A”, and that the currently accessed database 8
The table data file name in 05 is "sales management by item and establishment" and "item A" is currently specified as the "item name" item, and the value of the "office name" item is specified Is displayed to the user that it is not done (blank).

Subsequently, the user clicks one office A in the lower half of the table in the screen example of FIG. 4 with a mouse to link the form and displays the sales by item and genre shown in FIG. 2C. In addition to the display screen of FIG. 5, an execution state screen (3) as shown in the upper half table of the screen example of FIG. 5 can be displayed. The execution state screen is displayed by specifying “Office A” as the value of the “Office name” item in the execution state screen (2) shown in the upper half table of the screen example of FIG. With the execution state shown in (2) as the link source, the server name of the newly accessed link destination database server 804 is "D
B server B ", the table data file name of the link destination in the database 805 to be newly accessed is" sales management by product by genre by product ", and" item by product "in the newly accessed table. This indicates to the user that "item A" is specified as the "name" item, and that the values of the "genre name" item and the "product name" item are not specified (they are blank). In this case, a connection line with an arrow as shown in FIG. 5 is displayed between the table indicating the execution state of the link source and the table indicating the execution state of the link destination.

Further, when the user clicks on one genre A in the lower half of the table in the example of the screen in FIG. In addition to the screen, an execution state screen (4) as shown in the table in the upper half of the screen example of FIG. 6 can be displayed. This execution state screen further proceeds from the execution state screen (3) shown in FIG. 5, and displays to the user that "genre A" has been designated as the "genre name" item at the link destination.

Finally, the sales slip list display screen shown in FIG. 2E is displayed when the user clicks one product A in the lower half table of the screen example of FIG. In addition, an execution state screen (5) as shown in the table in the upper half of the screen example of FIG. 7 can be displayed. This execution state screen is displayed in the execution state screen (4) shown in the upper half table of the screen example of FIG.
By specifying “product A” as the value of the item,
With the execution state shown in the execution state screen (4) as a link source, the server name of the newly accessed link destination database server 804 is “DB server B” on the right side, and the newly accessed database It is displayed to the user that the table data file name of the link destination in 805 is “sales slip” and that “product A” is designated as the “product name” item in the newly accessed table. . Also in this case, a connection line with an arrow as shown in FIG. 7 is displayed between the table indicating the execution state of the link source and the table indicating the execution state of the link destination.

As described above, according to the embodiment of the present invention, not only a simple data display screen as shown in FIG.
The access history up to the present can be displayed as an execution state screen as shown in the upper half of each screen example in FIGS.

Further, in the embodiment of the present invention, as will be described later, an arbitrary link source table can be redisplayed by clicking a mouse on any displayed execution state screen.

The specific configuration and operation of the embodiment of the present invention for realizing the above operation will be described below. FIG. 8 is a system configuration diagram of the embodiment of the present invention.

The sites 801 such as #A, #B, etc.
They are connected by an AN (Wide Area Network) 809. Although only two sites 801 are connected in FIG. 8, a configuration in which more sites 801 are connected may of course be used.

One site 801 includes a database server 804, a WWW client 802, and a WWW server 8
03 is a LAN (local area network) 80
8 are connected.

The database server 804 manages a database 805 related to the site 801 and a specification file 806 and a data link information file 807 related thereto.

The WWW client 802 executes a WWW browser application operated by a user. The WWW server 803 is a WWW client 80
2 to control access to the database server 804 in its own site or another site.

FIG. 9 is a functional block diagram of the embodiment of the present invention. The database server 804 includes, in addition to the database 805, the specification file 806, and the data link information file 807 described in FIG.
Database processing unit 9 for logging in and accessing 5
04 and a logon management information file 906 holding information related to login by the database processing unit 904.
And a form definition processing unit 905 for managing the specification file 806 and the data link information file 807 and managing the form definition.

The WWW server 803 processes a request from the WWW browser 901 in the WWW client 802, and a WWW server unit 90.
Own site 801 or other site 80 according to instructions from 2
One database server 804 includes a database processing unit 904 and a database search processing unit 903 that accesses a form definition processing unit 905.

The database processing unit 904 in the database server 804 and the database search processing unit 903 in the WWW server 803 are connected to the WWW client 802.
Each time access from a user (the WWW browser 901 in FIG. 9) is authenticated, each process resides in the memory as one process.

Here, for example, the WWW server 803 of the site 801 (#B) functioning as the A business site accesses the database server 804 in the own site, and only the database 805 specialized for the own business site is accessed. A system can be constructed so that it can be managed. On the other hand, site 801 that functions as the Tokyo head office site
The (#A) WWW server 803 is a database server 804 in a site 801 (#B) that functions as an A office site in a format linked from the database 805 in the own site as well as the database server 804 in the own site. And so on, it is possible to construct a system so as to seamlessly access the database 805 distributed in each head office and office.

First, although not specifically shown, the user may select W
The table held in the database 805 in the database server 804 can be freely defined from the WWW browser 901 (FIG. 9) or the like in the WW client 802. This can be easily achieved with existing database construction tools.

FIG. 10 shows a database 805 in the database server 804 (#A) of the site 801 (#A).
FIG. 4 is a data configuration diagram of an item-by-item sales management table held in (#A), in which an item name item, a business item name item, and an amount item are defined. In this table, the aggregate data of each business establishment that should be compiled by the Tokyo head office is registered.

FIG. 11 shows a database 805 in the database server 804 (#B) of the site 801 (#B).
FIG. 9 is a data configuration diagram of an item-by-item, genre-by-product, sales management table held in (#B), in which an item name item, a genre name item, a product name item, and a price item are defined. FIG.
Is the database server 804 of the site 801 (#B)
FIG. 9 is a data configuration diagram of a sales slip table held in a database 805 (#B) in (#B), in which a slip No item, a date item, a person in charge item, a product name item, and an amount item are defined. Each table shown in FIG. 11 and FIG.
Data relating to establishment A corresponding to 1 (#B) is registered.

Although not particularly shown in FIGS. 8 and 9, for example, the database 805 in the database server 804 (#C) of the site 801 (#C) which is the site of the B office.
(#C) also holds the same sales management table for each item and genre as in FIG. 11, and the same sales slip table as in FIG. In each of these tables, data relating to the establishment B corresponding to the site 801 (#C) is registered.

FIG. 15 shows the database server 8 of the site 801 (#A) defined by the user via the WWW browser 901 (FIG. 9) in the WWW client 802.
FIG. 14 is a data configuration diagram of a specification file 806 of a sales management table for each item and each business held in 04 (#A). FIG.
6 is a data configuration diagram of the specification file 806 of the sales management table by item, genre, and product held in the database server 804 of #B or #C of the site 801 of #B or #C. FIG. 17 is a data configuration diagram of the sales slip table specification file 806 held in the #B or #C database server 804 of the #B or #C site 801.

The specification file 806 is stored in a corresponding table in the database 805 through the WWW server 803.
This is a meta file for specifying a display method of each item of the table when displayed on the WWW browser 901 (FIG. 9) in the WW client 802.

In the specification file name field of the specification file 806, the name of a corresponding table in the database 805 is specified. In the example of FIG. 15, “sales management by item and business establishment” is specified, in the example of FIG. 16, “sales management by product by genre by product” is specified, and in the example of FIG. 17, “sales slip” is specified. .

In the item name item of the specification file 806, the name of the item to be displayed when the corresponding table is displayed is specified. In the example of FIG. 15, each item of “item name”, “office name”, and “amount” is specified. In the example of FIG. 16, each item of “item name”, “genre name”, “product name”, and “amount” is specified. In the example of FIG. 17, each item of "slip No.", "date", "person in charge", "product name", and "amount" is designated.

In the data attribute item of the specification file 806, a display method of each item is specified. In the example of FIG. 15, the display method defined as “total level 1” is specified as the data attribute of the “item name” item. This “total level 1” is stored in a data link information file 8 described later.
07 (see FIG. 18), when a list of item names registered in the item-by-item sales management table is displayed, the item registered in the item name field of the table For each name, it is defined that the amounts registered in the amount item are totaled and displayed. Next, the "business name"
The display method defined as “total level 2” is specified as the data attribute of the item. In the “aggregation level 2”, when a list of the names of the offices belonging to the selected item name in the sales management table by item and office is displayed, each office name belonging to the selected item name in the table is displayed. Defines that the amounts registered in the amount item are displayed in total. In addition, the display of “data item 1” is designated as the data attribute of the “amount” item. This "data item 1"
This is the item name on the database 805 corresponding to the amount item (FIG. 10) of the sales management table for each item and each business in the database 805.

In the example of FIG. 16, the display method defined as “total level 1” is specified as the data attribute of the “item name” item. In this “aggregation level 1”, when a list of the item names registered in the item-specific genre-specific product-by-product sales management table is displayed, the amount item It is defined that the total amount registered in the is displayed. Next, a display method defined as “total level 2” is specified as the data attribute of the “genre name” item. In this “aggregation level 2”, when a list of genre names belonging to the selected item name in the item-by-item genre-by-product sales management table is displayed, for each genre name belonging to the selected item name in the table, In addition, it is defined that the amounts registered in the amount item are totalized and displayed. In addition, a display method defined as “total level 3” is specified as the data attribute of the “product name” item. In this “aggregation level 3”, when a list of product names belonging to the selected item name and genre name in the item-specific genre-specific product-by-product sales management table is displayed, the selected item name and genre name in the table are displayed. It is defined that the amounts registered in the amount item are totaled and displayed for each product name belonging to. Further, display of "data item 1" is designated as the data attribute of the "money" item. This “data item 1” is an amount item (FIG. 11, FIG.
Item names on the database 805 corresponding to 3).

In the example of FIG. 17, the display of "data items 1 to 5" is designated as each data attribute of each item of "slip No.", "date", "person in charge", "product name", and "amount". . These “data items 1 to 5” are stored in the database 8
Each item name on the database 805 corresponding to the slip No. item, date item, person in charge item, product name item, and money amount item (FIGS. 12 and 14) of the sales slip table in 05.

FIG. 18 shows the database server 8 of the site 801 (#A) defined by the user via the WWW browser 901 (FIG. 9) in the WWW client 802.
FIG. 14 is a data configuration diagram of a data link information file 807 of an item-by-item and business-by-business sales management table held in 04 (#A). FIG. 19 is a data configuration diagram of the data link information file 807 of the sales management table by item, genre, and product held in the database server 804 of #B or #C of the site 801 of #B or #C. Further, FIG.
6 is a data configuration diagram of a sales slip table data link information file 807 held in the #B or #C database server 804 of the #C site 801. FIG.

The data link information file 807 is a meta file for referring to the table in the database 805 in the other site 801 when a specific value of the corresponding table in the database 805 is selected.

In the data link information file 807, the name of the database server 804 corresponding to the file is specified in the server name item. In the example of FIG. 18, the name “DB server A” corresponding to the database server 804 (#A) is used, and in the examples of FIGS. 19 and 20, the name “DB server” corresponding to the database server 804 (#B) is used.
Server B "is specified.

In the data link information file name field of the data link information file 807, the name of the data link information file 807 is specified. In the aggregation level 1 item and the aggregation level 2 item of the data link information file 807, an aggregation method when they are specified as data attributes in the above-described specification file 806 is defined. In the example of FIG. 18, the aggregation level 1 is for each item name registered in the “item name” item, and the aggregation level 2 is for each business name registered in the “office name” item. In the example of FIG. 19, it is defined that the aggregation is performed. In the example of FIG. 19, the aggregation is performed for each item name registered in the “item name” item, and the aggregation level 2 is registered in the “genre name” item. Aggregation is defined for each genre name, and aggregation level 3 defines that aggregation is performed for each product name registered in the “product name” item.

The data items 1 to 5 of the data link information file 807 include the above-described specification file 8
The actual display item in the case where it is designated as a data attribute in 06 is defined. In the example of FIG. 18 and FIG. 19, the data item 1 is defined as the “money” item, and in the example of FIG. 20, the data items 1 to 5 are “slip No”, “date”, “person in charge”, “product”, respectively. It is defined that the items are "name" and "amount".

The link key 1 item and the link key 2 item of the data link information file 807 respectively include the first item name and the second item that are determined when a link is generated.
The second item name is specified. The number of items can be specified up to five. In the example of FIG. 18, the “office name” item is specified as one link key item, and the “item name” item is specified as two link key items. In the example of FIG. 19, the “product name” item is specified as one link key item. .

The link information item group of the data link information file 807 includes a link information item name,
Each item value of 2 (up to 5), a link destination server name, a link destination specification file name, and a link destination condition are specified. In the example of the link information item name “link information 1” in FIG. 18, when “business A” is designated as the link key 1 item and “item A” is designated as the link key 2 item, the link destination server Log in to the database server 804 (#B) corresponding to the name "DB server B", and the specification file 806 having the linked specification file name "sales management by item and genre and product" in the database 805 (#B) and the Reference is made to the sales management table for each product category and product in the corresponding database 805 (#B), and the data display is performed under the link destination condition that a record in which the value of the product name item is “product A” is extracted. Defined. In the example of the link information item name “link information 1” in FIG. 19, when “product A” is designated as the link key 1 item, the link destination server name “D
B server B "corresponding to the database server 804 (#
B) Log in to (the same server) and
5 (#B), the specification file 806 having the link specification file name “sales slip” and the corresponding sales slip table in the database 805 (#B) are referred to, and the value of the product name item is “product A”. Is defined to display data under a link destination condition that a record is extracted. In the example of FIG. 20, since there is no link from the sales slip table, only the name of each data item is described.

FIG. 21 shows the history information stored on the WWW client 802 (see FIG. 8) in order to perform the display control of the access history and the re-display control of the link source table described in FIGS. FIG. 21A is a diagram showing the contents of the memory, and FIG.
21 corresponds to the execution state screen (5) in FIG. 7, and FIG. 21 (b) corresponds to the execution state screen (3) in FIG.

First, the block number is a number corresponding to each of the tables shown in order from the left in the upper half of the screen example of FIGS. 7 and 5, and the access histories are numbered in chronological order.

The connection line information includes a connection source level number and a connection destination level number. The connection source level number is the number of the connection source level serving as a starting point for drawing connection lines with arrows shown in FIGS. The connection destination level number is a number of a connection destination level that is an end point for drawing the connection line.

When an item for which a totaling level is set is referred to in the specification file 806, the name of the totaling level (see FIG. 18 and the like) is stored. When it is referred to, the item name in the link destination condition set in the data link information file 807 is stored.

The level content stores the item value for which the totaling is performed when the item for which the totaling level is set is stored in the specification file 806, and stores the data when the item for which the totaling level is not set is referred to. The condition value in the link destination condition set in the link information file 807 is stored.

Next, the actual operation by the user will be described. FIG. 22 is an operation flowchart showing the overall operation of the user operation process. First, the user executes a specification file creation process using the WWW browser 901 (FIG. 9) in the WWW client 802 (step 2201). As a result, a specification file 806 having the data configuration shown in FIGS. 15 to 17 is created.

Next, the user executes a data link information file creation process using the WWW browser 901 (step 2202). As a result, the data link information file 8 having the data configuration shown in FIGS.
07 is created.

After that, via the WWW browser 901,
Search processing (step 2203), search result display processing (2
204), and the process of continuing the search (step 2205) is repeated.

FIG. 23 is an operation flowchart of the specification file creating process in step 2201 of FIG.
This operation flowchart is, for example, a case where the WWW browser 901 in the WWW client 802 is
3 is executed as a process of executing the JAVA applet program downloaded from the third program. The JAVA applet is a programming technology developed by Sun Microsystems, Inc. of the United States. FIG. 24 is a diagram showing an example of an operation screen of the WWW browser 901 in the specification file creation processing. Note that the following step 2301
Reference numerals 2309 to 2309 denote steps in the operation flowchart of FIG.

First, the user specifies on the WWW browser 901 whether to newly set the specification file 806 or edit the existing specification file 806 (step 2301).

In the case of new creation, step 2301
Is YES, a list of table data files in the database server 804 of the currently accessed site 801 is obtained and displayed on the WWW browser 901 as shown in FIG. The user selects one of the tabular data files to be displayed by clicking the mouse, and confirms by clicking the OK button with the mouse (step 2302).

On the other hand, if the user
When the editing of 06 is selected, it is not shown particularly,
A list of the specification files 806 in the database server 804 of the currently accessed site 801 is acquired and displayed on the WWW browser 901. The user selects one of the displayed specification files 806 by mouse clicking, and confirms by clicking the OK button with the mouse (step 2303).

Next, the user instructs the setting of the item (YES in step 2304). As a result, the user selects an arbitrary item from the list on the left side of the browser screen shown in FIG. An item to be output is selected (step 2305).

When the user presses the OK button shown in FIG. 24B, the selection result is recorded in the intermediate file on the WWW client 802 side (step 2306). When the user completes the setting of the items in steps 2304 to 2306 described above, the user instructs the setting of the aggregation level (NO in step 2304 and YES in step 2307). As a result, on the browser screen shown in FIG. 24 (c), for each display item selected by mouse click on the list on the left side, the user selects the aggregation level from the list on the right side by mouse click. To set the aggregation level of each display item (step 23).
08). As a default, a data item corresponding to each item is specified.

When the user presses the OK button shown in FIG. 24C, the selection result is recorded in the intermediate file on the WWW client 802 side (step 2306). When the user completes the setting of the items and the setting of the aggregation level in steps 2304 to 2308 described above, the WWW client 8 sends the WWW client 8 to the database server 804 in the site 801 currently being accessed from the WWW client 802.
The intermediate file on the 02 side is transmitted, and after the user specifies the file name, the intermediate file is registered in the database server 804 as a specification file 806 (step 2309).

FIG. 25 is an operation flowchart of the data link information file creation processing in step 2202 of FIG. This operation flowchart is realized, for example, as processing in which the WWW browser 901 in the WWW client 802 executes the JAVA applet program downloaded from the WWW server 803. FIG.
6 is WW in the data link information file creation processing
FIG. 7 is a diagram illustrating an example of an operation screen of a W browser 901. In addition,
The following steps 2501 to 2507 are respectively performed in FIG.
In the operation flowchart of FIG.

First, a list of the specification files 806 registered in the database server 804 of the site 801 currently accessing the WWW browser 901 is displayed, and the user designates one of them by clicking the mouse. .

Next, the user instructs to select a link key (YES in step 2502). As a result,
On the browser screen shown in FIG. 26 (a), the user selects the spec file 8 currently selected from the upper half table.
An arbitrary item in the table corresponding to 06 is selected by clicking the mouse (step 2503). As a result, the display names corresponding to the selected items are sequentially displayed from the key 1 in the lower half table on the browser screen shown in FIG.

Subsequently, the user sequentially sets the content value for each key in the lower half table of the browser screen shown in FIG. 26A (the determination in step 2504 is YES →
Step 2505).

Further, the user selects one of the key value combinations set in the lower half table of the browser screen shown in FIG. 26 (a) with a mouse click, and clicks the "link information" button with the mouse. As a result, the browser screen changes as shown in FIG. 26 (b), and the user displays on this screen the contents of the link destination corresponding to the selected combination of key values in the link information (FIGS. 18 to 20). (See step 2506: YES → step 2507). Here, the user selects a link destination server name and a specification file name from each displayed list, and specifies a link destination condition by text input.

Thereafter, the user finishes the setting of the data link information file 807 by clicking the OK button on the browser screen shown in FIG. 26B (NO in steps 2502, 2504, and 2506). ).

FIGS. 27 to 29 show the WWW client 8.
22 is an operation flowchart of a search process executed by a database search processing unit 903 (FIG. 9) in the WWW server 803 in response to the search process of FIG.

Prior to this, first, logon from the WWW client 802 to the WWW server 803 and the database server 804 is executed. The logon sequence is shown by the operation sequence diagram of FIG.

First, the WW in the WWW client 802
On the W browser 901, the user
When RL (uniform resource locator) is specified,
The WWW server unit 902 in the WWW server 803 is WWW
The browser 901 displays a user name and password input form. On the other hand, when the user inputs a user name and a password, the information is stored in the WWW server 803.
It is sent to the WWW server unit 902 in the inside (sequence 3001 in FIG. 30).

The WWW server section 9 in the WWW server 803
02 sends the received user name and password to the database server 804 (DB server A) accessed by default (sequence 3002 in FIG. 30).

As shown in FIG. 31, the database processing unit 904 in the database server 804 stores a logon management information file 906 holding a user name, a password, a logon ID, additional logon management information (name, contact information, etc.). Is managing. Then, the database processing unit 904 operates the WWW server unit 9 in the WWW server 803.
02 is compared with the information on the logon management information file 906. If the collation result is OK, the database processing unit 904 in the database server 804 (#A)
Information indicating approval together with the logon ID of the entry on the logon management information file 906 that has been collated is returned to the WW server unit 902 (sequence 3003 in FIG. 30).

The WWW server unit 902 stores one database search processing unit 90 in accordance with the returned logon ID.
Process 3 is started, and information indicating approval together with the logon ID is returned to the WWW browser 901 in the WWW client 802 (sequence 3004 in FIG. 30).

Thereafter, the WWW client 802 W
The WWW browser 901 uses the logon ID received from the WWW server 803 to use the database server 804
(DB server A). That is,
When the WWW browser 901 issues a data search instruction together with the logon ID (sequence 3005), the WWW server unit 902 passes the data search instruction to the database search processing unit 903 corresponding to the logon ID via the WWW server unit 902. The processing unit 903 generates an SQL (structured search language) statement corresponding to the instruction,
The L sentence is transmitted to the database processing unit 904 in the database server 804 (DB server A), and the processing unit 904 executes a search for the database 805 (sequence 3006). After the search result for the SQL statement is returned from the database processing unit 904 to the database search processing unit 903 corresponding to the logon ID (sequence 3007), the database search processing unit 903 sends the search result to the WW.
Returned to W browser 901 (sequence 3008).
Details of the operation of the database search processing unit 903 in the WWW server 803 in this series of search processing are shown below.
It is an operation | movement flowchart shown in FIG.

The following steps 2701 to 2716 are the respective steps in the operation flowchart of FIG. First, the database search processing unit 903 determines whether the instruction from the WWW browser 901 is an initial display instruction (step 2701).

If the instruction is an initial display instruction, the database search processing unit 903 is specified from the WWW browser 901 via the form definition processing unit 905 in the database server 804 (DB server A) accessed by default. The specification file 806 is obtained, and a table data file in the database 805 in the database server 804 (DB server A) is opened based on the specification file name (see FIG. 15 and the like) (step 2702).

Next, the database search processing unit 903
By referring to the specification file 806, it is determined whether or not the aggregation level is set for the item for which the initial display is instructed (see step 2703, FIG. 15 and the like).

If the aggregation level (= aggregation level 1) is set for the initial display item, the database search processing unit 903 sequentially sends the SQL statement to the database processing unit 904 in the database server 804 (DB server A). By issuing, the value of the money amount item is totaled for each item value of the item of the totaling level 1 (step 2704).

The database search processing unit 903 also
The WWW client 802 instructs the database search client program executed by the JAVA applet or the like to create an execution status screen (step 2705). As a result, the program creates history information (see FIG. 21) corresponding to the aggregation level 1 in the memory of the WWW client 802, and the WWW browser 90
An execution status screen as shown in the upper half of the screen example of FIG. 3 is displayed on the first screen.

Then, the database search processing unit 903
Is a WWW browser 90 in the WWW client 802.
1 and transmits the search / aggregation result (step 270).
6). As a result, item-by-item sales are displayed on the WWW browser 901, for example, as shown in the lower half of the screen example in FIG. 3.

On the other hand, if the totaling level is not set for the initial display item, the database search processing section 9
03 issues a SQL statement instructing the database processing unit 904 in the database server 804 (DB server A) to search for a simple data item to perform a search (step 2).
706).

Also, as in the case of step 2705,
The database search processing unit 903 instructs the database search client program executed by the WWW client 802 to create an execution status screen (step 2707).

Then, the database search processing unit 903
Transmits the search / aggregation result obtained from the database processing unit 904 to the WWW browser 901 in the WWW client 802 (step 2706).

Next, in the display of item-by-item sales on the WWW browser 901 in the lower half of the screen example of FIG. 3, for example, the user clicks on one item A in the display to drill down (drill down). ), The determination in step 2701 is NO and the determination in step 2709 is YES in the database search processing unit 903.

As a result, the database search processing unit 903
Sequentially issues SQL statements to the database processing unit 904 in the database server 804 (DB server A), thereby acquiring the contents of the specified row using the contents of the aggregation level for which the drilling is specified as an extraction condition. (Step 2710).

Subsequently, the database search processing unit 903
Determines whether there is a specified lower aggregation level (step 2711). In the case of drilling down, this determination is YES, and the database search processing unit 903 totals the value of the money amount item for each item value of the item of the aggregation level next to the aggregation level to be drilled down (step 2712).

The database search processing unit 903 also
The database search client program executed by the WWW client 802 is instructed to add the contents of the specified line to the current execution state screen (step 2713). As a result, the program is
The content corresponding to the in-depth aggregation level is added to the history information in the memory of the client 802, and an execution state screen as shown in the upper half of the screen example of FIG. 4 is displayed on the screen of the WWW browser 901.

Then, the database search processing unit 903
Is a WWW browser 90 in the WWW client 802.
1 and transmits the search / aggregation result (step 270).
6). As a result, the WWW browser 901 displays, for example, item-by-item sales for each item, as shown in the lower half of FIG.

Conversely, in the display of item-by-item sales on the WWW browser 901, for example, shown in the lower half of FIG. Then, in the database search processing unit 903, the determination in step 2701 is NO, the determination in step 2709 is NO, and the determination in step 2714 is YES.

As a result, the database search processing unit 903
, The SQL statement is sequentially issued to the database processing unit 904 in the database server 804 (DB server A), and the value of the money amount item is totaled for each item value of the data item in the item of the totaling level after excavation ( Step 271
5).

The database search processing unit 903 also
The database search client program executed by the WWW client 802 is instructed to delete the state contents of the higher total level corresponding to the excavation in the current execution state screen (step 2716). Further, the database search processing unit 903 is configured to
The search / aggregation result is transmitted to the WWW browser 901 in Step 2 (Step 2706). As a result, the program updates the history information in the memory of the WWW client 802, and returns the screen display of the WWW browser 901 from the screen example of FIG. 4 to the screen example of FIG.

If the excavation occurs at the highest level, there is no higher level, so the database search processing unit 903 executes step 2714.
Is NO, and no processing is performed.

Subsequently, a database search process is performed by clicking on one establishment A on the user WWW browser 901 in which, for example, sales by item and establishment is displayed in the lower half of the screen example of FIG. In the unit 903, the determination in Step 2701 is NO, and Step 2709
Is YES, the determination in step 2711 is NO, and form link display processing is executed (see also the sequence 3009 in FIG. 30).

FIG. 28 is an operation flowchart of a form link display process. The following steps 2801 to 281
4 are the respective steps of the operation flowchart of FIG.

First, the database search processing unit 903
Database server 804 accessed by default
(DB server A) via the form definition processing unit 905
The designated data link information file 807 is opened (step 2801).

Next, the database search processing unit 903
It is determined whether the value of the link key specified by the user matches (step 2802). For example, when the user selects one establishment A in the display of item-by-item sales for item A, the set of the link key values of the establishment A and the item A is, for example, the data shown in FIG. It is determined whether or not the value matches the pair of the link keys 1 and 2 in each content of the link information in the link information file 807.

If the link keys do not match, the process ends as it is (NO in step 2802). If the link keys match, the database search processing unit 903
Issues an instruction to the database search client program executed by the WWW client 802 to add the contents of the specified line to the current execution state screen (step 2803). As a result, the program
The content corresponding to the aggregation level linked to the form is added to the history information on the memory of the WW client 802, and
An execution state screen is displayed on the screen of the W browser 901 as shown in the table on the left side of the upper half of the screen example in FIG.

Next, the database search processing unit 903
Database server 8 accessed by default
The log-off is notified to the database processing unit 904 in the server 04 (DB server A) (step 2804, FIG. 30).
Sequence 3010).

Next, the database search processing unit 903
From the link information in the data link information file 807 where the link keys match, a parameter of the link destination server name (see FIG. 18 and the like) is obtained (step 2805).

Subsequently, the database search processing unit 903
Executes logon to the database server 804 (DB server B) corresponding to the acquired link destination server name (step 2806, sequence 3011 in FIG. 30).
The user name and password in this case are, for example, those when the user logs on to the first database server 804 (DB server A).

The database processing unit 904 in the database server 804 (DB server B) corresponding to the link destination server name stores the link destination user name and the link destination password with the information in the logon management information file 906 in the own server. Collate. If the collation result is OK, the database processing unit 904 returns information indicating approval to the database search processing unit 903 in the requesting WWW server 803 (sequence 3012 in FIG. 30).

Next, the database search processing unit 903
The link specification file name (see FIG. 18 and the like) is acquired from the link information in the data link information file 807 whose link key matches, and the form definition processing unit in the database server 804 (DB server B) of the other site is obtained. 90
5, the specification file 806 corresponding to the acquired link destination specification file name is opened (step 2).
807).

Subsequently, the database search processing unit 903
Acquires the link destination condition (see FIG. 18 and the like) from the link information in the data link information file 807 whose link key matches, and sets the condition in the SQL statement at the time of the search.

Next, the database search processing unit 903
By referring to the specification file 806 obtained from the database server 804 (DB server B) of the other site, it is determined whether or not the aggregation level is set for the item instructed to display the form link (step). 2809).

If the aggregation level is not set for the display item of the form link, the database search processing unit 903 sets the database server 804 of the other site to the above.
An SQL statement for instructing a search for a data item is issued to the database processing unit 904 in (DB server B) together with the extraction condition set in step 2808 (step 2810,
A sequence 3013 in FIG. 30).

Further, the database search processing unit 903
The database search client program executed on the WWW client 802 is instructed to add a new execution status screen (step 2811).

Then, the database search processing unit 903
Transmits the search / aggregation result obtained from the database processing unit 904 to the WWW browser 901 in the WWW client 802 (step 2814, sequences 3014 and 3015 in FIG. 30).

On the other hand, if the aggregation level is set for the display item of the form link, the database search processing unit 903 sends the database server 804 of the other site.
By sequentially issuing SQL statements to the database processing unit 904 in (DB server B), the value of the money amount item is totaled for each item value of the item of the totaling level (step 281).
2. Sequence 3013 in FIG.

Also, as in the case of step 2705,
The database search processing unit 903 instructs the database search client program executed by the WWW client 802 to create a new execution status screen (step 2813). As a result, the program
New history information is created on the memory of the WWW client 802, and an execution state screen as shown in the table on the right side of the upper half of the screen example in FIG. 5 is displayed on the screen of the WWW browser 901.

Then, the database search processing unit 903
Transmits the search / aggregation result obtained from the database processing unit 904 to the WWW browser 901 in the WWW client 802 (step 2814, sequences 3014 and 3015 in FIG. 30). As a result, the WWW browser 901 displays, for example, sales by item, by genre, and by product, as shown in the lower half of the screen example in FIG.

Hereinafter, the drilling down from the execution state screen of FIG. 5 to the execution state screen of FIG. 6 is realized by the control processing of the operation flowchart of FIG. 27, and the form link to the execution state screen of FIG. 6 to FIG. This is realized by control processing.

Finally, when the user enters the WWW client 80
When logoff is performed from the WWW browser 901 of No.2,
Database search processing unit 903 in WWW server 803
Through the database server 804 of the other site
(DB server B) is notified of logoff (sequences 3016 and 3017 in FIG. 30).

Next, a database search process when the user designates a jump to an arbitrary higher aggregation level by mouse click or the like on the execution state screen (5) shown in the upper half of the screen example of FIG. 7, for example. The processing of the unit 903 will be described with reference to the operation flowchart of FIG.

The following steps 2901 to 2905
Are the respective steps of the operation flowchart of FIG. First, the determination in step 2901 is YES. If the user clicks the mouse to jump to a lower totalization level on the execution status screen, the database search processing unit 903 terminates the processing and does not perform any processing (the determination in step 2901 is made). NO).

After the determination in step 2901 becomes YES, the database search processing unit 903 sends a request to the database search client program executed by the WWW client 802 to the execution status screen on the right side of the specified execution status screen. An instruction to delete the connection line is issued (step 2902).

Next, the database search processing unit 903
It instructs the database search client program executed by the WWW client 802 to delete the lower-level state contents of the specified execution state screen (step 2903).

Subsequently, the database search processing unit 903
Sequentially issues SQL statements to the database processing unit 904 in the database server 804 set in the designated execution state screen, thereby setting the level of the designated execution state screen for each item value of the data item. The values of the money amount items are totaled (step 2904).

The database search processing unit 903
Is a WWW browser 90 in the WWW client 802.
1 and transmits the search / aggregation result (step 290).
5). As a result, the database search client program running on the WWW client 802 is
The history information on the memory of the WWW client 802 is updated, and the screen display of the WWW browser 901 is returned from, for example, the display of the screen example of FIG. 7 to the display of the screen example of FIG.

As described above, in the embodiment of the present invention, the display of the access history and the redisplay of an arbitrary link source table can be freely controlled. Note that the present invention may be configured as a computer-readable recording medium for causing a computer to perform the same function as the function realized by each of the above-described embodiments of the present invention when used by a server computer. Can also. In this case, a program for realizing various functions of the embodiment of the present invention via a portable recording medium such as a floppy disk, a CD-ROM disk, an optical disk, a removable hard disk, or a network line is stored in a memory in the server computer. (RAM or hard disk, etc.) and executed.

[0132]

According to the present invention, databases can be distributed and arranged at a plurality of sites, and a seamless connection can be established between the databases based on a data link information file preset for each database. Can be performed, and it is possible to freely control the access history reference to the tables linked to each other among a plurality of distributed databases and the redisplay of the link source table.

[Brief description of the drawings]

FIG. 1 is a diagram illustrating the principle of the present invention.

FIG. 2 is a screen transition diagram according to the embodiment of the present invention.

FIG. 3 is an execution state screen (1).

FIG. 4 is an execution state screen (2).

FIG. 5 is an execution state screen (3).

FIG. 6 is an execution state screen (4).

FIG. 7 is an execution state screen (5).

FIG. 8 is a system configuration diagram of the embodiment of the present invention.

FIG. 9 is a functional configuration diagram of the embodiment of the present invention.

FIG. 10 is a data configuration diagram of a sales management table for each item and office in a database 805 (#A) (Tokyo head office).

FIG. 11 is a data configuration diagram of a product-by-item, genre, and product-by-product sales management table in a database 805 (#B) (Office A).

FIG. 12 is a data configuration diagram of a sales slip table in a database 805 (#B) (Office A).

FIG. 13 is a data configuration diagram of a product-by-item, genre, and product-by-product sales management table in the database 805 (#C) (Office B).

FIG. 14 is a data configuration diagram of a sales slip table in a database 805 (#C) (Office B).

FIG. 15 is a data configuration diagram of a specification file of a sales management table for each item and for each business establishment.

FIG. 16 is a data configuration diagram of a specification file of a sales management table for each item, each genre, and each product.

FIG. 17 is a data configuration diagram of a specification file of a sales slip table.

FIG. 18 is a data configuration diagram of a data link information file of a sales management table for each item and business.

FIG. 19 is a data configuration diagram of a data link information file of a sales management table for each item, each genre, and each product.

FIG. 20 is a data configuration diagram of a data link information file of a sales slip table.

FIG. 21 is a diagram showing memory contents of history information.

FIG. 22 is an operation flowchart of a user operation process.

FIG. 23 is an operation flowchart of a specification file creation process.

FIG. 24 is a diagram illustrating an example of an operation screen of a specification file creation process.

FIG. 25 is an operation flowchart of a data link information file creation process.

FIG. 26 is a diagram illustrating an example of an operation screen of a data link information file creation process.

FIG. 27 is an operation flowchart of a search process.

FIG. 28 is an operation flowchart of a form link display process.

FIG. 29 is an operation flowchart of a moving process from an execution state screen.

FIG. 30 is an operation sequence diagram at the time of search processing.

FIG. 31 is a data configuration diagram of a logon management information file.

[Explanation of symbols]

 801 site 802 WWW client 803 WWW server 804 database server 805 database 806 Spec file 807 Data link information file 808 LAN 809 WAN 901 WWW browser 902 WWW server section 903 Database search processing section 904 Database processing section 905 Report definition processing section 906 File

Claims (2)

[Claims] 1. A data access device for accessing a table in a plurality of databases distributed on a network, wherein each table in the plurality of databases distributed on the network is used to access another table from the table. A data link information file defining means for defining a link to a table in a database in a data link information file; and, when accessing a table in the database, referencing a data link information file corresponding to the table to allow access to another database. Database search processing means for detecting a link to a table in the database and accessing a table in a database at a link destination specified by the data link information file; and holding history information of access to the table in each database. History information holding means, based on the history information, A history display means for displaying a history of access to the table; and a redisplay means for redisplaying an arbitrary link source table while controlling the history information. Data access device. 2. A recording medium for recording a program read by the computer when used by a computer, wherein each table in a plurality of databases distributed on a network is read from the table and stored in another database. A data link information file definition function for defining a link to a table in a data link information file; and a table in another database by referring to a data link information file corresponding to the table when accessing the table in the database. A database search processing function of detecting a link to a database and accessing a table in a database of a link destination specified by the data link information file; and holding history information for storing history information of access to a table in each database. A function and a table in each database based on the history information. A history display function of displaying the access history of the user; a redisplay function of redisplaying an arbitrary link source table while controlling the history information; and a computer readable recording of a program for causing the computer to perform recoding media.