JP4034377B2 - Database design device and database control device - Google Patents

Description

図９の（ｂ）は、サーバ配置（配置：Ｓ）の例を示す。ここでは、図示の下記のように設定する。
【００７４】

次に、図１０ないし図１２を用いてコード参照について詳細に説明する。
【００７５】
図１０は、本発明のＦＯＲＭ作成、入出力情報定義の説明図を示す。
図１０の（ａ）は、ＦＯＲＭ作成フローチャートを示す。
図１０の（ａ）において、Ｓ５１は、ＦＯＲＭに項目レイアウトを入力する。これは、図１０の（ｂ）に示す項目レイアウトを画面上から入力する。
【００７６】
Ｓ５２は、ＦＯＲＭの各項目ＴＡＧ（タグ）に項目ディクショナリ内英数項目名を選択入力する。これは、既述した図５の（ａ）の項目ディクショナリ１１内の英数項目名を選択入力する。例えば図１０の（ｂ）に示す、処理区分の▲３▼ＴＡＧとして、図５の（ａ）の項目ディクショナリ１１内の対応する英数項目名“ＳＹＲＫＢＮ”を選択入力する。同様に他のものを選択入力する。
【００７７】
Ｓ５３は、入出力情報定義を選択入力する。これは、図１０の（ｃ）の入出力情報定義５６に示すように、ＴＡＧに対応づけて図示のように、項目ディクショナリ１１およびコード一覧２１からそれぞれ該当するものを選択入力する。
【００７８】
以上の手順によって、図１０の（ｂ）のＦＯＲＭのレイアウト例の場合に、図１０の（ｃ）の入出力情報定義５６が生成されることとなる。
図１０の（ｂ）は、ＦＯＲＭ例を示す。これは、ＦＯＲＭに項目レイアウト（処理区分、商品コード）を行った例である。そして、各ＴＡＧに対応づけて図示のように英数項目名を図５の（ａ）の項目ディクショナリ１１が取り出す。
【００７９】
図１０の（ｃ）は、入出力情報定義の例を示す。入出力情報定義５６は、ＴＡＧに対応づけて、項目名、属性、桁数、コードを登録したものである。
次に、図１１のフローチャートに示す順序に従い、コード参照時の動作を詳細に説明する。
【００８０】
図１１において、Ｓ６１は、カーソルのあるフィールドに対するコードを取り出す。これは、既述した図１０の（ｂ）のＦＯＲＭを画面上に表示した状態で、カーソルのあるフィールドに対するコード、例えば▲３▼の矩形内にカーソルがある場合、図１０の（ｃ）の▲３▼’から該当するコード“処理区分検索”を取り出す。
【００８１】
Ｓ６２は、コードをもとにコードテーブル“処理区分検索”を検索する。
Ｓ６３は、ファイル名の拡張子から配置を判断する。これは、検索しようとするコードテーブル“処理区分検索”のファイルの拡張子が“Ｃ”のときはクライアント、“Ｓ”のときはサーバと予め定めてあるので、Ｃの場合（クラアイント配置の場合）には、Ｓ６４でクアイント内のコードテーブル３の内容を一覧表示し、Ｓ６５で一覧表示の中から選択入力する。一方、Ｓの場合（サーバ配置の場合）には、Ｓ６６でコードテーブルをもとにＳＱＬ文を自動生成し、Ｓ６７でサーバにＳＱＬ文を発行してデータを受信し、Ｓ６８で一覧表示し、Ｓ６９で選択入力する。
【００８２】
以上によって、例えば図１０の（ｂ）のＦＯＲＭの画面上でカーソルのあるフィールドのコードを入出力情報定義５６から取出し、このコードをもとにコードテーブルを検索し、Ｃ（クライアント）配置の場合にはクライアント配置のコードテーブルから一覧表示して選択入力し、一方、Ｓ（サーバ）配置の場合にはＳＱＬ文を自動生成して発行し受信して一覧表示して選択入力することが可能となる。
【００８３】
図１２は、本発明のコード参照の画面例を示す。
図１２の（ａ）は、実行画面の例を示す。左半分は、処理区分に対応して下側に
処理区分検索
１ 登録
２ 修正
３ 削除
が表示されるので、この中から例えば“２”を選択すると“修正”が入力されることとなる。右半分は、商品コードに対応して下側に
商品コード検索
０１ えんぴつ
０２ けしごむ
が表示されるので、この中から例えば“０２”を選択すると“けしごむ”が入力されることとなる。
【００８４】
【発明の効果】
以上説明したように、本発明によれば、テーブル設計およびコード設計をもとに自動継承した形でデータベースおよびコードテーブル３などを自動生成する構成を採用しているため、データベースの設計・製造の自動化を図ると共にテーブル設計やコード設計の情報の一元管理を簡易に実現することができる。
【図面の簡単な説明】
【図１】本発明の全体ブロック図である。
【図２】本発明の概念説明図である。
【図３】本発明のテーブル設計フローチャートである。
【図４】本発明のテーブル設計説明図である。
【図５】本発明のテーブル設計時のデータ構造例である。
【図６】本発明のコード設計フローチャートである。
【図７】本発明のコード設計説明図である。
【図８】本発明のコード設計時のデータ構造例である。
【図９】本発明のコード設計入力画面例である。
【図１０】本発明のＦＯＲＭ作成、入出力情報定義の説明図である。
【図１１】本発明のコード参照フローチャートである。
【図１２】本発明のコード参照の画面例である。
【図１３】従来技術の説明図である。
【符号の説明】
１：テーブル設計
１１：項目ディクショナリ
１２：テーブル一覧
１３：テーブル項目定義
１４：データライブラリ
１５：データライブアリ生成手段
１６：物理データベース生成手段
２：コード設計
２１：コード一覧
２２：コード定義
２３：コード情報継承手段
３：コードテーブル
４：サーバ
４１：データベース
５：クライアント
５４：コード参照手段
５６：入出力情報定義[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a database design apparatus and database control apparatus for designing and controlling a database.
[0002]
[Prior art]
Conventionally, when designing a database, as shown in FIG. 13, a DB design for storing data in the design process and various codes used at that time are designed to create a paper DB design document and a paper code design document. . Next, in the manufacturing process, an actual database was created based on a paper DB design document and a paper code design document, a list selection window, a business routine direct description, and the like were created.
[0003]
[Problems to be solved by the invention]
Conventionally, as shown in FIG. 13 described above, after designing the table and code in the design process, the actual database, general selection subwindow, business routine, etc. are described based on the paper-based table design and code design. Therefore, it may be difficult to manage and may be changed from the contents of the original table design and code design when the database is actually created during the manufacturing process, and based on the table design and code design There was a problem that the actual database and list selection window could not be automatically generated.
[0004]
In order to solve these problems, the present invention automatically generates a database and a code table based on the table design and code design, automates the design and manufacture of the database, and unifies information on the table design and code design. The purpose is to simplify management.
[0005]
[Means for Solving the Problems]
Means for solving the problem will be described with reference to FIG.
In FIG. 1, an item description 11 stores item names and attributes.
[0006]
The table list 12 stores table names and table IDs.
The table item definition 13 registers item names and the like in association with table IDs.
[0007]
The data library 14 is registered in advance with code information of table names and the like.
The data library generation means 15 automatically generates a table in which the item name and the attribute extracted from the item dictionary 11 are set in association with the table ID extracted from the table item definition 13.
[0008]
The code list 21 stores code names, table names, and the like.
The code definition 22 stores item name attributes and the like.
The code information inheriting means 23 extracts the item name of the code item and the item name that is the name item from the code definition 21 based on the attribute, and automatically generates the code table 3, or from the code definition 22 based on the attribute. The code table 3 is automatically generated by extracting the item name of the code item and the item name which is the name item, and extracting the code information of the corresponding table name from the data library 14 created in advance based on the corresponding table name of the code list 21. It is something to do.
[0009]
The code reference means 54 extracts the code at the position of the cursor on the screen with reference to the input / output information definition 56, extracts the corresponding code table 3 based on the extracted code, displays the contents thereof, and displays the code. It can be referred to.
[0010]
The input / output information definition 56 stores codes and the like in association with positions on the screen.
Next, the operation will be described.
[0011]
The input item name and attribute are stored in the item dictionary 11, the input table name and table ID are stored in the table list 12, and the item name is associated with the table ID based on the item dictionary 11 and the table list 12. Register in the table item definition 13 and create a table in the data library in which the data library generation unit 15 sets the item name and the attribute extracted from the item dictionary 11 in association with the table ID extracted from the table item definition 13 I have to. Then, the physical database generation means 16 refers to the table and creates a database.
[0012]
At this time, the actual data is registered in the automatically generated table in association with the item name.
Further, the input code name and table name are stored in the code list, and the attribute of the input item name is stored in the code definition, and the code information inheriting means 23 extracts the item name of the code item from the code definition 22 based on the attribute. The code table 3 is automatically generated by extracting the item name that is the name item, or the item name of the code item and the item name that is the name item are extracted from the code definition 22 based on the attribute and the code list 22 corresponds. The code table 3 is automatically generated by extracting the code information of the table name from the data library 14 created in advance based on the table name.
[0013]
At this time, the item name of the code item and the item name which is the name item are extracted from the code definition 22 based on the attribute, and the code table 3 is automatically generated and arranged in the client, or based on the attribute from the code definition 22. The code table 3 is automatically generated by extracting the item name of the code item and the item name as the name item, and extracting the code information of the table name from the data library 14 created in advance based on the corresponding table name of the code list 21. In other words, the arrangement on the server where the database exists is arbitrarily changed.
[0014]
The code reference means 54 stores the code in the input / output information definition 56 in association with the input position on the screen, takes out the code at the position where the cursor is on the screen with reference to the input / output information definition 56, Based on the extracted code, the corresponding code table 3 is extracted, its contents are displayed, and the code can be referred to.
[0015]
At this time, when the code table 3 is searched, the code table 3 corresponding to the client or server corresponding to the extracted code identifier is taken out, the contents thereof are displayed, and the code can be referred to.
[0016]
Therefore, by automatically generating the database and code table 3 based on the table design and code design, it is possible to automate the design and manufacture of the database and to easily realize centralized management of table design and code design information. Is possible.
[0017]
DETAILED DESCRIPTION OF THE INVENTION
Next, embodiments and operations of the present invention will be described in detail sequentially with reference to FIGS. Here, a program is loaded from a storage medium (not shown) onto the main memory and started, and various processes described below are executed.
[0018]
FIG. 1 shows a block diagram of an embodiment of the present invention.
In FIG. 1, a table design 1 designs a table for storing database data. As shown, an item dictionary 11, a table list 12, a table item definition 13, a data library 14, and a data library generation are generated. It comprises means 15, physical database generation means 16 and the like.
[0019]
The item description 11 stores item names, alphanumeric items, attributes, the number of digits, and the like (see (a) of FIG. 5).
The table list 12 stores table names, table IDs, arrangements, and the like (see FIG. 5B).
[0020]
The data item definition 13 is for registering an item name or the like in association with the table ID.
The data library (data library DB) 14 includes a definition body and a data part, and is a library that stores various data (see (d) of FIG. 5).
[0021]
The data library generation means 15 generates the data library 14 (see FIG. 3).
The physical database generation unit 16 generates the database 41.
[0022]
The code design 2 automatically generates the code table 3, and is composed of a code list 21, a code definition 22, a code information inheriting means 23, and the like.
[0023]
The code list 21 stores code names, code IDs, table names, and the like (see FIG. 8).
The code definition 22 stores a code ID, item name, item name attribute (code or name distinction), and the like (see FIG. 8).
[0024]
The code information inheriting unit 23 generates the code table 3.
The code table 3 stores code information (see FIG. 7).
The server 4 provides services to a plurality of clients. Here, the server 4 manages the database 41 and accesses the database 41 to provide various information to the clients.
[0025]
The database 41 is a centralized management that makes it easy to search various data.
The client 5 is connected to the server 4 via the network and receives provision of various services. Here, the client 5 includes an execution module 51 and the like as illustrated.
[0026]
The execution module 51 is connected to the server 4 via a network and requests provision of various services. Here, the execution module 51 includes a FORM helper 52, a FORM 55, a business routine 57, and the like. is there.
[0027]
The FORM helper 52 provides various services, and includes a list window 53, code reference means 54, and the like.
The list window 53 is a window that displays various lists.
[0028]
The code reference means 54 displays a list of the contents of the code table 3 corresponding to the code on the list window (see FIG. 11).
The FORM 55 defines a form for displaying a code input screen or displaying the contents of the code table 3. The input / output information definition 56 defines input / output information on the screen (see FIG. 10c).
[0029]
The business routine 57 is a program for performing business processing.
FIG. 2 is a conceptual explanatory diagram of the present invention. This is a conceptual explanatory diagram of the configuration of FIG.
[0030]
In FIG. 2, S1 designs a table. In this case, the table design 1 of FIG. 1 performs the design of the database table according to the flowchart of FIG.
In S2, code design is performed. In this case, various code designs required when the code design 1 of FIG. 1 searches a database are performed according to a flowchart of FIG. 6 described later.
[0031]
S3 performs FORM creation and input / output information definition. This is done by creating a FORM for referring to the code and defining input / output information in accordance with the flowchart of FIG.
[0032]
In S4, the code reference function is automatically executed. This performs code reference according to a flowchart of FIG. 11 described later as a function for referring to the code.
Details will be sequentially described below.
[0033]
The table design will be described in detail with reference to FIGS. 4 and 5 in the order shown in the flowchart of FIG.
FIG. 3 shows a table design flowchart of the present invention.
[0034]
In FIG. 3, S11 inputs an item dictionary.
In step S12, an item dictionary is created. In S11 and S12, as described on the right side, an item name, an alphanumeric item name, an attribute, the number of digits, and the like are input and stored in the item dictionary 11 (see FIGS. 4 and 5).
[0035]
In step S13, a table list is input.
In S14, a table list is created. In S13 and S14, as described on the right side, the table list 12 is input by inputting the table name, table ID, and arrangement (distinguishing whether the table is arranged in C (client) or S (server)). (See FIGS. 4 and 5).
[0036]
In S15, a table item definition is selected and input.
In step S16, a table item definition is created. In S15 and S16, as shown on the right side, item names, KEY, NULL, UNIQ, and the like are registered (see FIGS. 4 and 5).
[0037]
In step S17, data library creation processing is performed. In this process, the data library is created according to the procedures of S18 to S22 based on the information created in S11 to S16.
[0038]
In step S18, a table list is displayed and a table name to be created is selected. For example, as shown in FIG. 4A, a table list is displayed, and the table name “product master” is selected and input.
[0039]
S19 extracts information in the table item definition from the table ID. For example, the table ID “SHOHIN” of the “product master” selected on the table list 12 of FIG. 5 is taken out, and the table item definition 13 of FIG. 5C having this table ID “SHOHIN” as the table ID is shown. All entries in.
[0040]
In S20, the selected table (for example, “product master”) is created in the data library (see (f) of FIG. 4 and (d) of FIG. 5).
In S21, the item name of the table item definition is set in the item of the “product master” table in the data library. This sets the item names (for example, “product code”, “product name”, etc.) of the table item definition in FIG. 5C to the items of the table created in S20 (FIG. 4F), FIG. 5 (d)).
[0041]
In S22, the attribute of each item is extracted from the item dictionary and set. This sets the attribute of the item dictionary 11 corresponding to the item set in the table in S21. By these S18 to S22, for example, a frame of a table of “product master” is automatically created in the data library.
[0042]
In S23, the data entry is input to the data library “product master”. In this case, actual data is input in the frame of the “product master” table in the data library created up to S22. For example, in the product master table of FIG. 4F (or FIG. 5D)
01 Pencil 15 A
Enter the actual data.
[0043]
S24 is stored in the data part of the data library DB. This is stored in the data part of the data library DB 15 of FIG. 5 so that it can be used.
S25 EXPPORT (send) the table of arrangement “S” (symbol indicating that the arrangement is a server) to the server (the product master table of FIG. 4D, in the server DB of FIG. 5E). Store like the product master table).
[0044]
As described above, the table design can be automatically performed and stored as a table “product master” or the like in the data library DB.
FIG. 4 shows a table design explanatory diagram of the present invention. This shows the state of the table design described with reference to FIG.
[0045]
FIG. 4A shows an example of a table list. As shown in the figure, the table list 12 stores a table ID and an arrangement (S: server, C: client) in association with a table name.
[0046]
FIG. 4B shows an example of table item definition. As shown in the figure, this table item definition 13 stores item names “product code”, “product name,“ unit price ”,“ classification ”, etc., in association with the product master ID, and items in association with processing categories. Name “Processing category”, “Processing category name” and the like are stored.
[0047]
FIG. 4C shows the physical database generation means 16. The physical database generation means 16 generates a physical database as shown in the server database in FIG.
[0048]
FIG. 4E shows the data library generating unit 15. This data library generation means 15 is generated as shown in the data library of FIG. Here, a product master frame is created and its data entry is entered.
[0049]
FIG. 5 shows an example of the data structure when the table is designed according to the present invention.
FIG. 5A shows an example of an item dictionary. As shown in the figure, the item discretionary 11 stores alphanumeric item names, attributes, the number of digits, etc. in association with item names.
[0050]
FIG. 5B shows an example of a table list. As shown in the figure, the table list 12 stores table IDs, arrangements, etc. in association with table names.
FIG. 5C shows an example of table item definition. As shown in the figure, the table item definition 13 stores item names, KEY, NULL, and UNIQ in association with the table ID.
[0051]
FIG. 5D shows an example of the data library DB. The data library DB is composed of a definition body and a data part. Here, the table name and item definition are stored in the definition body. The data section stores a table “product master” and the like.
[0052]
FIG. 5E shows an example of the server DB. The server DB stores actual physical data (here, product master).
Next, the code design will be described in detail with reference to FIGS. 7 to 9 in the order shown in the flowchart of FIG.
[0053]
FIG. 6 shows a code design flowchart of the present invention.
In FIG. 6, a code list is input in S31.
In S32, a code list is created. In S31 and S32, as described on the right side, a code name, a code ID, a table name, and the like are input and stored in the code list 21 (see FIGS. 7 and 8).
[0054]
In S33, a code definition selection input is performed.
S34 creates a code definition. In S33 and S34, as described on the right side, a code ID, an item name, a code, a name, and the like are input and stored in the code definition 22 (see FIGS. 7 and 8).
[0055]
In S35, code information inheritance processing is performed. In this process, the code table 3 is created according to the procedures of S36 to S45 based on the information created in S31 to S34.
[0056]
In S36, a code list is displayed and a code name to be created is selected. For example, as shown in FIG. 7A, a code list is displayed, and a code name “processing category search” is selected and input.
[0057]
In S37, when the arrangement “C” (representing the arrangement of the code table 3 to the client) is designated, information in the code definition is extracted from the code ID. For example, based on the code ID “SYRKBN” of the code name “processing category search” in the code list 21 of FIG. 8 selected in S 36, the entry of the same code ID “SYRKBN” from the code definition 22, here , (1) Two entry information is extracted.
[0058]
In S38, the code item and the name item are recognized. Here, since the following two entries of (1) in the code definition of FIG. 8 are extracted in S37,
Code ID Item name Code Name
SYRKBN processing category 1
SYRKBN processing category name 1
The item name “processing category” of the entry set as “1” in the code column is recognized as the code item, and the item name “processing category name” of the entry set as “1” in the name column is recognized as the name item.
[0059]
In S39, the data library is extracted with the table name of the selected code list. Here, since the table name of the selected code list 21 is “processing category”, the table name “processing category” is extracted from the data library as shown in the lower right of FIG.
[0060]
In S40, a code table is created.
S41 is set based on the item dictionary information in the code table. This is based on the description in the format description column as shown in (2) in FIG.
・ Item length
・ Code name
・ Code data
Are respectively set to create the code table 3. Here, the item length is set to the number of digits “01” and “04” of the corresponding “processing category” and “processing category name” in the item dictionary 11 of FIG. “Processing category search” is set, and the data code of the “processing category” of the data library is set as the code data.
[0061]
Through the above S37 to 41, in the case of arrangement “C” (code table 3 is arranged on the client), the code table 3 is automatically created and set in the client 5 as shown in (2) of FIG. It will be.
[0062]
In S42, when the arrangement “S” (representing the arrangement of the code table 3 in the server S) is designated, information in the code definition is extracted from the code ID. For example, based on the code ID “SHOCD” of the code name “product code search” of the code list 21 of FIG. 8 selected in S36, the entry of the same code ID “SHOCD” from the code definition 22, , (1) 'information of two entries is extracted.
[0063]
In S43, the code item and the name item are recognized. Here, since the following two entries of (1) in the code definition of FIG. 8 are extracted in S43,
Code ID Item name Code Name
SHOCD product code 1
SHOCD Product Name 1
The item name “product code” of the entry set as “1” in the code column is recognized as the code item, and the item name “product name” of the entry set as “1” in the name column is recognized as the name item.
[0064]
In S44, a code table is created.
In S45, information is set in the code table. This is in accordance with the description in the format description column as shown in (2) in FIG.
-DB table name
・ Code name
・ C (code) information
・ N (name) information
Are respectively set to create the code table 3. Here, “product master” extracted from the code list 21 is set as the DB table name, “product code search” is set as the code name, “C product code” is set as the C (code) information, and N ( Name) information is set to “N product name”.
[0065]
Through the above S42 to 45, in the case of arrangement “S” (code table 3 is arranged on the server), the code table 3 is automatically created and set in the server 4 as shown in (2) of FIG. It will be.
[0066]
Further, when the arrangement is changed from S to C as the arrangement change, the code table 3 is created and arranged on the client through S37 to S41. On the other hand, when the arrangement is changed from C to S as the arrangement change, the code table 3 is created and arranged on the server through S42 to S45. As a result, the code table 3 can be automatically created and arranged for the client and the server only by arbitrarily setting the arrangement destination to C or S.
[0067]
FIG. 7 shows a code design explanatory diagram of the present invention. This shows the state of the code design described with reference to FIG.
FIG. 7A shows an example of a code list. As shown in the figure, the code list 21 stores table names in association with code names.
[0068]
FIG. 7B shows an example of code definition. As shown in the figure, the code definition 22 stores a code “product code” and a name “product name” for a product code search.
[0069]
FIG. 7C shows the code information inheriting means 23. This code information inheriting means 23 is for generating the code table 3 of FIG.
FIG. 7D shows an example of the code table 3. As shown in the figure, the code table 3 is described in the format description column as described in S37 to S41 in FIG. 6 in the case of arrangement: C (representing client arrangement).
・ Item length
・ Code name
・ Code data
Is set in the code table 3. A specific example is shown in (2) of the sample data.
[0070]
In the case of arrangement: S (representing server arrangement), as described in S42 to S45 in FIG.
-DB table name
・ Code name
・ C (code) information
・ N (name) information
Is set in the code table 3. A specific example is shown in (2) of sample data.
[0071]
FIG. 8 shows an example of the data structure at the time of designing the code of the present invention.
FIG. 8A shows an example of a code list. As shown in the figure, the code list 21 stores code IDs, table names, and the like in association with code names.
[0072]
FIG. 8B shows an example of code definition. As shown in the figure, the code definition 22 stores an item name, a code, and a name in association with the code ID.
FIG. 9 shows an example of a code design input screen of the present invention.
[0073]
FIG. 9A shows an example of client arrangement (arrangement: C). Here, the setting is made as shown below.

FIG. 9B shows an example of server arrangement (arrangement: S). Here, the setting is made as shown below.
[0074]

Next, the code reference will be described in detail with reference to FIGS.
[0075]
FIG. 10 is an explanatory diagram of FORM creation and input / output information definition according to the present invention.
FIG. 10A shows a FORM creation flowchart.
In FIG. 10A, in S51, an item layout is input to the FORM. This is done by inputting the item layout shown in FIG. 10B from the screen.
[0076]
In S52, an alphanumeric item name in the item dictionary is selected and input to each item TAG (tag) of the FORM. In this case, the alphanumeric item names in the item dictionary 11 shown in FIG. For example, as the processing category (3) TAG shown in FIG. 10B, the corresponding alphanumeric item name “SYRKBN” in the item dictionary 11 of FIG. Similarly, other items are selected and input.
[0077]
In S53, the input / output information definition is selected and input. As shown in the input / output information definition 56 in FIG. 10 (c), this is selected and input from the item dictionary 11 and the code list 21 as shown in association with the TAG.
[0078]
With the above procedure, the input / output information definition 56 of FIG. 10C is generated in the case of the FORM layout example of FIG.
FIG. 10B shows a FORM example. This is an example in which item layout (processing category, product code) is performed on FORM. Then, the item dictionary 11 of FIG. 5A takes out alphanumeric item names in association with each TAG as shown in the figure.
[0079]
FIG. 10C shows an example of input / output information definition. The input / output information definition 56 registers item names, attributes, the number of digits, and codes in association with TAGs.
Next, the operation at the time of code reference will be described in detail according to the order shown in the flowchart of FIG.
[0080]
In FIG. 11, S61 takes out the code for the field with the cursor. This is because the FORM of FIG. 10B described above is displayed on the screen and the code for the field where the cursor is located, for example, if the cursor is in the rectangle of (3), The corresponding code “process category search” is extracted from (3) ′.
[0081]
In step S62, the code table “processing category search” is searched based on the code.
In S63, the arrangement is determined from the extension of the file name. This is because it is predetermined as a client when the file extension of the code table “processing category search” to be searched is “C”, and as a server when “S”, the case of C (in the case of client arrangement). ), The contents of the code table 3 in the quant are displayed in a list in S64, and selected from the list display in S65. On the other hand, in the case of S (server arrangement), an SQL statement is automatically generated based on the code table in S66, an SQL statement is issued to the server in S67, data is received, and a list is displayed in S68. In S69, the selection is input.
[0082]
Thus, for example, in the case of the C (client) arrangement, the code of the field at the cursor is extracted from the input / output information definition 56 on the FORM screen in FIG. In the case of S (server) arrangement, a SQL statement is automatically generated, issued, received, displayed in a list, and can be selected and input. Become.
[0083]
FIG. 12 shows an example of a code reference screen according to the present invention.
FIG. 12A shows an example of an execution screen. The left half is on the lower side corresponding to the processing category
Processing category search
1. Registration
2 Correction
3 Delete
Is displayed, for example, if “2” is selected from among these, “correction” is input. The right half corresponds to the product code
Product code search
01 pencil
02 Keshgomu
Is displayed, for example, when “02” is selected, “Kakegomu” is input.
[0084]
【The invention's effect】
As described above, according to the present invention, since the database and code table 3 are automatically generated based on the table design and code design, the database and code table 3 are automatically generated. In addition to automation, it is possible to easily realize unified management of table design and code design information.
[Brief description of the drawings]
FIG. 1 is an overall block diagram of the present invention.
FIG. 2 is a conceptual explanatory diagram of the present invention.
FIG. 3 is a table design flowchart of the present invention.
FIG. 4 is a table design explanatory diagram of the present invention.
FIG. 5 is a data structure example when designing a table according to the present invention.
FIG. 6 is a code design flowchart of the present invention.
FIG. 7 is an explanatory diagram of code design of the present invention.
FIG. 8 is a data structure example when designing a code according to the present invention.
FIG. 9 is an example of a code design input screen according to the present invention.
FIG. 10 is an explanatory diagram of FORM creation and input / output information definition according to the present invention.
FIG. 11 is a code reference flowchart of the present invention.
FIG. 12 is an example of a code reference screen according to the present invention.
FIG. 13 is an explanatory diagram of a conventional technique.
[Explanation of symbols]
1: Table design
11: Item dictionary
12: Table list
13: Table item definition
14: Data library
15: Data live ant generation means
16: Physical database generation means
2: Code design
21: List of codes
22: Code definition
23: Code information inheritance means
3: Code table
4: Server
41: Database
5: Client
54: Code reference means
56: Input / output information definition

Claims (2)

In a system design device for designing a system composed of a server and a client,
A data attribute defining means for defining an attribute of a code item including information on an arrangement location indicating whether a code item of a database used in the system is arranged on a server or a client;
Based on the location information defined by the data attribute definition means, the contents of the code table in the client are displayed when the location is the client, and the SQL statement is automatically generated based on the code table when the location is the server. A system design apparatus comprising: processing means for issuing a SQL statement to the server and displaying the content of the received data, and for controlling a reference process of the defined code item. A data attribute defining means for defining an attribute of a code item including information on an arrangement location indicating whether a code item of a database used in the system is arranged on a server or a client;
Based on the location information defined by the data attribute definition means, the contents of the code table in the client are displayed when the location is the client, and the SQL statement is automatically generated based on the code table when the location is the server. A recording medium storing a program that causes a computer to function as processing means for controlling the reference processing of a defined code item , which displays the content of data received by issuing an SQL statement to a server.

Images