JP2005339333A - Form management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a form management system capable of suppressing the cost for arranging development software or environments, and treated by even a user having no special knowledge. <P>SOLUTION: This system comprises a first terminal 10 processing spreadsheet files, at least one second terminal 20 processing HTML (hyper text markup language) files, and a server interposed between the first and second terminals 10 and 20 through a network, which converts a spreadsheet file processed by the first terminal 10 to an HTML file followed by transferring to the second terminal 20, and converts an HTML file processed by the second terminal to a spreadsheet file followed by transferring to the first terminal 10. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  In the present invention, in a company having a plurality of company branches that are scattered at locations apart from the company headquarters and the company headquarters, a form is created while exchanging information between the company headquarters and each company branch via a network. The present invention relates to a form management system for management.

  For example, companies in the restaurant industry that have a head office and multiple stores, etc., such as the distribution industry, restaurant industry, and financial industry that have multiple corporate branches that are located in a location apart from the corporate headquarters. In the form management system, forms such as various application forms are changed or newly added depending on the operation status. For this reason, for example, it is necessary to manage the form while exchanging information between the company headquarters and each company branch via a network such as the Internet.

  In Patent Documents 1 and 3, a form created by spreadsheet software is converted into an HTML file (Hyper Text Markup Language) and stored on the server, and the form taken out from the client and entered is stored on the server. The technology to be operated is disclosed. Patent Document 2 discloses a technique for converting presentation data into an HTML file and using it.

JP 2003-50964 A JP 2003-299059 A JP 2003-303103 A

  However, when a form management system is constructed with a web application, it is expensive to prepare development software and an environment. In addition, since specialized knowledge such as HTML and script language is required, it is extremely difficult for the user to cope with it. For this reason, even if a minor change or new addition is made, there is a problem that it is necessary to request a specification change from the system developer, which takes both cost and time.

  In addition, the users at the corporate headquarters of this type of form management system are usually accountants of the company, and in many cases full-scale form management is performed using existing spreadsheet software for form management. . Such users are accustomed to using spreadsheet software. On the other hand, users in each company branch often only provide information necessary for form management requested by the accounting department of the company headquarters. Such users are not familiar with the spreadsheet software described above.

  In the technique described in Patent Document 1, creation of a new form or modification of an existing form must be performed by a system developer who has expertise other than just spreadsheet software. There is a problem that users who do not have specialized knowledge other than wear cannot do this. In addition, the technique described in Patent Document 2 has a problem that the presentation data is merely transmitted from the server to the client in the HTML format. Furthermore, in the technique described in Patent Document 3, the information processing terminal is provided with spreadsheet software, and a user who uses the information processing terminal needs to have knowledge about the spreadsheet software. is there.

  Therefore, an object of the present invention is to provide a form management system that can control costs for preparing development software and an environment and can be handled by a user who does not have specialized knowledge.

  Another object of the present invention is to provide a form management system that is easy to use for both users of a company headquarters and users of a plurality of company branches.

  According to the present invention, a first terminal that processes a spreadsheet file, at least one second terminal that processes an HTML (Hyper Text Markup Language) file, and a network between the first and second terminals The spreadsheet file processed by the first terminal is converted into an HTML file and transferred to the second terminal, while the HTML file processed by the second terminal is converted into a spreadsheet file. There is obtained a form management system comprising a server that performs conversion and transfers it to the first terminal.

  According to the present invention, the server is constituted by a file server and a web application server, and the first terminal creates a spreadsheet file and connects the created spreadsheet file to the file server. The web application server converts the spreadsheet file uploaded from the first terminal through the network and passed through the file server into an HTML file, and converts the converted HTML file through the network. Publish to the second terminal, and the second terminal browses the HTML file published via the network from the web application server and apparently writes to a predetermined item of the HTML file. In writing against Data to be uploaded to the web application server via a network, and the web application server further converts the HTML file supplemented based on the data uploaded from the second terminal into a spreadsheet file and is converted. The spreadsheet file is transmitted to the first terminal via the network via the file server, and the first terminal further downloads the spreadsheet file complemented via the network via the file server. The form management system is obtained.

  According to the present invention, it is further possible to obtain the form management system in which the first terminal displays at least a part of a display user interface for HTML files by using a display user interface for spreadsheet files.

  The first effect of the present invention is that it is possible to control the cost of preparing development software and environment, and to cope with a user who does not have specialized knowledge.

  The second effect of the present invention is that it is easy to use for both the user of the corporate headquarters and each user of the plurality of corporate branches.

  Hereinafter, a form management system according to the present invention will be described with reference to the drawings.

  Referring to FIG. 1, the form management system is installed in a company headquarters and is installed in a first terminal 10 for processing a spreadsheet file and each company branch and processes a Hyper Text Markup Language (HTML) file. A spreadsheet file that is processed through the Internet as a network between at least one second terminal 20 and the first terminal 10 and the second terminal 20 is converted into an HTML file. And a server 30 that transfers the HTML file processed by the second terminal 20 to a spreadsheet file and then transfers the file to the first terminal 10. .

  The server 30 includes a file server 31 and a web application server 36.

  The first terminal 10 creates a spreadsheet file using spreadsheet software such as Excel (registered trademark of Microsoft Corporation), for example, and uploads the created spreadsheet file to the file server 31 via the Internet.

  The web application server 36 converts a spreadsheet file uploaded from the first terminal 10 via the Internet and passed through the file server 31 into an HTML file, and converts the converted HTML file to at least a second terminal via the Internet. 20 public.

  The second terminal 20 browses an HTML file published from the web application server 36 via the Internet, and apparently writes data corresponding to the written item by writing to a predetermined item of the HTML file. Upload to the application server 36 via the Internet.

  The web application server 36 further converts the HTML file complemented or updated based on the data uploaded from the second terminal 20 into a spreadsheet file, and the converted spreadsheet file is passed through the file server 31 via the Internet. To the first terminal 10.

  Further, the first terminal 10 downloads the complemented or updated spreadsheet file via the file server 31 and the Internet. Then, the first terminal 10 processes the downloaded spreadsheet file as necessary.

  The first terminal 10 substitutes and displays at least a part of the display user interface for the HTML file with the display user interface for the spreadsheet file. Specifically, the display user interface for the HTML file is at least one of a writing area, a radio button, and a check box.

  The web application server 36 converts the display user interface for the spreadsheet file into a display user interface for the HTML file, while converting the display user interface for the HTML file into a display user interface for the spreadsheet file. It has. Thereby, bidirectional conversion between the spreadsheet file and the HTML file is performed more quickly.

  The file server 31 may store the spreadsheet file acquired from the first terminal and the spreadsheet file acquired from the web application server 36.

  Also, the web application server 36 may store the HTML file acquired from the file server 31 and converted, and the HTML file acquired from the second terminal.

  The file server 31 and the web application server 36 may be installed in one place. In this case, the connection is made via a LAN (Local Area Network) or an internal wiring of one server computer.

  Alternatively, the file server 31 and the web application server 36 may be installed in different places. In this case, connection is made via a WAN (Wide Area Network) such as the Internet.

  Note that the spreadsheet file having the same entity and the HTML file uploaded from the second terminal 20 (data-complemented HTML file) have the same document type information, unique information of the second terminal 20, and processing. It is preferable that date information is included. As a result, sorting is quickly performed when a plurality of files are handled.

  At least one of the first terminal 10, the second terminal 20, and the server 30 can be configured by a personal computer.

  Next, the operation of the form management system will be described with reference to FIGS.

  FIG. 2 shows a display screen on the first terminal 10 in the corporate headquarters.

A first user in the corporate branch creates a form using spreadsheet software. When creating,
-Color or highlight the part that will be the input area on the HTML file.

  -When the part that becomes a radio button on the HTML file is to be selected at the time of initial display, it is “●”, and when it is not selected at the time of initial display, it is “◎”.

  -In the HTML file, a check box is marked with “★” when it is selected when initially displayed, while it is marked with “☆” when it is not selected when initially displayed.

  As shown in FIG. 3, guidance display may be performed for the first user who is not accustomed to such a creation method.

  The first user uploads the created spreadsheet file to the file server 31 of the server 30. When uploading, the first user only needs to drag and drop the spreadsheet file icon to a specific folder representing the server 30 (file server 31).

  The spreadsheet file to be uploaded includes document type information and processing date information. At this point, the spreadsheet file does not yet include the unique information of the second terminal 20 described above. In other words, the spreadsheet file at this point is not dedicated to a specific second terminal 20 but is a so-called original or template file that is used for a plurality of second terminals 20 for general purposes.

  The file server 31 of the server 30 stores the spreadsheet file uploaded from the first terminal 10. That is, an original or template spreadsheet file is saved.

  The second user in the corporate branch activates the browser in the second terminal 20 as necessary to access the form page.

  When requested by the second terminal 20 to display the form screen, the web application server 36 of the server 30 converts the spreadsheet file stored in the file server 31 into an HTML file.

When converting the spreadsheet file to the HTML file by the web application server 36,
-The highlighted area on the spreadsheet file is the input area on the HTML file.

  ・ The part marked “●” in the spreadsheet file is the selected radio button in the initial display in the HTML file, and the part marked “◎” is not selected in the initial display. State radio button.

  ・ The part marked with “★” in the spreadsheet file is the selected radio button in the initial display in the HTML file, and the part marked with “☆” is not selected in the initial display. It is a state check box.

  The HTML file obtained by converting the spreadsheet file also includes document type information and processing date / time information. Even at this time, the unique information of the second terminal 20 described above is not yet included in the HTML file.

  As shown in FIG. 4, the second user in the corporate branch browses the page of the form through the browser in the second terminal 20, enters characters and numbers in the input area, selects a radio button, and selects a check box. Make a selection. After entering all the predetermined items, press the upload, send, or enter button.

  At the time of information input using the second terminal 20, unique information for each of the plurality of second terminals 20 (corporate branches) is automatically or manually uploaded and included in the corresponding HTML file. Become.

  When the web application server 36 of the server 30 receives predetermined item data from the second terminal 20, the web application server 36 converts the HTML file into a spreadsheet file.

When the web application server 36 converts an HTML file into a spreadsheet file,
-Color or highlight the part that is the input area on the HTML file.

  ・ If the part that is a radio button on the HTML file is selected, it will be “●” on the spreadsheet file, while if it is not selected on the HTML file, it will be “◎” on the spreadsheet file. .

  ・ If the part that is a check box in the HTML file is in the selected state, it is “★” on the spreadsheet file, while if it is not selected on the HTML file, it is “☆” on the spreadsheet file. .

  The file server 31 of the server 30 stores the spreadsheet file from the web application server 36 and transmits the spreadsheet file to the first terminal 10 as necessary. The spreadsheet file stored in the file server 31 includes unique information for each of the plurality of second terminals 20 (enterprise branches), and is stored separately from the above-described original or template spreadsheet file.

  The first user in the company branch uses the first terminal 10 to process a spreadsheet file in which each item is supplemented or updated as shown in FIG.

  Thereafter, the same process is performed for each of the various forms and for each branch of the company.

  As described above, according to this form management system, the result input on the screen of the second terminal is output as a spreadsheet file on the first terminal, so that later data management and processing, etc. Is easy.

  Although the embodiments of the present invention have been described above, the present invention is not limited to these embodiments, and various modifications are possible within the technical scope described in the claims. Needless to say.

  For example, in the above embodiment, a form management system that handles a spreadsheet file has been described as an example. It may be a form management system that handles two files borderlessly or in a multiple manner. In those embodiments, the spreadsheet file in the above embodiment is replaced with the corresponding file.

  The network in the present invention is not limited to the Internet. In the present invention, the network may include, for example, an intranet at least in part. That is, the network in the present invention is configured by at least one of WAN and LAN such as the Internet and an intranet.

It is a figure which shows the structure of the form management system by this invention. It is a figure which shows the example of a display screen on the 1st terminal in the form management system shown in FIG. It is a figure which shows the example of a display screen on the 1st terminal in the form management system shown in FIG. It is a figure which shows the example of a display screen on the 2nd terminal in the form management system shown in FIG. It is a figure which shows the example of a display screen on the 1st terminal in the form management system shown in FIG.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 1st terminal 20 2nd terminal 30 Server 31 File server 36 Web application server

Claims (12)

A first terminal for processing the spreadsheet file;
At least one second terminal for processing HTML (Hyper Text Markup Language) files;
While interposing through the network between the first and second terminals, the spreadsheet file processed by the first terminal is converted into an HTML file and transferred to the second terminal, while the second terminal A form management system comprising: a server that converts an HTML file processed by the terminal of the first to a spreadsheet file and transfers the file to the first terminal. The server includes a file server and a web application server,
The first terminal creates a spreadsheet file and uploads the created spreadsheet file to the file server via a network,
The web application server converts a spreadsheet file uploaded from the first terminal via the network and passed through the file server into an HTML file, and converts the converted HTML file to the second terminal via the network. Published against
The second terminal browses an HTML file published via the network from the web application server, and apparently writes data corresponding to a write item by writing to a predetermined item of the HTML file. Upload to the server over the network,
The web application server further converts an HTML file supplemented based on data uploaded from the second terminal into a spreadsheet file, and converts the converted spreadsheet file via the file server via the network. Send to the first terminal,
The form management system according to claim 1, wherein the first terminal further downloads a spreadsheet file supplemented via a network via the file server.   The form management system according to claim 1 or 2, wherein the first terminal displays at least a part of a display user interface for HTML files by using a display user interface for spreadsheet files.   The form management system according to claim 3, wherein the display user interface for the HTML file is at least one of a writing area, a radio button, and a check box.   The web application server converts a display user interface for a spreadsheet file into a display user interface for an HTML file, and a correspondence table for converting a display user interface for an HTML file into a display user interface for a spreadsheet file. The form management system according to claim 3 or 4, further comprising:   6. The form management system according to claim 2, wherein the file server stores a spreadsheet file acquired from the first terminal and a spreadsheet file acquired from the web application server.   The form management system according to any one of claims 2 to 6, wherein the web application server stores an HTML file acquired and converted from the file server and an HTML file acquired from the second terminal.   The form management system according to any one of claims 2 to 7, wherein the file server and the web application server are connected via a LAN (Local Area Network).   The form management system according to claim 2, wherein the file server and the web application server are connected via a WAN (Wide Area Network).   10. The spreadsheet file having a common entity and the complemented HTML file include the same document type information, unique information of the second terminal, and processing date and time information, respectively. Form management system.   The form management system according to any one of claims 1 to 10, wherein a word processor file is used instead of the spreadsheet file. The form management system according to claim 1, wherein a presentation file is handled instead of the spreadsheet file.

Images