JP2007272315A - File management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To quickly display registered data in the order of file numbers. <P>SOLUTION: Registration data are registered in the order of registration in a merchandise database constructed in a flash ROM 108, and file number data included in the registration data are registered in the order of file numbers in a file number database constructed in the flash ROM 108. When the data registered in the merchandise database are displayed in a list, the file numbers are read from the file number database, and the registration data corresponding to the read file numbers are retrieved and acquired from the merchandise database in the order of the read file numbers and displayed. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a file management system, and more particularly to a file management system that searches and outputs registered data.

  Conventionally, information about the display position in the screen is stored as a location code in a table file, and the location code is added to the screen display data to be displayed based on the table file, and the screen display data to which the location code is added is grouped. By editing items and executing display commands on group items, the screen display data can be displayed in a lump so that the processing speed can be improved without increasing the number of executions of display commands. (For example, refer to Patent Document 1).

Japanese Patent Laid-Open No. 5-224852

  However, in the background art, after registering data to which a file number is added, it has not been possible to perform processing for searching and displaying data in numerical order at high speed.

  The present invention has been made in view of such a situation. Even when data with file numbers added is registered in a random order regardless of the file number, the data is quickly searched and displayed in the order of the file numbers. Is to be able to.

The file management system according to claim 1, wherein the file number data indicating the file number and the input means for inputting the product data corresponding to the file number data are associated with the file number data input by the input means and the product data. Product data registering means for registering in the first database in the input order, and file number registering means for registering only the file number data while rearranging the file numbers in ascending order in the second database. It is characterized by.
Further, when displaying a list of product data registered in the first database on a predetermined display device in the order of file numbers, the file number data is sequentially read from the second database, and the product corresponding to the read file number data An acquisition unit that searches and acquires data from the second database and an output unit that outputs the product data acquired by the acquisition unit can be further provided.

According to the file management system of the present invention, even when data with file numbers added is registered in a random order regardless of the file number, the file numbers are registered in ascending order, so that data can be searched quickly in the order of the file numbers. can do.
Further, since the data can be quickly searched in the order of the file numbers, the data can be quickly displayed on the predetermined display device in the order of the file numbers.

  FIG. 1 is a block diagram illustrating a configuration example of an embodiment of a printer to which the present invention is applied. As shown in the figure, the present embodiment operates in accordance with a control program stored in a flash ROM (Read Only Memory) 108 described later, controls each unit, and executes various processes. ) 101, a RAM (Random Access Memory) 109 that stores various data necessary for the CPU 101 to execute processing, a motor 106 that drives a conveyance unit that conveys paper under the control of the CPU 101, and a conveyance unit Lights at a predetermined timing under the control of the thermal head 107 that prints predetermined print data on the conveyed paper at a predetermined timing, a communication interface 102 that controls transmission / reception of data to / from an external device, and the CPU 101. In addition, an LED (Light Emitting Diode) 103 that transmits predetermined information by turning it off, An operation unit 104 for inputting commands and data, a removable card 110 having a memory for storing various data, a flash ROM 108 for storing a control program executed by the CPU 101, and an LCD ( Liquid Crystal Display) 105 and the like. The communication interface 102 is RS232C, Centronics, wireless, or the like. The operation unit 104 includes a numeric keypad and a touch panel. The touch panel is composed of a transmissive member and is placed over the LCD 105. Therefore, when a predetermined part of the touch panel corresponding to the display position of the selection item or button displayed on the LCD 105 is touched by the user, the CPU 101 recognizes which part of the touch panel is touched. Based on the display content of the LCD 105 and the position of the touched portion of the touch panel, the selection operation or button operation of the selection item by the user is recognized.

  Next, the operation of the present embodiment will be described with reference to the flowchart of FIG. First, in step S <b> 1, the CPU 101 determines whether data registration is instructed based on the operation of the operation unit 104 by the user. As a result, if it is determined that data registration has been instructed, the process proceeds to step S2.

  In step S <b> 2, the CPU 101 once stores the registration data including the file number and the product data input by operating the operation unit 104 by the user or the registration data transmitted from the personal computer or the like via the communication interface 102. To supply and memorize.

  Next, in step S <b> 3, the registration data stored in the RAM 109 is registered in the product database constructed in the flash ROM 108 in the order in which the registration data is input, under the control of the CPU 101.

  Next, in step S <b> 4, the CPU 101 determines whether a file number database has already been constructed in the flash ROM 108. As a result, if it is determined that the file number database has already been constructed in the flash ROM 108, the process proceeds to step S5. On the other hand, if it is determined that the file number database has not yet been built in the flash ROM 108, the process proceeds to step S6.

  In step S5, under the control of the CPU 101, file number data indicating the same file number as the file number included in the registration data registered in the product database in step S3 is registered in the file number database so as to be arranged in the file number order. . That is, the file number data registered in the file number database is always rearranged so as to be arranged in ascending order. Thereafter, the process proceeds to step S13.

  On the other hand, in step S 6, a file number database is newly created in the flash ROM 108 under the control of the CPU 101. That is, the file number included in each registration data registered in the product database is read and registered in the file number database in ascending order. Thereafter, the process proceeds to step S13.

  If it is determined in step S1 that data registration is not instructed, the process proceeds to step S7, and the CPU 101 determines whether or not deletion of registered data is instructed. As a result, if it is determined that deletion of registered data has been instructed, the process proceeds to step S8.

  In step S8, a file number is input from the operation unit 104, or registration data to be deleted is specified by a cursor 129 (FIG. 4) or the like on a product data list display screen (FIG. 4) described later. The CPU 101 recognizes the file number of registration data to be deleted.

  Next, in step S9, the CPU 101 deletes the registration data designated to be deleted from the product database. Then, it progresses to step S4, it is determined whether a file number database exists, and a file number database is updated when a file number database exists. That is, the file number data corresponding to the file number included in the deleted registration data is deleted from the file number database. Thereafter, the process proceeds to step S13.

  If the file number database does not exist, a new file number database is created based on the file number included in the registration data registered in the product database. This file number database does not include the file number included in the registration data deleted in step S9. Thereafter, the process proceeds to step S13.

  If it is determined in step S7 that deletion of registration data has not been instructed, the process proceeds to step S10, and the CPU 101 determines whether or not a list display of registration data has been instructed. As a result, if it is determined that the list display of registered data is not instructed, the process proceeds to step S12, and after other processes are executed, the process proceeds to step S13. On the other hand, if it is determined that the list display of registered data is instructed, the process proceeds to step S11.

  In step S11, a list display process of registered data, which will be described later with reference to the flowchart of FIG. 3, is executed. Thereafter, the process proceeds to step S13.

  In step S13, it is determined whether an instruction to end the process has been issued. As a result, when it is determined that the end of the process is not instructed, the process returns to step S1 and the processes after step S1 are repeatedly executed. On the other hand, if it is determined that the end of the process has been instructed, the present process ends.

  Next, the registration data list display process executed in step S11 of FIG. 1 will be described in detail with reference to the flowchart of FIG.

  First, in step S21, the CPU 101 determines whether or not the file number database already exists in the flash ROM 108. As a result, if it is determined that the file number database does not exist in the flash ROM 108, the process proceeds to step S22. A file number database is newly created in the flash ROM 108. Thereafter, the process proceeds to step S23.

  On the other hand, if it is determined that the file number database exists in the flash ROM 108, the process proceeds to step S23, and file number data indicating the file number is read from the file number database under the control of the CPU 101. The read file number data is supplied to the RAM 109 and stored therein.

  Next, in step S24, the CPU 101 executes a data list display process. That is, the CPU 101 reads out the file number data stored in the RAM 109 by the number that can be displayed on the screen of the LCD 105. Next, registration data corresponding to the read file number data is retrieved from the product database, and is temporarily stored in the RAM 109. Thereafter, the CPU 101 generates display data for displaying the registration data supplied to the RAM 109 and supplies the display data to the LCD 105. The LCD 105 displays the display data supplied from the CPU 101.

  FIG. 4 shows an example of a product data list display screen. As shown in FIG. 4, registration data is displayed in order of file numbers on the product data list display screen. Also, on this screen, a “product data list display screen” indicating the title of the screen, a file number input field for number search, a “cursor up” button 121 operated when moving the cursor upward, A “cursor down” button 122 that is operated when moving the cursor downward, an “add” button 123 that is operated when adding data, and a “correct” button 124 that is operated when correcting registered data. , “Delete” button 125 operated when deleting registered data, “Back” button 126 operated when returning to the previous screen, “Previous” button 127 operated when returning to the previous page, Next A “next” button 128 or the like operated when moving to the page is also displayed.

  That is, the display data generated by the CPU 101 includes, as shown in FIG. 4, a “product data list display screen” indicating the title of the screen, a file number input field for number search, and when moving the cursor upward. The “cursor up” button 121 operated when the cursor is moved downward, the “cursor down” button 122 operated when moving the cursor downward, the “add” button 123 operated when adding data, and the registered data “Correct” button 124 operated when correcting, “Delete” button 125 operated when deleting registered data, “Return” button 126 operated when returning to the previous screen, and returning to the previous page Data for displaying a “Previous” button 127 that is operated when the “Next” button 128 is operated when moving to the next page is included.

  Next, in step S <b> 25, the CPU 101 determines whether or not the page switching key (“Previous” button 127 or “Next” button 128) has been operated. As a result, if it is determined that the page switching key has been operated, the process proceeds to step S26. On the other hand, if it is determined that the page switching key has not been operated, the process proceeds to step S27.

  In step S26, the CPU 101 reads the file number of the registered data to be displayed on the page to be switched next from the file number database, and obtains it from the file number data stored in the RAM 109.

  Next, the process returns to step S24, and the data list display process is executed based on the file number data acquired in step S26. That is, as described above, the CPU 101 retrieves and acquires registration data corresponding to the file number data acquired in step S26 from the product database, and temporarily stores it in the RAM 109. Thereafter, the CPU 101 generates display data for displaying the registration data supplied to the RAM 109 and supplies the display data to the LCD 105. The LCD 105 displays the display data supplied from the CPU 101. In this way, page switching is performed.

  Next, in step S27, it is determined whether or not the user has operated the operation unit 104 to instruct the end of the product data list display process. As a result, when it is determined that the end of the product data list display process is not instructed, the process returns to step S24, and the processes after step S24 are repeatedly executed. On the other hand, if it is determined that the end of the product data list display process has been instructed, this process ends, and the process proceeds to step S13 in FIG.

  By operating at least one of the “cursor up” button 121 and the “cursor down” button 122 displayed on the product data list display screen shown in FIG. 4, the cursor 129 displayed on the screen is displayed as desired registration data. The registered data can be deleted by moving it up and selecting it, and operating the “delete” button 125.

  Further, by operating at least one of the “cursor up” button 121 and the “cursor down” button 122, the cursor 129 displayed on the screen is moved and selected onto desired registration data, and the “correct” button 124 is selected. After the operation, the operation unit 104 can be operated to correct the registered data.

  In addition, after the “add” button 123 is operated, desired data can be newly registered by operating the operation unit 104.

  FIG. 5 shows a data configuration example of a product database constructed in the flash ROM 108 or the like. As shown in the figure, the product database is composed of one or a plurality of data files (records). Each data file includes a file number indicating the number of the data file, the product name of the product constituting the product data, and the price. And each item such as raw materials. Each data file is registered in the product database in the order of registration.

  In this example, the product database includes a data file including a file number “0005”, a product name “E lunch box”, a price “350 yen”, a raw material “rice,...”, A file number “0002”, a product name. Data file consisting of “B lunch”, price “450 yen”, raw material “rice, ...”, file number “0004”, product name “D lunch”, price “400 yen”, raw material “rice, ...” .., A file number “0001”, a product name “A bento”, a price “500 yen”, a raw material “rice,...”, A data file “File” “0003”, a product name “ Data file consisting of “C lunch box”, price “600 yen”, raw material “rice, ...”, file number “0006”, product name “Tamago Sand”, price “200 yen”, raw material A data file consisting of “bread,...”, A file number “0008”, a product name “vegetable sandwich”, a price “210 yen”, a raw material “bread,. ”, A product name“ ham sand ”, a price“ 200 yen ”, and a data file including raw materials“ bread,... ”Are registered in this order.

  FIG. 6 shows a data configuration example of a file number database constructed in the flash ROM 108 or the like. As shown in the figure, the file number database is composed of one or a plurality of data files (records), and each data file is composed only of items corresponding to the file numbers of the respective data files of the product database.

  In the file number database, the file number data corresponding to the file numbers included in the data file registered in the product database is rearranged and registered in ascending order.

  In this way, the file numbers of the registration data of the product database are arranged in the order of registration, but the file numbers of the file number database are always arranged in ascending order, and are registered in the file number database. By searching and acquiring registration data in the product database in the order of file numbers, the registration data can be quickly displayed in the order of file numbers. The same applies when the file numbers registered in the file number database are not consecutive.

  It should be noted that the configuration and operation of the above-described embodiment are examples, and it goes without saying that they can be changed as appropriate without departing from the spirit of the present invention.

  As an application example of the present invention, for example, the present invention can be applied when registering and searching various data as well as product data.

It is a block diagram which shows the structural example of one embodiment of this invention. It is a flowchart for demonstrating operation | movement of embodiment of FIG. It is a flowchart for demonstrating the detailed process sequence of the list display process of FIG. It is a figure which shows the example of a goods data list display screen. It is a figure which shows the structural example of a goods database. It is a figure which shows the structural example of a file number database.

Explanation of symbols

101 CPU
102 Communication interface 103 LED
104 Operation unit 105 LCD
106 Motor 107 Thermal head 108 Flash ROM
109 RAM
110 Card 121 “Cursor up” button 122 “Cursor down” button 123 “Add” button 124 “Modify” button 125 “Delete” button 126 “Back” button 127 “Previous” button 128 “Next” button 129 Cursor

Claims (2)

Input means for inputting file number data indicating a file number and product data corresponding to the file number data;
Product data registration means for associating the file number data input by the input means with the product data and registering them in the first database in the order of input;
A file management system comprising: file number registration means for registering only the file number data while rearranging the file numbers in the second database so that the file numbers are arranged in ascending order. When displaying the list of product data registered in the first database on a predetermined display device in the order of the file number data, the file number data is read out from the second database in order, and the read file number Obtaining means for retrieving and obtaining the product data corresponding to data from the second database;
The file management system according to claim 1, further comprising: an output unit that outputs the product data acquired by the acquisition unit.

Images