JP2008186411A - Data management method, client terminal device and client server system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To improve the efficiency of operation while suppressing consumption of a system resource in a client terminal. <P>SOLUTION: This data management method comprises: a confirmation step wherein a client computer 2 confirms whether a database 121 of a server computer 1 is available; a local database starting step wherein, if the database 121 is not available, portable data having a general-purpose form, is read from a portable data storage part 223, converted into an appropriate form, and stored in the database 221; and a data storage step wherein, when finishing an operation using the database 221, data in the database 221 is read, converted into the general-purpose form, and stored as the portable data into the portable data storage part 223. When the database 121 of the server computer 1 is available, a database engine of the database 221 is not started. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a data management method when a client computer performs work using a database of a server computer or its own local database, a client terminal device using the same, and a client server system.

  A client computer (hereinafter simply referred to as a client or client terminal) refers to and uses data stored in a file managed by a server computer (hereinafter simply referred to as a server). In recent years, in addition to advances in performance and miniaturization of devices, there have been fewer restrictions on work locations due to the advancement of wireless networks and broadbandization. The number of cases where mobile terminals are used is increasing. Therefore, techniques for improving convenience and the like when using a mobile terminal as a client terminal have been proposed.

  For example, Patent Document 1 below discloses a technique that considers a case where a mobile terminal (client) is disconnected from a server and work is performed using a client-side local database. Specifically, when acquiring data used in the local database from the server side, only the necessary data is selectively acquired, shortening the synchronization processing time between the server side database and the client side database. In addition, the data can be used quickly and efficiently.

JP 11-31178 A

  As described above, if the technique described in Patent Document 1 is used, the synchronization process can be shortened and the convenience when a mobile terminal is used as a client terminal is improved. No consideration is given to the use when connected. Further, it is a technique related to acquisition and write-back of data from the server, and no consideration is given to the efficiency of work performed using a mobile terminal.

  In general, portable terminals such as notebook personal computers are designed in consideration of portability, power consumption, and the like, and therefore have inferior performance compared with stationary terminals (desktop computers and the like). On the other hand, recently, in addition to the above-mentioned reasons such as higher performance of devices and changes in the network connection environment, mobile terminals are frequently used in business for reasons such as saving space in the office. . In other words, mobile terminals that have been often used stand-alone separately from the network (server) are increasingly used while connected to the network. Along with this, it is desired to realize work efficiency when using a portable terminal connected to a network.

  The present invention has been made in view of the above, and a data management method and a client for realizing work efficiency when a portable terminal such as a notebook personal computer is used as a client terminal and connected to a server An object is to obtain a terminal device and a client server system.

  In order to solve the above-described problems and achieve the object, the present invention provides a client computer that operates using a database of a server computer or its own local database. A confirmation step for confirming whether or not the database of the server computer can be used, and when the database of the server computer is not usable, the data management unit has previously generated a general format based on the data stored in the database of the server computer Data is read from the portable data storage unit, and the read data is converted into a format for storing in the local database, and the data obtained by executing the conversion process is passed through the database engine. To store in local database When the local database startup step and the work using the local database are completed, the data management unit reads the data in the local database, converts the read data into a general-purpose format, and executes the conversion process A data storage step for storing the data in the general-purpose format obtained as portable data in the portable data storage unit, and if it is determined in the checking step that the database of the server computer is available The database engine of the local database is not started.

  Further, in the data management method according to the next invention, when it is determined that the database of the server computer is usable in the confirmation step, the data management unit is stored in the portable data storage unit. A database update step of updating the database based on portable data.

  In the data management method according to the next invention, in the database update step, the data management unit converts portable data read from the portable data storage unit into a format for storing in the database, and the conversion Data obtained by executing the process is stored in the database via the database engine of the database.

  Further, in the data management method according to the next invention, when it is determined that the database of the server computer is usable in the confirmation step, the data management unit is stored in the portable data storage unit. A database update requesting step for requesting the server computer to update the database based on the portable data.

  In the data management method according to the next invention, the data storage step further includes a flag indicating whether or not the work using the local database has been normally completed after the data in the general format is stored in the portable data storage unit. In the local database startup step, the data management unit further checks the status of the flag, and if it can be confirmed that the work using the previous local database has been completed normally, Reading portable data stored in the data storage unit, converting the read data into a format for storing in the local database, and storing the data obtained by executing the conversion process in the local database Features.

  In addition, the data management method according to the next invention is further specified by the user when the data management unit receives an instruction from the user in a state of performing work using the database of the server computer. Data for acquiring data from the database of the server computer, further converting the acquired data into general-purpose data, and storing the converted data obtained by executing the conversion process in the portable data storage unit An acquisition step.

  In addition, the data management method according to the next invention is further specified by the user when the data management unit receives an instruction from the user in a state of performing work using the database of the server computer. It is data, Comprising: The data acquisition step which acquires the data converted into the general-purpose format in the said server computer from the said server computer, and stores the acquired data in a portable data storage part is characterized by the above-mentioned.

  In the data management method according to the next invention, the general-purpose format is a CSV (Comma Separated Values) format or an XML (Extensible Markup Language) format.

  A client terminal device according to the next invention is a client terminal device that performs work using a database of a server computer or its own local database, and confirms whether or not the database of the server computer can be used. When the connection status confirmation unit, the portable data storage unit for storing portable data that is data in a general format generated based on the database of the server computer, and the database of the server computer are not available Portable data obtained by converting the portable data format read from the portable data storage unit into a format for storing in the local database, and converting the data format obtained from the local database into a general-purpose format Data for storing data in the portable data storage unit In accordance with an instruction from the management unit and the data management unit, the data stored in the local database received from the data management unit is stored in the local database, and the data acquired from the local database is stored in the data management unit. And a database engine section to be passed to the section.

  In the client terminal device according to the next invention, when the database of the server computer is available, the data management unit stores the portable data format read from the portable data storage unit in the database. And converting the data obtained by executing the conversion process to the server computer.

  In the client terminal device according to the next invention, when the database of the server computer is available, the data management unit passes the portable data read from the portable data storage unit to the server computer. It is characterized by.

  Further, in the client terminal device according to the next invention, the data management unit can carry out the portable data storage unit from the portable data storage unit when the process of storing the previously executed portable data in the portable data storage unit is normally completed. Data is read, and the format of the read portable data is converted into a format for storing in a local database.

  Further, in the client terminal device according to the next invention, the data management unit is further designated by the user when receiving an instruction from the user in a state where the operation using the database of the server computer is being executed. Data is acquired from the database, and the converted data obtained by converting the acquired data into general-purpose data is stored in a portable data storage unit.

  Further, in the client terminal device according to the next invention, the data management unit is further designated by the user when receiving an instruction from the user in a state where the operation using the database of the server computer is being executed. It is data, Comprising: The data converted into the general-purpose format in the said server computer are acquired from the said server computer, The said acquired data are stored in a portable data storage part, It is characterized by the above-mentioned.

  In the client terminal device according to the next invention, the general-purpose format is a CSV (Comma Separated Values) format or an XML (Extensible Markup Language) format.

  A client server system according to the next invention includes the client terminal device according to any one of claims 9 to 15 and a server terminal device that manages data used by the client terminal device. Features.

  In the data management method according to the present invention, the client computer monitors the state of the network connection, and determines whether to start the database engine of the local database according to the monitoring result. In other words, when the client computer accesses the database of the server computer and does not need to use the local database, the system engine is prevented from being wasted without starting the database engine. did. Further, when the client computer is used while being disconnected from the server computer, system resources used for accessing the database of the server computer are allocated to operate the database engine of the client computer. As a result, in both the state where the client computer is connected to the server and the state where the client computer is disconnected from the server, it is possible to prevent the performance of the entire system from being deteriorated, so that the work efficiency can be improved.

  Embodiments of a data management method according to the present invention will be described below in detail with reference to the drawings. Note that the present invention is not limited to the embodiments.

  FIG. 1 is a diagram showing a configuration example of a computer network system including client computers (also referred to as workstations) and server computers that use the data management method according to the present invention. This computer network system includes a server computer 1 and a plurality of client computers 2 connected to a network 100 such as a LAN or the Internet.

  FIG. 2 is a diagram showing a configuration example of a server computer (hereinafter simply referred to as a server) and a client computer (hereinafter simply referred to as a client) constituting the computer network system shown in FIG.

  The server 1 includes a control unit 11, a storage unit 12, and a communication unit 15. The control unit 11 includes a data management unit 111, a database engine unit 112, and an authentication unit 113, and the storage unit 12 includes a relational database (RDB, hereinafter referred to as a database) 121. Further, the server 1 has a function of connecting to a network via the communication unit 15 and exchanges various information with other terminals (computers) connected to the network.

  In the control unit 11 of the server 1, the data management unit 111 instructs the database engine unit 112 when receiving a request from a terminal connected via a network such as the client 2, and stores the data stored in the database 121. Update, read, etc. The database engine unit 112 exchanges data exchanged between the data management unit 111 and a relational database (RDB, hereinafter referred to as database) 121 in accordance with an instruction from the data management unit 111. The authentication unit 113 authenticates a terminal that requests access to itself (server 1), and determines whether to permit access.

  The client 2 includes a control unit 21, a storage unit 22, a display unit 23, an input unit 24, and a communication unit 25. The control unit 21 includes a data management unit 211, a database engine unit 212, a usage mode switching unit 213, a portable data handling unit 214, a data editing unit 215, a power supply state confirmation unit 216, and a server connection state confirmation unit 217. The storage unit 22 includes a database 221, a synchronization detection flag 222, and a portable data storage unit 223. The display unit 23 is composed of a CRT, LCD (liquid crystal display panel), etc., and displays various screens to the user. The input unit 24 includes, for example, a keyboard and a mouse (not shown), and is used by the user to input various information. The client 2 also has a function of connecting to a network via the communication unit 25, and exchanges various information with other terminals (computers) connected to the network.

  In the control unit 21 of the client 2, the data management unit 211 instructs the database engine unit 212 to update and read data stored in the database 221. Note that the data management unit 211 can switch the operation mode according to the usage mode (whether or not it is connected to the server 1).

  The database engine unit 212 exchanges data exchanged between the data management unit 211 and the database 221 in accordance with instructions from the data management unit 211.

  When the usage mode switching unit 213 receives an instruction from the input unit 24 (from the user), the usage mode switching unit 213 performs an operation in a state where the terminal (client 2) is connected to the server 1 according to the content of the instruction, or the server 1 The data management unit 211 is notified of whether to perform the operation in a state disconnected from the server (a state in which access to the server 1 is impossible).

  The portable data handling unit 214 instructs the data management unit 211 to acquire the data specified by the user from the database 121 of the server 1 in accordance with the instruction from the user acquired via the input unit 24. Further, an instruction is issued to store the data in the portable data storage unit 223 designated by the user in the database 121 of the server 1.

  The data editing unit 215 obtains an instruction for editing data stored in the database 221 or data stored in the database 121 in the server 1 from the user via the input unit 24. Further, the data management unit 211 is instructed to edit the data according to the content of the acquired editing instruction.

  The power status confirmation unit 216 monitors the power ON / OFF operation performed by the user using the input unit 24 and notifies the data management unit 211 of the monitoring result.

  The server connection status confirmation unit 217 confirms whether the own terminal is connected to the target server (here, the server 1), and notifies the data management unit 211 of the confirmation result.

  Note that the database 221 in the storage unit 22 is used when the client 2 performs work while being disconnected from the server 1. The synchronization detection flag 222 indicates whether or not the synchronization processing of data stored in the database 221 to be described later and data stored in the portable data storage unit 223 has been normally completed. Is set to '1' when starting a work using, and returned to '0' when the work ends normally. In addition, the portable data storage unit 223 acquires data from the database 121 or the database 221 of the server 1 and holds data in a general format obtained by converting the acquired data into a general format as portable data. It is an area.

  Next, a general flow of work (work) performed using the client 2 having the above-described configuration will be described with reference to FIGS. 3-1 and 3-2. Here, a description will be given assuming that a portable terminal such as a notebook personal computer is used as the client 2. As an example, a case where the client 2 is used in the business of an accounting office will be described. FIG. 3A is a diagram illustrating an outline of a work flow performed using the client 2 (corresponding to the workstation illustrated in FIG. 3A). FIG. 2 is a flowchart illustrating an example of a work flow performed using WS).

  A workstation (WS) corresponding to the client 2 is usually used in an office to which a user belongs in a state where it can access a database (SV-DB) of a server via a LAN (see FIG. 1).

  Here, in the work at an accounting office, a plurality of types of financial book tables are created for one customer (company, etc.), but each financial book table has common basic data (for example, customer name, address, etc.). Financial information such as fixed information and sales amount). For this reason, it is general that basic data is converted into a database and managed centrally, and the work is performed while accessing the database (while connected to the database). On the other hand, there may be a case where the work at the advisor is required due to a request from the advisor, but as described above, it is necessary to connect to the database at the time of the work. For this reason, the WS includes a local database (WS-DB), and enables work in an environment where it is not possible to connect to the SV-DB such as an advisor.

  Then, when work is required in an environment where it is not possible to connect to an SV-DB different from the normal time, such as an advisor, the user reads the necessary data from the SV-DB and stores it in the storage unit (hard disk, etc.) of the workstation. Keep it. Note that the data acquired from the SV-DB is converted into a versatile text format (for example, CSV (Comma Separated Values) format, XML (Extensible Markup Language) format, etc.), and then stored in the storage unit (step). S1). Details of the operation of acquiring necessary data by the client terminal will be described later.

  After that, the connection to the SV-DB is terminated and the office moves from the office to the consultant (step S2). When the workstation is turned on to start the work there, it is stored in the storage unit. Existing text data (WS-text) is stored in a local database (WS-DB) in the workstation (step S3). It is assumed that the SV-DB cannot be accessed from the destination (advisor). If the SV-DB can be accessed from the destination, the process of step S3 is not executed.

  In this state (the state in which the SV-DB cannot be accessed), the user performs work and the WS-DB is updated (step S4). Further, when an operation for instructing the power-off of the workstation is performed by the user, at that time The data stored in the WS-DB in the workstation is read from the WS-DB, converted into a text format, and then stored in the storage unit in the workstation (step S5). Details of the operation of converting the data stored in the WS-DB into a text format and storing it in the storage unit will be described later.

  Thereafter, after the user moves from an environment inaccessible to the server in the office to an environment in which the server can be accessed (for example, in the office) and then the workstation is powered on again (step S6), the storage unit The database (SV-DB) in the server is updated based on the text data (WS-text) stored in the server. That is, the SV-DB and WS-text synchronization process is executed (step S7). The details of the SV-DB and WS-text synchronization process will be described later, but the execution timing of the process may be performed immediately after the power is turned on, or when the execution instruction is given by the user. Also good. Since the workstation does not need to use a local database in a state where it can access the database (SV-DB) of the server, the system resource is set so that its own database (WS-DB) engine is not started. Of consumption.

  In this way, when the mobile terminal is used as a client terminal (workstation) and the mobile terminal has a local database, the work place is not limited to the office or the like that can access the server that is the original work place. Can be flexibly changed.

  Next, based on FIG. 4, a description will be given of the startup processing of the mobile terminal when the mobile terminal is used as a client terminal (operation when a user requests to turn on the power) and the subsequent operation. . FIG. 4 is a flowchart illustrating an example of a client terminal activation process. The description will be made assuming that the configuration of the mobile terminal is the same as that of the client computer 2 shown in FIG.

  When the start processing start condition is satisfied in the client 2, the client 2 first executes a server search operation to confirm the operating environment as shown in FIG. Specifically, the server connection state confirmation unit 217 confirms the connection state to the network, and if it is connected to the network, whether there is a connectable server (access to the desired server and the database can be used) (Step S11, S12).

  If there is a server that can be connected to the network (step S12, Yes), the data management unit 211 performs a connection process to the database 121 of the desired server (here, server 1) via the communication unit 25. And start the operation in a state where the database 121 of the server 1 is available (referred to as “normal processing” in this embodiment) (step S13). In this case, since the local database 221 is not used, the data management unit 211 does not activate the database engine unit 212.

  On the other hand, when it is not possible to access the database of the desired server (server 1) because it is not connected to the network or there is no server that can be connected to the network (No in step S12), the data management unit 211 Then, processing in a state where the database 121 of the server 1 is unavailable (referred to as “portable processing” in this embodiment) is started. Although the portable processing will be described separately, when performing the portable processing, the data management unit 211 activates the database engine unit 212.

  Further, during the operation of the server 1 with the database 121 available (during normal processing execution), the portable data handling unit 214 receives a data operation instruction in the portable data storage area 223 via the input unit 24. To see if it is from the user. Specifically, monitoring whether or not the user has instructed that data used when the client 2 is disconnected from the server 1 to be used from the database 121 and stored in the portable data storage unit 223, and It is monitored whether or not the user has instructed the data stored in the portable data storage unit 223 to be stored in the database 121.

  If there is no data operation instruction (No at step S14), the normal process is continued. On the other hand, when the user gives an instruction to acquire data from the database 121 and store it in the portable data storage unit 223 when the client 2 is disconnected from the server 1 (step S14, Yes, step S15, Yes), the portable data handling unit 214 notifies the data management unit 211 to that effect, and the data management unit 211 reads data from the database 121 (in this embodiment, “to portable device”). (Referred to as “take-out process”).

  When the user instructs to store the data stored in the portable data storage unit 223 in the database 121 (step S14, Yes, step S15, No), the portable data handling unit 214 To the data management unit 211, the data management unit 211 writes the data stored in the portable data storage unit 223 to the database 121 (referred to as “return processing from the portable device” in this embodiment). ).

  Next, the take-out process to the portable device (data reading process from the database 121 by the data management unit 211) will be described with reference to FIG. FIG. 5 is a flowchart showing an example of a process for reading data from the database 121. This process is performed when the user gives an instruction to execute the process for taking out to the portable device in the process shown in FIG. To run.

  As shown in FIG. 5, in the take-out process to the portable device, first, the data management unit 211 confirms the state of the synchronization detection flag 222 in the storage unit 22 (step S21), and from the confirmation result, the previous portable operation is performed. It is determined whether or not the process (details will be described later) has been completed normally (step S22). If it is determined that the previous mobile processing has not ended normally (No in step S22), the data management unit 211 instructs the display unit 23 to display that fact (error display). Then, the display unit 23 performs error display according to this instruction to notify the user (step S27).

  On the other hand, when it is determined that the previous mobile processing has been normally completed (step S22, Yes), the data management unit 211 waits for the user to select data to be read from the database 121 of the server 1. (Step S23). Specifically, the data management unit 211 displays, for example, a list of data stored in the database 121 on the display unit 23 so that the user can select data to be read from the database 121 of the server 1. The user selects data to be read using a mouse or the like constituting the input unit 24, and instructs the start of reading processing of the selected data after the data selection is completed. The information on the data selected by the user and the information for instructing the start of the data reading process are captured by the portable data handling unit 214, and the portable data handling unit 214 passes the captured information to the data management unit 211. .

  The data management unit 211 confirms the content of the data received from the portable data handling unit 214, and first stores which data has been selected by the user (step S24). Here, for example, information indicating the selected data is stored in the storage unit 22 and stored. Next, the data selected by the user is read from the database 121, and the read data is converted into a text format (CSV format, XML format, etc.) using a predetermined conversion algorithm or the like (step S25).

  Finally, the data management unit 214 stores the converted data obtained by executing the conversion process in the portable data storage unit 223 in the storage unit 22 (step S26). And after the process of step S26 is complete | finished, it returns to a normal process.

  Next, a return process from the portable device (a process of writing data stored in the portable data storage unit 223 to the database 121) will be described with reference to FIG. FIG. 6 is a flowchart illustrating an example of a process of writing data stored in the storage unit 223 to the database 121. This process executes a return process from the portable device in the process illustrated in FIG. As instructed by the user, it is executed.

  As shown in FIG. 6, in the return processing from the portable device, first, the data management unit 211 confirms the state of the synchronization detection flag 222 in the storage unit 22 (step S31), and the previous portable processing from the confirmation result. It is determined whether or not has been normally completed (step S32). If it is determined that the previous mobile processing has not been completed normally (step S32, No), the data management unit 211 instructs the display unit 23 to display that fact (error display). Then, the display unit 23 performs error display according to this instruction to notify the user (step S36).

  On the other hand, if it is determined that the previous portable process has been normally completed (step S32, Yes), the data management unit 211 stores the data stored in the portable data storage unit 223 and the server 1 Merge processing of data stored in the database 121 is performed (step S33). In the merge process, the data management unit 211 converts the format of the data to be merged as necessary. Next, the data management unit 211 waits for the user to select data to be returned (stored) to the database 121 from the merged data obtained by executing the merge process (step S34). Specifically, the data management unit 211 displays, for example, a list of merged data on the display unit 23 so that the user can select data to be returned to the database 121. The user selects data to be read using a mouse or the like constituting the input unit 24, and instructs the start of return (storage) processing of the selected data to the database 121 after the data selection is completed. The information on the data selected by the user and the information for instructing the start of the data return process are captured by the portable data handling unit 214, and the portable data handling unit 214 passes the captured information to the data management unit 211. .

  The data management unit 211 confirms the contents of the data received from the portable data handling unit 214, first grasps which data has been selected by the user, and registers the selected data in the database 121 (step S35). . And after the process of step S35 is complete | finished, it returns to a normal process.

  Next, the portable processing (processing in a state where the database 121 of the server 1 cannot be used) will be described with reference to FIG. FIG. 7 is a flowchart showing an example of processing in a state where the database 121 of the server 1 cannot be used. This processing is performed when the client 2 is not connected to the network as described in the description of FIG. Alternatively, execute this when there is no server that can be connected to the network. However, here, the description will be made from the point where the client 2 is activated, similarly to the operation description based on FIG. 4 described above.

  When the start process start condition is satisfied in the client 2, the client 2 first executes a server search operation to confirm the operating environment as shown in FIG. 7 (steps S41 and S42). Steps S41 and S42 are the same as steps S11 and S12 shown in FIG.

  In step S42, when the client 2 is not connected to the network or there is no server that can be connected to the network (No in step S42), the data management unit 211 starts the portable process on the display unit 23. A confirmation screen is displayed to determine whether or not to accept (step S43), and waits for the user to determine whether or not to start the portable process. The usage pattern switching unit 213 acquires the determination result by the user via the input unit 24, and the usage pattern switching unit 213 passes the acquired information to the data management unit 211.

  When the user does not select the start of the portable process (No at Step S44), Step S41 and the subsequent steps are executed again. On the other hand, when the start of the portable process is selected (step S44, Yes), the client 2 starts an operation using the local database 221 (step S45). That is, the data management unit 211 activates the database engine unit 212.

  Next, the data management unit 211 confirms the state of the synchronization detection flag 222 in the storage unit 22 (step S46), and determines from the confirmation result whether the previous portable processing has been normally completed (step S47). . If it is determined that the previous portable process has been normally completed (step S47, Yes), the data management unit 211 reads all the data stored in the portable data storage unit 223, and reads the read data. Is converted into a format for storing in the database 221, and the converted data obtained by executing the conversion process is stored in the database 221 (step S48). Further, the state of the synchronization detection flag is changed (step S49).

  On the other hand, if it is determined that the previous portable process has not ended normally (step S47, No), the process of step S50 is immediately started without executing the processes of steps S48 and S49.

  After that, the data is changed by the user (step S50). Further, the power state confirmation unit 216 detects that the operation for instructing the power-off of the client 2 is performed by the user, and a notification to that effect is sent to the power Upon receipt from the status confirmation unit 216, the data management unit 221 reads all the data stored in the database 221 at that time, converts the read data into a text format (step S51), and executes the conversion process. The obtained text format data is stored in the portable data storage unit 223 (step S52). Then, the state of the synchronization detection flag is changed (step S53). In step S53, a process opposite to the process executed in step S49 is executed, and the state of the synchronization detection flag is returned to the state before executing step S49.

  As described above, since the portable processing (the processing in steps S45 to S53) is performed while the synchronization detection flag is operated and the state of the flag is checked, the power supply is stopped during the portable processing. Even if the data stored in the database 221 is in a newer state than the data stored in the portable data storage unit 223, the process is abnormally terminated. The database 221 in which newer data is stored can be prevented from being overwritten with data in the portable data storage unit 223 which is older data.

  In the above description, in the process (startup process) when the client 2 is turned on, it is confirmed whether or not the database built in the server on the network that is normally used is available. However, the server connection state confirmation unit 217 monitors whether or not the database built in the server can be used even during normal processing (operation), instead of performing confirmation only in the startup processing.

  Further, in the above-described export process to the portable device, the client 2 performs the process of converting the data read from the database 121 into the text format. However, the present invention is not limited to this, and the server 1 executes the conversion process to text. The client 2 may receive the data after being converted into the text format. Similarly, the merge process in the return process from the portable device described above may be performed not by the client 2 but by the server 1. When the server 1 performs these processes, the load on the client 2 can be reduced.

  As described above, in this embodiment, the client computer monitors the state of the network connection and determines whether to start the database engine of the local database according to the monitoring result. In other words, when the client computer accesses the database of the server computer and does not need to use the local database, the system engine is prevented from being wasted without starting the database engine. did. Further, when the client computer is used while being disconnected from the server computer, system resources used for accessing the database of the server computer are allocated to operate the database engine of the client computer. Accordingly, it is possible to prevent a decrease in the performance of the entire system in both the state in which the client computer is connected to the server and the state in which the client computer is disconnected from the server, so that work efficiency can be improved.

  As described above, the data management method according to the present invention is useful for data management of a local database provided on the client side of the client server system. In particular, the client and the database on the server side according to the connection status to the server Suitable for data management when working with different databases.

It is a figure which shows the structural example of the computer network system comprised by the client computer and server computer which utilize the data management method concerning this invention. It is a figure which shows the structural example of the server computer which comprises the computer network system shown in FIG. 1, and a client computer. It is a figure which shows the outline | summary of the work flow performed using a client computer. It is a flowchart which shows an example of the work flow performed using a client computer. It is the flowchart which showed an example of the starting process of a client terminal. It is a flowchart which shows an example of the data reading process from a database. It is a flowchart which shows an example of the write-in process to the database of the data stored in the storage part. It is a flowchart which shows an example of the process in the state which cannot use the database of a server.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Server computer 2 Client computer 11, 21 Control part 12, 22 Storage part 15, 25 Communication part 23 Display part 24 Input part 100 Network 111, 211 Data management part 112, 212 Database engine part 113 Authentication part 121 Relational database (RDB)
213 Usage type switching unit 214 Portable data handling unit 215 Data editing unit 216 Power supply state confirmation unit 217 Server connection state confirmation unit 222 Synchronization detection flag 223 Portable data storage unit

Claims (16)

On a client computer that works using a database on the server computer or its own local database,
A server connection state confirmation unit confirming whether the database of the server computer is available;
When the database of the server computer is not available, the data management unit converts the portable data, which is data in a general format generated in advance based on the data stored in the database of the server computer, to the portable data storage unit A local database starting step of converting the read data into a format for storing in the local database, and storing the data obtained by executing the conversion process into the local database via the database engine;
When the work using the local database is finished, the data management unit reads the data in the local database, converts the read data into a general-purpose format, and executes the conversion process. A data storage step for storing the data in the format as portable data in the portable data storage unit;
Including
A data management method comprising: not starting a database engine of a local database when it is determined in the checking step that the database of the server computer is usable. further,
A database update step in which the data management unit updates the database based on portable data stored in the portable data storage unit when it is determined in the checking step that the database of the server computer is available ,
The data management method according to claim 1, further comprising:   In the database update step, the data management unit converts the portable data read from the portable data storage unit into a format for storing in the database, and executes the conversion process to obtain the data obtained by executing the conversion process. The data management method according to claim 2, wherein the data is stored in the database via the database engine. further,
When it is determined in the checking step that the database of the server computer is usable, the data management unit updates the database based on the portable data stored in the portable data storage unit. Database update request step to request to the server computer,
The data management method according to claim 1, further comprising: In the data storage step, after storing the data in the general-purpose format in the portable data storage unit, the state of the flag indicating whether or not the work using the local database is normally completed,
In the local database startup step, the data management unit further checks the state of the flag, and if it can be confirmed that the work using the previous local database has been completed normally, it is stored in the portable data storage unit. The portable data is read out, the read data is converted into a format for storing in the local database, and the data obtained by executing the conversion process is stored in the local database. The data management method as described in any one of -4. further,
When the data management unit receives an instruction from a user in a state of performing work using the database of the server computer, the data management unit obtains data designated by the user from the database of the server computer, and A data acquisition step of converting the acquired data into data in a general format, and storing the converted data obtained by executing the conversion process in the portable data storage unit,
The data management method according to claim 1, further comprising: further,
When the data management unit receives an instruction from a user in a state of performing work using the database of the server computer, the data specified by the user is converted into a general format by the server computer. Data acquisition step of acquiring the acquired data from the server computer and storing the acquired data in the portable data storage unit,
The data management method according to claim 1, further comprising:   8. The data management method according to claim 1, wherein the general-purpose format is a CSV (Comma Separated Values) format or an XML (Extensible Markup Language) format. A client terminal device that performs work using a database of a server computer or its own local database,
A server connection state confirmation unit for confirming whether the database of the server computer is available;
A portable data storage unit for storing portable data that is data in a general format generated based on the database of the server computer;
When the database of the server computer is not available, the format of the portable data read from the portable data storage unit is converted to the format for storing in the local database, and the format of the data acquired from the local database A data management unit for storing portable data obtained by converting the data into a general-purpose format in the portable data storage unit;
A database that stores data in a format for storing in a local database received from the data management unit in accordance with an instruction from the data management unit, and that passes data acquired from the local database to the data management unit An engine unit,
A client terminal device comprising:   When the database of the server computer is available, the data management unit converts the portable data format read from the portable data storage unit into a format for storing in the database, and performs the conversion process. 10. The client terminal device according to claim 9, wherein the converted data obtained by execution is transferred to the server computer.   10. The client terminal according to claim 9, wherein the data management unit delivers portable data read from the portable data storage unit to the server computer when a database of the server computer is available. apparatus.   The data management unit reads the portable data from the portable data storage unit when the process of storing the portable data previously executed in the portable data storage unit is completed normally, and stores the portable data stored in the portable data storage unit. 12. The client terminal device according to claim 9, 10 or 11, wherein the format is converted into a format for storing in a local database.   The data management unit further obtains data designated by the user from the database when receiving an instruction from the user in a state where the work using the database of the server computer is being performed, and the obtained data 13. The client terminal device according to claim 9, wherein the converted data obtained by converting the data into data in a general format is stored in a portable data storage unit.   Further, the data management unit, when receiving an instruction from a user in a state of performing work using the database of the server computer, is data designated by the user and is converted into a general format in the server computer. The client terminal apparatus according to claim 9, wherein the converted data is acquired from the server computer, and the acquired data is stored in a portable data storage unit.   15. The client terminal device according to claim 9, wherein the general-purpose format is a CSV (Comma Separated Values) format or an XML (Extensible Markup Language) format. The client terminal device according to any one of claims 9 to 15,
A server terminal device for managing data used by the client terminal device;
A client-server system comprising:

Images