JP2004157601A - Processing device for business form file - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a processing device for a business form file that can effectively prevent manipulation while reducing the frequency of delivery of the business form file. <P>SOLUTION: In a business form file processing system, a client saves and reuses scrambled business form files delivered from a server. The client requests the server to redeliver a business form file, (1) if the business form file saved in the client is different from the business form file in the server, (2) if the business form file is not delivered to the client, or (3) if the business form file delivered to and saved in the client remains for a given period after the preceding delivery. Especially in the third (3) case, a scrambling method different from a scrambling method at the preceding delivery is used. <P>COPYRIGHT: (C)2004,JPO

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention provides a form file processing apparatus, form file processing system, form file processing method, form file processing method, form file processing suitable for distribution, printing, and display of a form, which is a fixed form document including ruled lines and characters, and associated data. The present invention relates to a program and a recording medium.
[0002]
[Prior art]
2. Description of the Related Art Conventionally, in a form control system, in a computer system including a server and a client connected via a network such as a LAN (local area network), a WAN (wide area network), and the Internet, a server sends a request from a client. And the client prints or displays the distributed form.
[0003]
In such a form control system, printing or display processing is performed using a group of files that are always classified into fixed data such as ruled lines and data that differs for each document and are embedded in a fixed part of the data. In this specification, the above-mentioned fixed form data is referred to as “form”, and data embedded in this data (form) is referred to as “embedded data”.
[0004]
Also, the form and the embedded data are managed by the server and distributed from the server to the client, so that the client can print or display the result of the form processing using the form and the embedded data. At this time, the form and the embedded data are put together as one file, and this file is appropriately compressed or encrypted as appropriate.
[0005]
In particular, in a form distribution technique using the Web and the like whose usage range is expanding, a form file managed on the server side is distributed to the client, and the client side can use the form file even after it has been used for processing. A process is performed in which the data is not immediately deleted but is stored.
[0006]
On the client side, when a certain form is used, instead of having the server deliver the form file always, if the corresponding form file has not been delivered from the server before, or the file on the current server Only when an older form file exists on the client and the form file needs to be updated, the server can be requested to distribute the form file. By such a process, the client can use the form file stored therein until the form file once downloaded becomes necessary to be updated. Therefore, when processing the form, the amount of data to be distributed can be reduced, and the load on the communication path and the processing can be reduced.
[0007]
In this specification, the form file is not always distributed, but the client automatically requests distribution when it is needed and the server performs distribution. An operation in which the server specifies to perform or does not perform distribution and the server performs distribution in accordance with the specification is referred to as “fixed distribution”.
[0008]
Further, on the client side, a record of the distribution history of the form is stored by means such as a file or a registry in order to determine the form to be requested to be distributed to the server. In the distribution history, information such as the file name, the file size, and the file generation date and time of the distributed form is recorded.
[0009]
When it becomes necessary to use an arbitrary form file, the client requests to distribute the current server-side form file, receives a response from the server, and checks the status of the server-side form file included in the response. By requesting the server to fix-distribute only those files that need to be redistributed from the distribution history information left on its own side, only the required form files are automatically distributed, and the client Is updated.
[0010]
The embedded data file, unlike the form file, is updated in principle every time, so if it is deleted immediately after processing used for printing or display, there is no problem. Not applicable.
[0011]
In general, in a form printing / display system used for printing securities, etc., measures for preventing falsification of form data are necessary in view of the importance of printed matter. However, as described above, when the form file is continuously present in the client, there is a possibility that an unauthorized print is issued by editing it from the outside and falsifying the contents.
[0012]
Therefore, in order to prevent such tampering, the form file delivered to the client is subjected to scramble or encryption processing.
[0013]
Here, a description will be given of a securities report distribution system using a conventional Web system employing such processing.
[0014]
In this conventional system, a user sends a request from a Web browser of a client to a Web application (server application) on a server using HTTP parameters or the like, thereby creating a form file for printing securities. It requests distribution of the embedded data file and the like accompanying it.
[0015]
In this execution system, the server application prepares a specified form and other accompanying data in response to a request from the Web browser.
[0016]
Here, the client transmits the name of the form file to be processed and a flag indicating that it is desired to automatically distribute them to the server as the value of the HTTP parameter.
[0017]
The server application that receives it picks up information such as the file name, file size, and update date from the form file that it manages for the form file requested to be automatically distributed, and organizes it in an appropriate format. To the client as an information file.
[0018]
The information file is given a specific MIME type, and the client that receives it analyzes the transmitted information file using a plug-in of a Web browser that can analyze the MIME type.
[0019]
At the time of analysis, the client side retrieves the history information of the form file held so far, compares the file name, file size, update date, etc., and redistributes the form file managed by the server Determine if you need to do so.
[0020]
As a result of the determination, if there is a form file that requires redistribution, the next distribution requests that the form file determined to require redistribution be distributed not by automatic distribution but by fixed distribution. Request the server application again with the parameters.
[0021]
The server that has received it appropriately combines the requested form files and distributes them fixedly to the client.
[0022]
At this time, the server prepares a necessary form file, performs compression or encryption processing, adds header information necessary for other processing on the client side, and combines the files into one file.
[0023]
In the combined file group, whether to insert a characteristic data string (for example, a character string such as "--------------------------- separator line") Alternatively, by describing the start / end offset byte numbers of each file in the header and referring to the values, it is possible to easily disassemble each original file.
[0024]
When the client receives the delivered file, it restores the combined files separately while classifying them, saves them again in a location suitable for client-side form management, and stores the contents of the history of the managed files Is updated to the content based on the acquired file.
[0025]
After that, the client performs printing or display processing using these forms.
[0026]
Here, the form file distributed to the client has been subjected to the above-described scramble processing. To use the form for printing or display processing on the client side, the scramble must be once released each time.
[0027]
Here, a plurality of scrambling methods have been agreed between the server and the client, and information on the scrambling method is held using the first few bytes of the distributed form file.
[0028]
To process the form file on the client side, the leading few bytes are read, the scramble type agreed with the server is identified therefrom, and the form file portion is decrypted by a descrambling method suitable for that.
[0029]
A sufficient number of types of scrambling are provided to prevent malicious users from deciphering. Also, the information on the type of scramble to be written in the first few bytes is appropriately added with random number noise or the like so that it is not easily known to the user.
[0030]
In order to hold the scramble type, not only the method of the first few bytes of the file but also various methods are employed.
[0031]
[Problems to be solved by the invention]
However, if the means of the scrambling or encryption process is elucidated, the above-described tamper-proof measures become meaningless. Then, there is a problem that the longer the form file exists on the client, the higher the possibility that the scramble method or the like is analyzed becomes.
[0032]
The present invention has been made in view of the above problems, and has as its object to provide a form file processing apparatus capable of effectively preventing falsification while suppressing the number of times the form file is distributed. .
[0033]
[Means for Solving the Problems]
A form file processing apparatus according to the first invention of the present application is a form file processing apparatus for processing a form file distributed from a server. When the form file is distributed from the server, the form file is processed. File storage means for storing, when a form file is distributed from the server, history storage means for storing the history of the form file, notifying means for notifying the server of a form file to be used, Searching means for searching the history of the scheduled form file from the server, and comparing the information of the scheduled form file received from the server with the information of the scheduled form file searched from the history Means, an elapsed time determining means for determining an elapsed time since the delivery of the scheduled form file received from the server, And having a list creation means for creating a list of document files for requesting distribution against over server, and a list transmitting means for transmitting the list to the server.
[0034]
A form file processing system according to a second aspect of the present invention includes the form file processing apparatus described above and the server.
[0035]
A form file processing method according to a third invention of the present application is a form file processing method for processing a form file distributed from a server. When the form file is distributed from the server, the form file is processed. A file storing step of storing, when a form file is distributed from the server, a history storing step of storing a history of the form file; a notifying step of notifying the server of a form file to be used; A search step of searching for the history of the scheduled form file from the server, and comparing the information of the scheduled form file received from the server with the information of the scheduled form file searched from the history An elapsed time determining step of determining an elapsed time from the delivery of the scheduled use form file received from the server; And having a list generation step of generating a list of document files for requesting distribution against over server, and a list transmission step of transmitting said list to the server.
[0036]
A form file processing program according to a fourth invention of the present application is a form file processing program for causing a computer to process a form file distributed from a server, and the form file is distributed from the server to the computer. Then, when the form file is delivered from the server, a file saving procedure for saving the form file is stored, and a history saving procedure for saving the history of the form file is provided, and the form file to be used is notified to the server. A notification procedure, a search procedure for searching the history of the scheduled form file from the history, and the scheduled form searched from the information of the scheduled form file received from the server and the history A comparison procedure for comparing the information of the file with the file information of the form file to be used received from the server. Executing an elapsed time determination procedure for determining an elapsed time from the communication, a list creation procedure for creating a list of form files requesting distribution to the server, and a list transmission procedure for transmitting the list to the server. It is characterized by making it.
[0037]
A computer-readable recording medium according to a sixth invention of the present application is characterized by recording the above-mentioned form file processing program.
[0038]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, a form file processing apparatus, a form file processing system, a form file processing method, a form file processing program, and a recording medium according to an embodiment of the present invention will be specifically described with reference to the accompanying drawings.
[0039]
FIG. 1 is a block diagram showing a hardware configuration of a client (form file processing apparatus) in a form file processing system according to an embodiment of the present invention.
[0040]
The client is composed of, for example, a computer system, and includes a CPU (central processing unit) 12, a memory 13 such as a RAM and a ROM as a main storage device, an FD drive 15a for driving an FD (flexible disk) as an external memory, and an external An HD drive 15b having an HD (hard disk) as a memory; an input device 11 having a keyboard (K / B) and a pointing device such as a mouse; a display device 14 such as a CRT display; a printing device 17 such as a printer; An external input / output interface (I / O I / F) 16 connected to a network 18 is provided as a main part.
[0041]
The client operates when the CPU 12 executes, for example, a basic I / O program, an OS (operating system), and a form file processing program. The basic I / O program is written in the memory 12, and the OS is written in the HD fixed to the HD drive 15b. When the power of the client is turned on, the OS is read from the HD into the RAM 13 by the IPL (initial program loading) function in the basic I / O program, and the operation of the OS is started. The processing program causes the CPU 12 to execute a part of the processing shown in FIGS. 4 and 5, for example, and is coded. The processing program and its related data are recorded on, for example, the FD. The other parts of the processing shown in FIGS. 4 and 5 are executed by, for example, a server.
[0042]
FIG. 2 is a schematic diagram showing the configuration of the contents of data recorded on the FD. The data 30 includes, for example, volume information 31, directory information 32, a processing program execution file 33, a processing program related data file 34, and the like.
[0043]
The processing program and related data recorded on the FD can be loaded into the computer system (client) through the FD drive 15a as shown in FIG. When this FD is set in the FD drive 15a, this processing program and related data are read from the FD under the control of the OS and the basic I / O program, and are loaded into the memory 13, for example, the RAM, and become executable.
[0044]
FIG. 3 is a schematic diagram showing a memory map when the processing program is loaded into the memory 13 and becomes executable. The memory 13 stores, for example, a basic I / O program 41, an OS 42, a processing program 43, a data area 44, a work area 45, and the like.
[0045]
Note that the processing program and related data may be temporarily stored (installed) in the HD in the HD drive 15 from the FD, and loaded into the memory 13 from the HD when the processing program is executed. Further, the medium on which the processing program is recorded may be a CD-ROM, an IC memory card, or the like in addition to the FD. Further, the present processing program may be stored in a read-only memory 13, for example, a ROM, configured to form a part of a memory map, and directly executed by the CPU 12.
[0046]
In the processing system according to the present embodiment, a plurality of clients as described above are mutually connected via an external network 18, and a server is connected to the external network 18.
[0047]
Next, the operation of the form file processing system including the client configured as described above will be described with reference to the flowcharts of FIGS. 4 and 5 are flowcharts showing the operation of the form file processing system according to the embodiment of the present invention.
[0048]
First, as shown in FIG. 4, when processing a single or a plurality of forms, the client transmits one or more necessary form file names to the server together with a flag for designating automatic distribution (step s1). ).
[0049]
Upon receiving the flag and the form file name from the client, the server searches the form file managed by the server for a file with the specified name, and acquires the size and update date of the file (step s2). ).
[0050]
Next, the server lists the name, size, and update date of the obtained file as a file information list in an appropriate format, and specifies the MIME type to be processed by the plug-in for parsing the file information list on the client. Is transmitted to the client (step s3).
[0051]
When the plug-in of the client receives the file information list, it stores the content in a memory in a format that is easy to use. At the same time, the plug-in of the client opens a history file that retains the file information distributed so far as a history, and expands the contents on the memory in a format that is easy to use (step s4).
[0052]
This history file is stored, for example, in a position where it is difficult for the user to search in a description format that is difficult to decipher. In the history file, the name, size, update date, date and time of distribution of the file distributed so far, and the scramble method of the file are written.
[0053]
After expanding the history file as described above, the client secures and initializes a list memory area for storing the file name requested for distribution (step s5).
[0054]
The client extracts the file names described in the file information list sent from the server one by one, and searches the history file for information on the file having the same name (step s6).
[0055]
If a file having the same name is found as a result of the search in step s6, the size and update date (file information) of the file when it was previously distributed are acquired (step s7).
[0056]
It is checked whether the size and update date obtained from the history file match those in the file information list sent from the server (step s8). If not, this file should be distributed again. Is determined, and the name of this file is added to the previously reserved file name list for distribution request, that is, the file name list initialized in step s5 (step s9).
[0057]
On the other hand, if a file with the same name is not found as a result of the search in step s6, it is determined that the file has not been distributed yet, and Then, the name of the file is added (step s9).
[0058]
If the target file is found as a result of the search in step s6, and the file size and update date match those in the file information list transmitted from the server, the previous distribution of the file is performed. The date and time are extracted from the history file expanded in the memory in step s4 (step s10).
[0059]
Thereafter, the previous distribution date and time are compared with the current date and time to check whether or not the previous distribution date and time is a predetermined period or more before the present (step s11). That is, in this step s11, the elapsed time from the previous distribution of the form file to be used received from the server is determined.
[0060]
As a result of the comparison in step s11, if it is determined that the current time is a predetermined period or more, the name is added to a file name list for which distribution request is made to distribute this file again. At this time, information on the scramble method applied to the file when the file was previously distributed is also added to the file name list for which distribution is requested (step s12).
[0061]
Note that the value of the “certain period” as a criterion for the determination in step s11 is a value determined by the processing system and settable by the system administrator. Also, this value is stored as a value that can be accessed by the client helper application in a description format that is difficult for the user to search in a place that is difficult to search.
[0062]
Then, the process from step s6 to step s12 is repeated until the end of the file information list transmitted from the server is reached. If the end is reached, the process proceeds to the next processing (step s13).
[0063]
In the next process, the file name list storing the file name requested for distribution is converted into a format understandable by the server and transmitted to the server (step s14). At this time, even if the form file requested to be distributed is not listed in the file name list, other information, that is, information used for printing or display setting in the subsequent processing, etc. is always transmitted.
[0064]
Thereafter, as shown in FIG. 5, the server receiving the request in step s14 from the client reads the received information. Then, with respect to the form file requested to be distributed, the information is first extracted one by one for the file requested to be distributed, and it is determined whether the list is still left in the server (step s15).
[0065]
If the list remains, that is, if the requested file list is not completed, whether the previous scrambling method has been specified in step s12 for the form file, that is, whether the scramble information is included Is determined (step s16).
[0066]
If the previous scramble method has been designated, in this distribution, a scramble format different from that method is selected, and the scramble is applied to the form file (step s17). On the other hand, if the previous scramble method is not specified, an arbitrary scramble format is selected and the scramble is applied to the form file (step s18).
[0067]
Thereafter, the scrambled form files are combined and distributed to the client (step s19).
[0068]
After receiving the distributed file, the client first stores the date and time at which the distributed file was received in a memory (step s20).
[0069]
Thereafter, the client decomposes the distributed combined file into original files, and obtains the size, update date, and scramble method for each file (step s21).
[0070]
Subsequently, the client develops the history file of the distributed file in the memory as in step s4 (step s22).
[0071]
Then, the client then takes out the form files one by one from the distribution file and performs the processing. Determine if any files remain to be processed. (S23)
[0072]
If it is determined in step s23 that "the file remains", the information of the file is compared with the information of the history file developed in step s22 (step s24). Is changed again in the memory (step s25). At this time, the received date and time of the stored file is entered in step s20 as the distributed date and time.
[0073]
On the other hand, if there is no change as a result of the comparison in step s24, the process returns to step s23.
[0074]
The processing from step s23 to step s25 is repeated until the file is exhausted, that is, until it is determined in step s23 that "the file information has been completed".
[0075]
Then, when all the files have been processed, the client writes the history file expanded on the memory to an actual file (step s26). At this time, this file is desirably scrambled and stored like the form file so that the information is not recognized by a malicious user.
[0076]
When the above processing is completed, it becomes possible to perform the form printing or display processing while decrypting the form files one by one.
[0077]
Next, printing or display processing by the client will be described. FIG. 6 is a flowchart showing a print or display process.
[0078]
When printing or displaying, when using each form file, while opening the scrambled form file (step s31), the scramble method recorded in the item of the file described in the history file is checked. Acquire (step s32). Then, the obtained scramble method is compared with the actual file scramble method (step s33).
[0079]
If the scramble method is different, there is a gap between the history and the stored form file, so that it is regarded as an improper state and the process is interrupted (step s34).
[0080]
On the other hand, if the scramble methods match, the process is continued as it is (step s35). That is, processing such as output on a printing device or a display device is performed.
[0081]
According to such an embodiment, malicious tampering can be prevented while suppressing unnecessary duplicate distribution of the form file.
[0082]
In the above-described embodiment, the malicious alteration of the user is prevented by scrambling the form file. However, the same effect can be obtained by encrypting the form file.
[0083]
In this case, for example, if public key encryption is used, it is preferable to generate a public key on the client side and pass it to the server for encryption.
[0084]
As described above, the embodiment of the present invention can be realized by a computer executing a program. Further, means for supplying the program to the computer, for example, a computer-readable recording medium such as a CD-ROM in which the program is recorded, or a transmission medium such as the Internet for transmitting the program is also applied as an embodiment of the present invention. Can be. Further, the above-described program can also be applied as an embodiment of the present invention. The above programs, recording media, transmission media, and program products are included in the scope of the present invention.
[0085]
Examples of embodiments of the present invention are listed below.
[0086]
(Embodiment 1) A form file processing apparatus for processing a form file distributed from a server,
When the form file is distributed from the server, a file storage unit for storing the form file,
When the form file is distributed from the server, history storage means for storing the history of the form file,
Notifying means for notifying the server of a form file to be used,
Searching means for searching the history of the scheduled form file from the history, information of the scheduled form file received from the server, and information of the scheduled form file searched from the history; Means for comparing
Elapsed time determination means for determining an elapsed time from the delivery of the scheduled form file received from the server,
List creation means for creating a list of form files requesting distribution to the server;
List transmitting means for transmitting the list to the server;
A form file processing apparatus comprising:
[0087]
(Embodiment 2) An embodiment according to the first embodiment, further comprising a decomposing means for decomposing the combined data into the plurality of form files when the server has delivered combined data obtained by combining a plurality of form files. Processing device for the described form file.
[0088]
(Embodiment 3) The history stored in the history storage unit includes a method of scrambling the form file,
First acquisition means for acquiring a method of scrambling a form file to be used stored in the file storage means;
Second acquisition means for acquiring, from the history, a method of scrambling the form file to be used;
Comparing means for comparing the scrambling method obtained by the first obtaining means with the scrambling method obtained by the second obtaining means;
As a result of the comparison by the comparing means, suspending means for suspending the processing when it is determined that there is a mismatch,
3. The form file processing device according to the first or second embodiment, further comprising:
[0089]
(Embodiment 4) A form file processing system comprising: the form file processing device according to any one of Embodiments 1 to 3; and the server.
[0090]
(Embodiment 5) The server:
Information transmitting means for transmitting the form file information notified by the notifying means to the form file processing device,
Scramble storage means for storing a plurality of types of scramble methods applied to the form file,
Selecting one scrambling method from the plurality of types of scrambling methods, scrambling means for scrambling the form file to be distributed to the form file processing device,
Distribution means for distributing the scrambled form file to the form file processing device,
The form file processing system according to the fourth embodiment, further comprising:
[0091]
(Embodiment 6) A processing method of a form file for processing a form file distributed from a server,
When the form file is distributed from the server, a file saving step of saving the form file,
When a form file is distributed from the server, a history saving step of saving the history of the form file,
A notification step of notifying the server of a form file to be used,
A search step of searching the history of the scheduled form file from the history, and information of the scheduled form file received from the server and information of the scheduled form file searched from the history. A comparison step of comparing
An elapsed time determination step of determining an elapsed time since the delivery of the scheduled form file received from the server;
A list creation step of creating a list of form files requesting distribution to the server,
A list transmitting step of transmitting the list to the server;
A method of processing a form file, comprising:
[0092]
(Embodiment 7) An embodiment 6 further comprising a disassembling step of disassembling the combined data into the plurality of form files when combined data obtained by combining a plurality of form files is distributed from the server. How to process the described form file.
[0093]
(Embodiment 8) The history stored in the history storing step includes a method of scrambling the form file,
A first obtaining step of obtaining a scramble method of a form file to be used stored in the file storing step;
A second acquisition step of acquiring, from the history, a method of scrambling the form file to be used;
A comparing step of comparing the scrambling method obtained in the first obtaining step with the scrambling method obtained in the second obtaining step;
As a result of the comparison in the comparison step, an interruption step of interrupting the processing when it is determined that the two do not match,
8. The method for processing a form file according to the sixth or seventh embodiment, comprising:
[0094]
(Embodiment 9) A form file processing program for causing a computer to process a form file distributed from a server,
To the computer,
When the form file is distributed from the server, a file saving procedure for saving the form file,
When a form file is distributed from the server, a history saving procedure for saving the history of the form file,
A notification procedure for notifying the server of a form file to be used,
A search procedure for searching the history of the scheduled form file from the history, information of the scheduled form file received from the server, and information of the scheduled form file searched from the history. A comparison procedure for comparing
An elapsed time determination procedure for determining an elapsed time since the delivery of the scheduled form file received from the server,
A list creation procedure for creating a list of form files requesting distribution to the server,
A list transmission procedure for transmitting the list to the server;
And a form file processing program.
[0095]
(Embodiment 10) A recording medium recording a form file processing program for causing a computer to process a form file distributed from a server,
To the computer,
When the form file is distributed from the server, a file saving procedure for saving the form file,
When a form file is distributed from the server, a history saving procedure for saving the history of the form file,
A notification procedure for notifying the server of a form file to be used,
A search procedure for searching the history of the scheduled form file from the history, information of the scheduled form file received from the server, and information of the scheduled form file searched from the history. A comparison procedure for comparing
An elapsed time determination procedure for determining an elapsed time since the delivery of the scheduled form file received from the server,
A list creation procedure for creating a list of form files requesting distribution to the server,
A list transmission procedure for transmitting the list to the server;
A computer-readable recording medium on which is recorded a form file processing program for executing a form file.
[0096]
【The invention's effect】
As described above, according to the present invention, a form file that is automatically distributed is not changed and the like is not generated. However, it is possible to forcibly change the method of scrambling or encryption every predetermined time and redistribute it. Therefore, in a situation where the same form file is concentrated and used many times in form processing within a certain time, the form file can be distributed only once at the beginning, and after that, After a certain period of time, the form file can be redistributed again by the server. Therefore, it is possible to overwrite with a form file in which the scramble method has been changed without giving any falsification. As a result, falsification can be effectively prevented while suppressing the number of times of distribution of the form file.
[Brief description of the drawings]
FIG. 1 is a block diagram showing a hardware configuration of a client (form file processing apparatus) in a form file processing system according to an embodiment of the present invention.
FIG. 2 is a schematic diagram showing the configuration of the content of data recorded on an FD.
FIG. 3 is a schematic diagram showing a memory map when the processing program is loaded into a memory 13 and becomes executable.
FIG. 4 is a flowchart showing the operation of a form file processing system according to the embodiment of the present invention.
FIG. 5 is a flowchart showing the operation of a form file processing system according to the embodiment of the present invention.
FIG. 6 is a flowchart illustrating print or display processing.
[Explanation of symbols]
11; input device
12; CPU
13; memory
14; display
15a; FD drive
15b; HD drive
16; I / O I / F
17; Printer
18; Network

Claims (1)

A form file processing device for processing the form file distributed from the server,
When the form file is distributed from the server, a file storage unit for storing the form file,
When the form file is distributed from the server, history storage means for storing the history of the form file,
Notifying means for notifying the server of a form file to be used,
Searching means for searching the history of the scheduled form file from the history, information of the scheduled form file received from the server, and information of the scheduled form file searched from the history; Means for comparing
Elapsed time determination means for determining an elapsed time from the delivery of the scheduled form file received from the server,
List creation means for creating a list of form files requesting distribution to the server;
List transmitting means for transmitting the list to the server;
A form file processing apparatus comprising:

Images