JP2000222494A - Method and system for preparing form, and storage medium storing computer readable program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To make surely updatable form information without human intervention by comparing the acquired date and time of preparation with the date and time of preparation added to the form information and acquiring the form information from a server when it is judged that the acquired date and time of preparation is newer. SOLUTION: First of all, an instructed form file is acquired, the name of that form file is interpreted and it is identified whether the file is introduced to a client or not. Comparison with a master file installed to the server is performed locally, namely, in the case of existing in a form cache file 113 of a client. The date and time of preparation of the form file are inquired to the server and the dates and times of preparation are mutually compared. When the file installed to the server is a version having the same date and time of preparation as the client, that file is utilized as it is but when the form file of the server is updated into new version, the required form file is transferred from the server.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an apparatus and a method for creating a form including, for example, a client and a server arranged on a network, and a storage medium storing a computer-readable program.

[0002]

2. Description of the Related Art In Japan, details of contracts and transactions are often described in a form. In transactions with insurance and financial institutions, a method of printing ruled lines and graphics corresponding to the type of contract on paper in advance and embedding and printing customer information at the time of contract is widely adopted. In industries where there are many types of products such as life insurance and non-life insurance, the types of forms used are also large, and the forms to be printed and prepared in advance are also various. In recent years, instead of the preprinting method of preparing a form in advance, a form creation system that prints information such as ruled lines and trademarks on blank paper at the same time as embedded data to finish the form has been put to practical use. Such a form printing / browsing system uses a form information file describing the form of the form and a field data file describing customer data to be embedded in the frame of the form. Form information should be prepared for each type of form, and necessary information is installed and used in each host computer. For the field data, an operator operating the host inputs customer information and the like via a data input application, and a form is created based on the data.

[0003] There are times when a form needs to be changed in accordance with changes in the product structure, social environment, legal system, and the like. Even for small changes such as changes in address notation or trademark, all forms must be recreated with the preprint method. Form sheets printed so far have been discarded, and the cost of incurring a new piece of paper has to be reprinted.

On the other hand, in a form printing / browsing system, form information is output in superimposition on field data at the time of final form printing. Even if there is a change in the form, it is possible to change the appearance without wasting paper as long as it is updated to the latest form information. To change the appearance of a report,
Update the form information file and create a field data file for the new form.

[0005] Generally, a department that manages the format of a form is located in a company and directs the updating of forms. New form information files are distributed to all branches, calling for updates to the format after a certain transition period, and fixed dates are being changed all at once. Companies with branches and sales offices nationwide could also distribute form information files and share data using a computer network that connects them.

[0006]

However, there is an aspect that the network is not effectively used for distributing form information of a form. A network is used for updating and distributing the form information file. In the updating, an operator often replaces the form information file with new form information distributed using the network on the day of the update. As described above, since the form is to be updated all company-wide because of manual intervention, there is a possibility that a time lag or an error may occur in updating manually by the operator.

[0007] On the other hand, there is also an operation in which a network client accesses a server and obtains form information every time a form is used without manual intervention. The latest version is always registered to all clients,
Frequent access to the server reduces network efficiency.

As described above, in a system for distributing form information via a network, there is a problem that the form information is not reliably updated or the network is congested in order to surely update the form. There was a point.

[0009] The present invention has been made in view of the above conventional example, and can reliably update form information without manual intervention.
Moreover, it is an object of the present invention to provide a form creation method and system that do not impose a heavy load on a network.

[0010]

In order to achieve the above object, according to the present invention, the date and time of creation of a form data file published on a server are compared with those stored on a client, and the data on the server is newly updated. If it has, it is determined that it has been updated, and it is read. The updated file is transferred from the server to the client, and as a result, the latest form information is always introduced to the client.
No file transfer is performed while no update is performed. In order to check the date and time, the server inquires about the date and time when the form information file was created. The information returned from the server has a sufficiently small amount of communication compared to transferring a file, and the time required for exchanging information is short. That is, it is possible to keep the amount of communication flowing through the network small while always maintaining the latest form information. When the field data is read from the server, it is transferred from the server each time it is used.

Alternatively, the present invention has the following configuration. In other words, a form creation method for acquiring form information from a server connected via a network and overlaying the form with field data to print the form information, including a determination step of determining the presence or absence of designated form information, and form information In the case, an acquisition step of acquiring the creation date and time of the file of the same name from the server, a comparison step of comparing the acquired creation date and time with the creation date and time attached to the form information,
A step of acquiring the form information from the server if the comparison step determines that the creation date and time acquired in the acquisition step is newer.

Preferably, the method further comprises the step of reading out the field data from the server when the field data held by the server is designated.

Preferably, the form information is composite form information obtained by combining part forms, and in the obtaining step, creation dates and times of all part forms included in the composite form information are obtained.

Preferably, in the comparing step,
If it is determined that the creation date and time obtained in the obtaining step is newer, all the component forms included in the composite form are obtained from the server by the obtaining step.

Preferably, when the field data is read from a server, the field data is
Delete after use.

[0016]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS [First Embodiment] FIG. 9 is a view / form view for explaining a form creation system according to the present invention.
FIG. 1 is a conceptual diagram of a printing system. Here, a form creation system in which branch offices, sales offices, and the like in various parts of a company are connected by a computer network is assumed. FIG. 9 shows one of the branches. Computer 90
1, 902, 903, 904, 905 are network 9
00 tied. The network 900 is also connected to a network such as a head office (not shown) via a public line or the like. Computers 901 to 905 are computers having general functions and uses, and
Reference numeral 01 denotes a server, and the computers 902 to 905 have a client role.

FIG. 10 shows computers 901, 902, 9
It is a block diagram which shows schematic structure of 03,904,905. The CPU 1001 is an HD (hard disk) 1005
And executes control to temporarily store information, files, and the like necessary for program execution in the RAM 1003.
The RAM 1003 functions as a main memory, a work area, and the like for the CPU 1001. The ROM 1004 stores programs such as a basic I / O program, and various data such as font data and template data used for document processing. The operator looks at the CRT 1008 and
09, etc., and instructs creation of a form, overlay printing, and the like. The computer is connected to the network by the communication unit 1010.

FDD (Floppy Disk Drive) 1
006 can load a program or the like stored in an FD (floppy disk) 1007 into the computer system as shown in FIG. The FD 1007 stores a server and client program of the form browsing / printing system in which the form creation method described in the present embodiment is mounted, and link data, and the contents are shown in FIG.

In FIG. 6, reference numeral 600 denotes the data content of the FD 1007. The data content has several structures,
Reference numeral 601 denotes volume information indicating FD information.
Reference numeral 2 denotes directory information indicating an arrangement of files.
Reference numeral 03 denotes a server program of a form creation system in which the form creation method described in this embodiment is introduced, and reference numeral 604 denotes a client program. Some related data are also F
D1007 and expanded to the related data 605. In FIG. 6, a program for the server and a program for the client are stored in the same FD. However, it is possible to introduce an appropriate program according to the purpose of use of the computer to be used.

FIG. 8 is a diagram for explaining how a form is created by superimposing form information and print data. The form is composed of two types of files. The form information file is a file in which ruled lines, figures, and fixed character strings for creating the form 801 are described. The field data file is created according to the form information file, and is described in the order in which numerical and character data is embedded or by specifying a variable name. The print data 802 is one example, and is created based on field data. The field data file is created by an application (not shown) on a client. For example, if the application is operated at the point of contact with the customer,
It is assumed that the application inputs the contract details and customer information and instructs the creation of a form as it is.

As shown in FIG. 8, it is the form creation system that interprets the field data file according to the form information described in the form information file, embeds the field data value in the form, and creates the form 803. The principle of operation.

Although FIG. 8 shows the form 801 as a single form information, a plurality of forms may be overlapped to form one form. Such a form is called a composite form, and a form that forms the composite form is called a part form. In the composite form, the component form contains image information as shown in FIG. 8, but the composite form data itself only has a combination of the component forms as its contents, and does not include the image information.

In the form creation system of this embodiment, a file is placed on a server 901 on a network 900,
It is characterized by being transferred to a client as needed. Always keep the latest form information file and field data file on the server. The form information file is updated according to changes in the product structure, the time of day, the situation of the forest association, and the legal system. Data commonly used by branches, data that requires complicated calculations, and field data that is managed in a company-wide manner are also placed on a server and can be transferred in response to a request from a client.

In the form browsing / creating system, a data file and a form file are designated, and overlay printing is performed in which field data characters are superimposed on the form.
For printing, a printer 906 connected directly to the network
Alternatively, a printer 907 connected to the client is used.

Although the present embodiment has been described on the assumption that a laser beam printer (page printer) is used, the present invention can be similarly applied to other types of printers. A blank sheet is prepared for the printer, and a form is created by one printing. For browsing, an image of a form is created based on the same principle and can be displayed on a display connected to the client. In this embodiment, the description is made assuming a Windows system. In this case, a window for browsing a form is opened, and the completed form is displayed in the window. As long as the same function can be realized, the same description can be applied regardless of the type of OS and the display method.

The server 901 is always provided with the latest form information file and field data file. These files are given unique file names and are shared by the server and client. The created date and time information is embedded in each file, and the information does not change even when transferred to the client.

To issue a form printing instruction on the client, a form information file name to be used and a field data file name to be embedded in the form are specified. The client uses the file name to query the server about the file creation date and time. The server searches for the corresponding file from the list of managed file names and sends it back to the client. The returned date is compared with the date of the file stored in the cache by the client. If the cache is the latest one, the transfer from the server is not performed.If the file on the server is updated, a transfer request is sent. Updates the client cache when a transfer is received from the server.

In the form creation system according to the present embodiment, the form information files and the part files constituting the form information are compared and updated with the creation dates.
As for the field data file registered in the server, the latest file is acquired every time.

FIG. 1 is a block diagram of a form creation system according to the present embodiment. A form output instructing unit 101 for instructing printing in this system and a form information managing unit 1
With 02, a form information file used for the form instructed to be output is searched. When the form information file is retrieved from the form file 113 on the client or the form cache 112 on the server, form information having a form of the form is created by the form information creating unit 103 using the form information file, and the form information is created. The information is stored in the information storage unit 104.

Similarly, a field data file to be recorded in the form designated to be output by the form output instructing section 101 is searched by the field data managing section 105, and the field data file 11 on the client is retrieved.
5 or field data file 1 on server
14 is obtained. The field data creation unit 106 arranges the field data from the acquired field data file according to the created form information, and stores it in the field data storage unit 107. Thereafter, the form information storage unit 1 stores the form information in a form suitable for printing by the form creation unit 108.
04, the form information read from the field data storage unit 107 and the field data are overlapped, and a form is created. When browsing, the browsing unit 109 displays the superimposed form as an image. In the case of printing, a print command is sent to the printer 111 via the printing unit 110, and a form is output.

It should be noted here that the client caches the form information received from the server, but does not cache the field data. When the client downloads and uses the field data from the server, it does not save it and discards it each time.

FIG. 2 is a flowchart illustrating the operation of the form information management unit 102 in the client in the above configuration.

First, the designated form file is acquired and its form file name is interpreted (S202).
It is determined whether the file has been installed in the client (S203). If it exists locally, ie in the client's form cache file 113, the comparison is made with the master file located on the server. In this embodiment, the server inquires of the server about the creation date and time of the form file (S204), and compares the creation dates and times (S205). If the file located on the server is
If the version has the same creation date and time as the client, the local cache is used as it is, but if the form file of the server has been updated to a new version, the necessary form file is transferred from the server (S212).

If there is no form file to be requested locally, and if the form file is present on the server (step S211), the necessary form file is transferred from the server (S212). Otherwise, since the form to be sought does not exist in the system, an error to that effect is output (step S213).

Subsequently, necessary field data files are obtained. It is determined whether the required field data file is a local file created on the client (S
207), otherwise, it is determined whether the data file is located on the server (S214). If the data file exists on the server, the client requests the server for transfer and acquires data (S215, 216). If the client has a field data file, use it.

When all of the form information file and the field data file are completed, a form is created (S20).
8) Display or print (S209). If a non-existent file name is specified, an error is notified (S2
17) Cancel the form creation process.

As described above, the client requests the latest form information from the server. If the form information used by the client is a composite form, the above procedure is used to compare not only the creation date and time of the composite form file but also the creation date and time of the component forms included in the composite form and obtain the latest version from the server I do.

FIG. 3 is a flowchart showing a part of the processing in the server which has received a request from the client. First,
It is determined what the inquiry from the client is (S301). If a form file is designated from the client and the inquiry is about the creation date and time, the existence of the file is checked (S302). If the file exists on the server, the information on the creation date and time is returned to the client (S303). If it does not exist, it notifies that it does not exist (S304).

If a request for transfer of a form file is made from the client, the existence of the requested file is checked (S312), and if it is on the server, the form information file is returned (S313). If it does not exist, it notifies that it does not exist (S314).

If the request for the field data file transfer is met from the client, the existence of the requested file is checked (S322), and if it is on the server, the field data file is returned (S323). If it does not exist, it notifies that it does not exist (S324).

Of course, there are other requests from the client, but these are omitted.

As described above, in a system including a server and a client connected to each other via a network, when the client performs overlay printing using form information distributed from the server, the client has the client itself. The creation date of the form information file having the same name as that of the server is compared with the creation date and time. If the file of the server is newer, the file is loaded from the server and used.

For the overlay printing field data, if the client does not have the necessary field data file, it is downloaded from the server and used.

In this way, the client can use the latest form information, and can avoid wasting network bandwidth in obtaining the form information from the server.

FIG. 4 shows a memory map of a client in a state where a client program for implementing the form creation system described in the present embodiment is loaded into the RAM 1003 and becomes executable. In the present embodiment, an example is shown in which the client program and related data are directly introduced from the FD 1007 to the RAM 1003 and executed, but other than that, the related program is stored in the HD 1005, and
003 may be loaded. Further, the form creation system is recorded in the ROM 1004, and is configured so as to be a part of the memory map.
01 can also be executed. HD1005
Can also be explained in the same way when using as a part of the memory.

A basic I / O program 401 and an OS 402 are installed on the memory 400 and execute applications, print, and communicate. The client program of the form creation system is installed 403 in the memory, and the locally copied form information file is expanded in the memory and used as a cache. The data file stores field data files created locally and management information of form information files acquired from the server.

FIG. 5 shows that a server program for implementing the form creation system described in the present embodiment is a RAM.
The memory map of the client loaded into the executable file 1003 and becoming executable is shown. Although described in the same way as in FIG. 4, the work area 506 stores a file group stored on the server, for example, the creation date and time of a composite form and the component form files constituting the composite form, such as 507.

FIG. 7 is a module configuration diagram of the form creation system described in this embodiment. In this embodiment, O
It is assumed that Windows (registered trademark) manufactured by Microsoft Corporation is used as S, but the description is similarly applied to a different OS. In FIG. 7, reference numeral 701 denotes a client;
Reference numeral 2 denotes a server.

When a form printing instruction is issued by the client program 703, the processing described in FIG. 2 is performed, and the form information file and the field data file are referred to. The created image is displayed in a window on the display for browsing, but this is not shown in the description up to the middle of the printing process because the same is performed. At the time of printing, a drawing command is created by using a GDI (graphic display interface) 705, and a spooler 706 is used.
Send to The print information is once stored in the spooler, converted into a format that can be interpreted by the printer using the printer driver 707, and sent to the printers 710 and 711 to execute printing. Information is transferred to the network printer 711 via the network communication module 708. Server 70
In 2, the server program 704 and the network communication module 709 execute the processing described in FIG.

As described above, in the present embodiment, in a form creation system in which a form information file and a field data file on a server are transferred to a client and used, the date and time of creation of a file published on the server is provided to the client. Compared with the saved one, if the one on the server is newer, it is determined that it has been updated and transferred from the server to the client. As a result, the latest form information is always introduced to the client. The form information transmitted to the client is cached,
It will be used when browsing and printing forms with the same file name in the future. When using a cached form file, the server is inquired of whether or not the file has been updated, and the file is not transferred from the server until the file is updated.

For this reason, the information returned from the server for checking the date and time has a sufficiently small communication amount as compared with the transfer of the file, and the time required for exchanging the information is short. That is, there is an effect that the amount of communication flowing through the network is kept small while always maintaining the latest form information.

Further, when a field data file is created, the field data file, which is frequently updated, is transferred from the server every time it is viewed or printed, so that the latest file data can be provided to the client. There is.

As described above, since the form information that has been updated by manual operation in the past operation can be automatically updated to the latest version by all clients, errors caused by manual intervention, On the renewal date, there is also an effect of reducing the cost required to disseminate the method.

[Second Embodiment] In the first embodiment, for a composite form, the composite form file itself and its component form files are
Although it is described that the creation date and time of the server file and the client file are compared, if the client requests the creation date and time of the composite form, the creation date and time of the component files that compose it may also be responded at the same time. good.

At this time, the form information file used as the part form searches for the form information file of the part form, not the creation date and time recorded in the composite form, and returns a list of the creation date to the client. .

In the client, since the information on the creation date returned from the server covers the entire related file, the query for date collation is performed only once.

Further, if an updated form information file is found in the composite form used by the client, the update of the form information file can be performed at once. At this time, since a plurality of files need to be transferred, the files are transferred collectively during a time period when the use of the CPU of the client computer is low.

In the manner described above, the number of request messages from the client to the server can be reduced.
Further, if there is an updated part form included in the composite form, the entire form is loaded from the server, thereby eliminating the need to determine whether each file is the latest one by one.

[Third Embodiment] In S216 in FIG. 2 of the first embodiment, the field data file acquired from the server is not stored in the disk of the client, but is expanded on the memory to be browsed and printed. After being used, it is deleted from the memory so that no trace is left locally on the client. This can prevent the field data from being reused by the client.

[Fourth Embodiment] Instead of referring to the server 901 in FIG. 9 of the first embodiment as a specific server from a client, an arbitrary server name is specified to specify a form information file. To get. As a result, when transmitting a form by electronic mail or the like, only the field data file is attached to the mail, and the form information is specified by a URL (Unified Resource Locator) or the like. The computer that receives the mail becomes a client, and the client compares the date of the cached form information file with the date of the form information file specified by the URL in the same manner as in the first embodiment.

With this configuration, an unspecified user can download and use the latest form information from the server.

[0062]

As described above, it is possible to reliably update the form information without human intervention, and to prevent a heavy load on the network. In addition, it is possible to prevent a human error.

Further, the information returned from the server for the date and time collation has a sufficiently small communication volume as compared with the file transfer, and the time required for exchanging the information is short. That is, there is an effect that the amount of communication flowing through the network is kept small while always maintaining the latest form information.

Further, the field data file, which is frequently updated frequently, is transferred from the server every time it is browsed or printed, thereby providing the client with the latest one.

Further, with respect to the composite file, the number of messages on the network can be reduced by collectively sending the creation date and time of the component form constituting the composite file from the server to the client. Further, if there is an updated part form included in the composite form, the entire form is loaded from the server, thereby eliminating the need to determine whether each file is the latest one by one.

Further, by deleting the field data loaded from the server after use, the data can be prevented from being reused by the client.

Further, the form information is stored from a server closest to the client by arbitrarily specifying the server for storing the form information, instead of specifying the server, and reducing the load on the network. effective.

[Brief description of the drawings]

FIG. 1 is a block diagram of a form creation system.

FIG. 2 is a flowchart showing a flow of form creation in a client computer.

FIG. 3 is a flowchart showing a flow of form creation in a server computer.

FIG. 4 is a diagram of a memory map when a form creation system is introduced into a client computer.

FIG. 5 is a diagram of a memory map when a form creation system is introduced into a server computer.

FIG. 6 is an allocation map showing an arrangement of data inside a floppy disk.

FIG. 7 is a configuration diagram of software modules operated by a server and a client.

FIG. 8 is a conceptual diagram illustrating form creation by overlay printing.

FIG. 9 is a network system diagram including a server, a client, and a printer.

FIG. 10 is a block diagram of a computer constituting a server and a client.

FIG. 11 is a diagram showing a relationship between a computer and a floppy disk.

[Explanation of symbols]

400, 500 Memory map 401, 501 Basic I / O program 402, 502 OS 403 Form creation system client program 503 Form creation system server program 404 Form information file (cache) 504 Form information file (master) 405 Field data file 505 Field data file (master) 406, 506 Work area 601 Volume information 602 Directory information 603, 704 Server program 604, 703 Client program 605 Related data 900 Network 901-905 Computer (server, client) 906 Network printer 907 Printer 1001 CPU 1002 System bus 1003 RAM 1004 RO 1005 HD 1006 FDD 1007,1102 FD 1008 CRT 1009 keyboard 1010 network communication unit 1101 computer

Claims (16)

[Claims] 1. A form creation method for acquiring form information from a server connected via a network, overlaying the form information with field data, and printing the form data, comprising: a determination step of determining whether there is designated form information; If there is, an acquisition step of acquiring the creation date and time of the file of the same name from the server; a comparison step of comparing the acquired creation date and time with the creation date and time attached to the form information; Acquiring the form information from the server when it is determined that the creation date and time obtained in the obtaining step is newer. 2. The form creation method according to claim 1, further comprising a step of reading out the field data from the server when the field data held by the server is designated as the field data. 3. The method according to claim 2, wherein the form information is composite form information obtained by combining part forms, and in the obtaining step, creation dates and times of all part forms included in the composite form information are obtained. Item 1. The form creation method according to Item 1. 4. In the comparing step, if it is determined that the creation date and time obtained in the obtaining step is newer, all the component forms included in the composite form are obtained from the server by the obtaining step. The form creation method according to claim 3, wherein: 5. The form creation method according to claim 2, wherein when the field data is read from a server, the field data is deleted after use. 6. A form creation device for acquiring form information from a server connected via a network and overlaying the form data with field data for printing, comprising: a determination unit for determining the presence or absence of designated form information; When there is, acquisition means for acquiring the creation date and time of a file of the same name from the server, comparison means for comparing the acquired creation date and creation date and time attached to the form information, Means for acquiring the form information from the server when it is determined that the creation date and time acquired by the acquiring means is newer. 7. The form creation apparatus according to claim 6, further comprising means for reading out the field data from the server when the field data held by the server is designated as the field data. 8. The method according to claim 1, wherein the form information is composite form information obtained by combining part forms, and the acquisition unit acquires the creation date and time of all the part forms included in the composite form information. Item 7. The form creation device according to Item 6. 9. When the comparison unit determines that the creation date and time acquired by the acquisition unit is newer, all the component forms included in the composite form are acquired from the server by the acquisition unit. 9. The form creation device according to claim 8, wherein: 10. The form creation device according to claim 7, wherein when the field data is read from the server, the field data is deleted after use. 11. A form creation system including a server device and a client device that obtains form information from the server device and overlays and prints the field data to print the form information, wherein the server has a form with date and time of creation. Information, wherein the client has determination means for determining the presence or absence of the specified form information; if there is form information, obtaining means for obtaining the creation date and time of the file having the same name from the server; And comparison means for comparing the creation date and time attached to the form information. If the comparison means determines that the creation date and time acquired by the acquisition means is newer, the server sends the form information And a means for acquiring the form. 12. A computer, comprising: a determination unit for determining whether there is specified form information; an obtaining unit for obtaining a creation date and time of a file having the same name from the server when there is form information; Comparing means for comparing the creation date and time attached to the form information; and if the comparison means determines that the creation date and time acquired by the acquisition means is newer, the server sends the form information to the form information. A storage medium storing a computer program for functioning as a means for acquiring. 13. The computer program according to claim 12, wherein the computer program further functions as means for reading out the field data from the server when the field data held by the server is designated. Storage medium. 14. The method according to claim 1, wherein the form information is composite form information obtained by combining part forms, and the acquisition unit acquires the creation date and time of all the part forms included in the composite form information. Item 13. The storage medium according to Item 12. 15. When the comparison means determines that the creation date and time acquired by the acquisition means is newer, all the part forms included in the composite form are acquired from the server by the acquisition means. The storage medium according to claim 14, wherein: 16. The storage medium according to claim 13, wherein when the field data is read from a server, the computer program further functions as means for deleting the field data after use.