JP5571985B2 - Spreadsheet file version conversion system, version conversion method, and program therefor - Google Patents

Description

  The present invention relates to a spreadsheet file version conversion technique, and more particularly, to a spreadsheet file version existing on a server and spreadsheet software (hereinafter referred to as client software) installed in a client computer that refers to the spreadsheet file. This relates to a technology that automatically absorbs the difference between versions of spreadsheet software).

  As a conventional porting technology for porting form data defined and created in the old system to the new system, for example, there is one described in JP 2009-116632 A (Patent Document 1).

  The one described in Patent Document 1 is a transplant that absorbs the difference between the form data defined and created in the old system such as the existing monitoring control system and the form data for the spreadsheet software of the new system by automatic conversion. The purpose is to provide a transplant technology that can significantly reduce the replacement cost. To achieve that purpose, fixed data (ruled line information, Item name, title, etc.) and variable part data (date, measurement value, history, etc.) are individually analyzed and primary converted into text format data, fixed text data of this text format data and new system table Absorbing the difference from the fixed part data defined in the calculation software, it is secondarily converted into form data for spreadsheet software, and this is converted to text format data. It is obtained to perform the secondary conversion process of expanding the variable part data.

JP 2009-116632 A

  However, even if the form data defined and created in the old system is ported to the form data for the spreadsheet software of the new system using the transplant technology described in Patent Document 1, the spreadsheet of the new system Due to the difference in the version of the spreadsheet software of the client that refers to the form data for software, the display may differ from the defined display.

  In that case, in the new system, it is necessary to prepare each form data for spreadsheet software defined according to the version of the client spreadsheet software, in order to absorb the difference in version in addition to the replacement porting man-hours. Man-hours are newly generated.

  In addition, if the form data for spreadsheet software is modified during the operation of the new system, it is necessary to modify and confirm all the form data defined according to the client spreadsheet software version. The maintenance man-hours are also greatly increased.

  An object of the present invention is to provide a spreadsheet for spreadsheet software used in the system even when the version of the spreadsheet file existing on the server is different from the version of the client spreadsheet software that refers to the spreadsheet file. Version conversion system that eliminates the need to be aware of the version of the spreadsheet software installed on the client PC that references the spreadsheet file when creating and modifying data, and can greatly reduce the number of development and operation man-hours And a version conversion method and a program therefor.

  In order to achieve the above object, the spreadsheet file version conversion technique according to the present invention is a spreadsheet software version installed on a server and a spreadsheet software installed on a client PC that refers to the spreadsheet file. If the versions are different, the version of the spreadsheet software installed on the client PC is automatically collected and exists on the server by referring to the format information database that manages the information for absorbing the differences between the versions. The spreadsheet file to be converted is automatically converted into a version of spreadsheet software installed on the client PC that refers to the spreadsheet file.

More details
a) A version conversion system according to the present invention is a version conversion system for automatically converting a spreadsheet file existing on a server into a version of a spreadsheet software installed on a client PC. A format information database for managing information for absorbing differences, a version search means for collecting a version of spreadsheet software installed in a client PC that refers to a spreadsheet file existing on the server, and the version search Based on the version of the spreadsheet software collected by the means, the version and setting information of the spreadsheet file existing on the server, and the contents of the format information database, the spreadsheet file existing on the server, Refer to the spreadsheet file Is characterized by having a version converting means for automatically converting the version of the spreadsheet software installed on the client PC that, the.

b) In addition, in the above a), the format information database includes a spreadsheet software provided for absorbing a difference between versions of format element names (names uniquely identifying format elements that define formats). The format element name setting table for registering the format element name defined for each version and the format element value (value that uniquely identifies the attribute of the format element) are provided to absorb the difference between the versions. From the format element value setting table that registers format element values defined for each version of spreadsheet software, and the software information registration table that registers the type (name) and version of spreadsheet software installed on the client PC The version conversion means includes the version and setting of the spreadsheet file existing on the server. Based on the information, the version of the spreadsheet software installed in the client PC collected by the version search means, the contents of the format element name setting table, the format element value setting table, and the software information registration table, The spreadsheet file existing on the server is automatically converted into a spreadsheet file of a spreadsheet software version of the client PC.

c) A version conversion method according to the present invention is a version conversion method for automatically converting a spreadsheet file existing on a server into a version of a spreadsheet software installed on a client PC, the table existing on the server. Version search procedure for collecting the version of the spreadsheet software installed on the client PC that refers to the calculation file, the version of the spreadsheet software collected by the version search means, and the spreadsheet file existing on the server Based on the version and setting information and the contents of the format information database, the format information database is referred to, and the spreadsheet file existing on the server is installed in the client PC that refers to the spreadsheet file. Spreadsheet software It is characterized by having a version conversion procedure for automatically converting the version.

d) In addition, in the above c), the format information database includes a spreadsheet software provided for absorbing differences between versions of format element names (names that uniquely identify format elements that define formats). The format element name setting table for registering the format element name defined for each version and the format element value (value that uniquely identifies the attribute of the format element) are provided to absorb the difference between the versions. From the format element value setting table that registers format element values defined for each version of spreadsheet software, and the software information registration table that registers the type (name) and version of spreadsheet software installed on the client PC The version conversion procedure is performed by the client PC collected by the version search means. Based on the version of the installed spreadsheet software, the version and setting information of the spreadsheet file existing on the server, the format element name setting table, the format element value setting table, and the contents of the software information registration table This is a procedure for automatically converting a spreadsheet file existing on the server into a spreadsheet file of a spreadsheet software version of the client PC.

e) A program according to the present invention is a program for causing a computer to execute each procedure in the version conversion method described in c) or d) above.

  According to the present invention, when the version of the spreadsheet file existing on the server and the version of the spreadsheet software installed on the client PC that refers to the spreadsheet file are different, the spreadsheet file existing on the server is Since it is possible to automatically convert to a spreadsheet file corresponding to the version of the spreadsheet software installed on the client PC, the spreadsheet file will be used when creating and modifying the form data for the spreadsheet software used in the system. It is not necessary to be aware of the version of the spreadsheet software installed on the client PC that refers to the above, and it is possible to greatly reduce the number of development / operation man-hours.

It is a figure which shows the example of whole structure of the version conversion system of the spreadsheet file which concerns on this invention. It is a figure which shows the structural example of the format information database (format element name setting table) which concerns on this invention. It is a figure which shows the structural example of the format information database (format element value setting table) which concerns on this invention. It is a figure which shows the structural example of the format information database (software information registration table) which concerns on this invention. It is a flowchart of the process which the version search means (version information acquisition process part) which concerns on this invention performs. It is a flowchart of the process which the version conversion means (format conversion process part) which concerns on this invention performs (the 1). It is a flowchart of the process which the version conversion means (format conversion process part) which concerns on this invention performs (the 2). It is a figure which shows an example of the spreadsheet file (file before conversion) which exists on the server, and the spreadsheet file (file after conversion) created on the client PC.

  FIG. 1 shows an example of the overall configuration of a spreadsheet file version conversion system according to the present invention.

  As shown in the figure, the version conversion system according to the present invention includes a server 101, a client PC 102, and a network 200 such as the Internet that transmits and receives data between the server 101 and the client PC 102.

  The server 101 also includes a spreadsheet file 103 before conversion that is referred to by the client PC 102 and a version conversion unit 104 that automatically converts the version of the spreadsheet file 103.

  Further, the version conversion means 104 includes a format conversion processing unit 107 that performs version conversion, and a format information database (master database) 108 that manages information for absorbing differences between versions.

  The client PC 102 includes spreadsheet software 110 and version search means 106 that automatically acquires the version of the spreadsheet software 110 installed in the client PC 102.

  The version search unit 106 includes a version information acquisition processing unit 109 that acquires version information of the spreadsheet software 110 installed in the client PC 102. The spreadsheet file 105 is a spreadsheet file obtained by converting the spreadsheet file 103 before conversion in the server 101 according to the version of the spreadsheet software 110 installed in the client PC 102.

  FIG. 2-A, FIG. 2-B and FIG. 2-C show three tables stored in the format information database 108, namely, <format element name setting table>, <format element value setting table>, and <software information registration>. Table> is a diagram for explaining (1) table name, (2) table item, and (3) data example. Hereinafter, each table will be described in detail.

(A) About [Format Element Name Setting Table] (See Figure 2-A)
(1) A table named [name of format element setting table] is a table for registering format element names (names uniquely identifying format elements) defined for each version of spreadsheet software. This table is a table provided to absorb differences between versions of format element names.

(2) Table item The data items of the format element name setting table are composed of <function group>, <version>, and <format element name>.

  In the <function group> column, format element names having the same function are grouped and registered.

  In the <Version> column, the version of the spreadsheet software that defines the format element name is registered.

  In the <format element name> column, a format element name defined for each version of the spreadsheet software is registered.

(3) Data example A data example of each data item of the format element name setting table is shown.
(A) In this example, a format element name that uniquely identifies the function “sheet name” (defined as “SheetName” in the version “2000” of the spreadsheet software and “WorkSheet” in the version “2003”). Are grouped together in a function group called “sheet name setting”.

(B) In this example, a format element name that uniquely identifies the function “cell name” (defined as “CellName” in the version “2000” of the spreadsheet software and “WorkCell” in the version “2003”). , “Cell name setting” is grouped together.

(C) In this example, a format element name that uniquely identifies the function “line display” (specified as “Line” in the version “2000” of the spreadsheet software and “Column” in the version “2003”) Are grouped together in a function group called “line display settings”.

(D) In this example, a format element name that uniquely identifies the function “column display” (specified as “Sequence” in the version “2000” of the spreadsheet software and “Row” in the version “2003”). The function group is called “column display setting”.

(E) In this example, a format element name that uniquely identifies the function “cell value” (defined as “Variable” in the version “2000” of the spreadsheet software and “Value” in the version “2003”) Are grouped together in a function group called “cell value setting”.

(F) In this example, a format element name that uniquely identifies the function of “cell color” (defined as “Tone” in the version “2000” of the spreadsheet software and “Color” in the version “2003”). Are grouped together in a function group called “cell color setting”.

(B) [Format Element Value Setting Table] (See Figure 2-B)
(1) The table named [format element value setting table] is a table that registers format element values (values that uniquely identify the attributes of format elements) defined for each version of spreadsheet software. is there. This table is a table provided to absorb the difference between the versions of the format element values.

(2) Table items The data items of the format element value setting table are composed of <function group>, <attribute group>, <version>, and <format element value>.

  In the <function group> column, a function group that specifies information on format element values in the <function group> column registered in the [format element name setting table] is registered.

  In the <attribute group> column, format element values having the same attribute are grouped and registered.

  In the <version> column, the version of the spreadsheet software that defines the corresponding format element value is registered.

  In the <format element value> column, a format element value defined for each version of the spreadsheet software is registered.

(3) Data example (a) Within the function group “row display setting”, a format element value that uniquely identifies the attribute “display” (“YES” for spreadsheet software version “2000”, and “2003” for version “2003”) “TRUE”) are grouped together in an attribute group “display”.

Therefore, if the format information “line display” is an example of the spreadsheet software version “2000”,
a) [Format element name setting table] ⇒ Function group “Line display setting”, Format element name “Line”
b) [Format element value setting table] => Function group “Line display setting”, Attribute group “Display”,
c) Format element value “YES”
Thus, the format information ““ Line ”=“ YES ”” can be expressed.

  Similarly, the format information “row display” can be expressed as the format information “Column” = “TRUE” when the spreadsheet software version “2003” is taken as an example.

(B) The same applies to the case where the row display setting is not displayed, the case where the column display setting is displayed, and the case where the column display setting is not displayed.

(C) In the function group “cell color setting”, a format element value that uniquely identifies the attribute “red” (“# FF0000” for spreadsheet software version “2000”, “Red” for version “2003”) In the attribute group “red”.

Therefore, if the format information “cell color is red” is taken as an example of the spreadsheet software version “2000”,
a) [Format element name setting table] ⇒ Function group “Set cell color”, Format element name “Tone”
b) [Format element value setting table] ⇒ Function group “Cell color setting”, Attribute group “Red”,
c) Format element value “# FF0000”
Thus, it is possible to express the format information ““ Tone ”=“ # FF0000 ””.

  Similarly, if the format information “cell color is red” is taken as an example of the spreadsheet software version “2003”, the format information “Color” = “RED” can be expressed.

(C) About [Software Information Registration Table] (See Fig. 2-C)
(1) The table named “software information registration table” is a table for registering the spreadsheet software information of the client PC. This table is a table provided for acquiring the type (name) and version of the spreadsheet software installed in the client PC.

(2) Table items The data items of the software information registration table are composed of <MAC address>, <software name>, and <version information>.

a) In the <MAC address> column, a MAC address which is a value for uniquely identifying the client PC is registered.
b) In the <software name> column, the type (name) of spreadsheet software installed in the client PC is registered.
c) In the <version information> column, the version of the spreadsheet software installed in the client PC is registered.

(3) Data Example The software information registration table in this example is stored in the client PC uniquely identified by the MAC address “00-07-E9-4D-C2-AA”, the version “1” of the spreadsheet software “software A”. ”Is installed, the version“ 2000 ”of the spreadsheet software“ software B ”is installed on the client PC uniquely identified by the MAC address“ 00-07-E9-4D-C2-BB ”, and the MAC address“ 00 ” This indicates that the version “2003” of the spreadsheet software “software C” is installed in the client PC uniquely identified by “−07-E9-4D-C2-CC”.

  FIG. 3 is a flowchart of processing performed by the version information acquisition processing unit 109 of the version search unit 106 according to the present invention. This process is automatically executed when the client PC 102 is activated.

(A) The version information acquisition processing unit 109 of the version search unit 106 performs a registry search of the client PC 102 in order to check the installation information of the spreadsheet software 110 (step S301).

(B) It is determined whether the installation information of the spreadsheet software 110 exists in the registry (step S302).

(C) As a result of the determination, if the installation information of the spreadsheet software exists in the registry (step S302: Y), “Client Information Registration Table” 306 (see FIG. 2C) “Client” “MAC Address of PC”, “Spreadsheet Software Name” in the <Software Name> column, and “Spreadsheet Software Version” in the <Version Information> column are registered (step S303).

(D) After registration in the [software information registration table] 306 or when installation information of the spreadsheet software does not exist in the registry (step S302: N), all the registry items specified by the version search means 106 It is determined whether the search has been executed (step S304).

(E) When all the registry items designated by the version search means 106 have not been searched (step S304: N), the process moves to the next registry search item (step S305), and the registry search process is repeated. If all the registry items have been searched (step S304: Y), the processing of this program ends.

  FIG. 4 is a flowchart of the processing performed by the format conversion processing unit 107 of the version conversion means 104, which is roughly divided into (1) conversion preparation processing phase, (2) conversion processing (sheet name setting) phase, and (3) conversion. Processing (cell name setting) phase, (4) conversion processing (row display setting) phase, (5) conversion processing (column display setting) phase, (6) conversion processing (cell value setting / setting information) phase, (7 ) Consists of reflection processing to all sheets. This process is automatically executed when the spreadsheet file 103 existing on the server 101 is opened by the spreadsheet software 110 of the client PC 102.

(1) Conversion preparation processing phase This phase is a preparation processing phase of the version conversion processing performed by the format conversion processing unit 107 of the version conversion means 104.

(A) The format conversion processing unit 107 of the version conversion unit 104 acquires the version of the spreadsheet file 103 existing on the server 101 (step S401).

(B) Next, the [software information registration table] 432 (see FIG. 2C) is searched to obtain the spreadsheet software information of the client PC 102 (step S402).

  Here, the search condition is the <MAC address> column, and the acquired value is data in the <software name> column and the <version information> column.

(C) It is determined whether the version information of the spreadsheet software 110 of the client PC 102 has been acquired (step S403).

(D) If the version information of the spreadsheet software 110 of the client PC 102 can be acquired (step S403: Y), it is determined whether or not the version of the spreadsheet file 103 existing on the server 101 is the same (step S404).

(E) When the version information of the spreadsheet software 110 of the client PC 102 cannot be acquired (step S403: N), or the version information of the spreadsheet software 110 of the client PC 102 and the version of the spreadsheet file existing on the server are If they are the same (step S404: Y), the processing of this program is terminated.

(F) If the version information of the spreadsheet software 110 of the client PC 102 and the version of the spreadsheet file 103 existing on the server 101 are not the same (step S404: N), the version information of the spreadsheet software 110 of the client PC 102 is used. Then, a new spreadsheet file 105 is created on the client PC 102 (step S405).

  In the following description, for the sake of convenience, the spreadsheet file 103 existing on the server 101 is referred to as “pre-conversion file”, and the newly created spreadsheet file 105 on the client PC 102 is referred to as “post-conversion file”. .

(2) Conversion Process (Sheet Name Setting) Phase This phase is a sheet name setting conversion process phase performed by the format conversion processing unit 107 of the version conversion means 104.

(A) The sheet name is acquired from the “file before conversion” 103 existing on the server 101 (step S406). An example in which the sheet name “HR” is acquired from an arbitrary sheet in the version “2000” file is shown in “”.

{Process 1} [Format element name setting table] 433 (see FIG. 2A) is searched to acquire the format element name.

  The search conditions in this case are <function group> column: “sheet name setting” value “sheet name setting”, <version> column: “file before conversion” version “2000”, and acquired value As a result, a <format element name> column ““ SheetName ”” is obtained.

{Process 2} Next, the setting information of the “file before conversion” 103 existing on the server 101 is searched, and the value set in the format element name is acquired.

  The search condition in this case is the format element name: “SheetName” acquired in the format element name: {Process 1}, and the value ““ Human Resources ”” set in the format element name “SheetName” as the acquired value. Is obtained (see FIG. 5A).

(B) A sheet name is set in the “post-conversion file” 105 created on the client PC 102 (step S407). An example in which the sheet name “HR” is set for an arbitrary sheet in the version “2003” file is shown in “”.

{Process 3} [Format element name setting table] 433 is searched to acquire the format element name.

  The search conditions in this case are <function group> column: “sheet name setting” value “sheet name setting”, <version> column: “file after conversion” version “2003”, and acquired value As a result, a <format element name> column ““ WorkSheet ”” is obtained.

{Process 4} Next, the setting information of the “post-conversion file” 105 created on the client PC 102 is searched to set a value for the format element name.

  The search condition in this case is the format element name: the format element name ““ WorkSheet ”” acquired in {Process 3} above, and the value ““ Personnel ”” acquired in {Process 2} is obtained as the setting value. .

  Accordingly, the processing performed in the conversion processing (sheet name setting) phase is ““ SheetName ”=“ Human Resources ”” → ““ WorkSheet ”=“ Human Resources ”” in this example (see FIG. 5B). .

(C) It is determined whether conversion processing has been performed on all sheet names of the “file before conversion” 103 existing on the server 101 (step S408). If not performed for all sheet names, the process moves to the next sheet name (step S409), and the conversion process (sheet name setting) is repeatedly executed.

(3) Conversion process (cell name setting) phase The spreadsheet software has a function to specify a cell range. For example, in the pre-conversion file, the cell name “cell range” for the range A4 to E11 Can be granted. This phase is a phase of cell name setting conversion processing performed by the format conversion processing unit 107 of the version conversion means 104.

(A) A cell name is acquired from the “file before conversion” 103 existing on the server 101 (step S410). Hereinafter, an example in which the cell name “cell range” is acquired from an arbitrary cell in the version “2000” file is shown in “”.

{Process 1} [Format element name setting table] 434 is searched to acquire the format element name.

  In this case, the search condition is <function group> column: “cell name setting” value “cell name setting”, <version> column: “file before conversion” version “2000”, and acquired value As a result, a <format element name> column “CellName” is obtained.

{Process 2} The setting information of the “file before conversion” 103 existing on the server 101 is searched, and the value set in the format element name is acquired. The search condition in this case is the format element name: “cell name” acquired in the format element name {process 1}, and the value ““ cell range ”set in the format element name“ cell name ”as the acquired value. "" Is obtained.

(B) A cell name is set in the “converted file” 105 created on the client PC 102 (step S411). Hereinafter, an example in which a cell name “cell range” is set in an arbitrary cell in the file of version “2003” is shown in “”.

{Process 3} [Format element name setting table] 434 is searched to acquire the format element name.

The search conditions in this case are as follows: <Function group> column: “cell name setting” value “cell name setting”, <version> column: “file after conversion” version “2003”
The <format element name> column ““ WorkCell ”” is obtained as the acquired value.

{Process 4} The setting information of the “post-conversion file” 105 created on the client PC 102 is searched, and a value is set to the format element name.

  The search condition in this case is the format element name: “format element name“ WorkCell ”” acquired in {process 3}, and the value ““ cell range ”” acquired in {process 2} is obtained as the setting value. It is done.

  Therefore, the process performed in the conversion process (cell name setting) phase is ““ CellName ”=“ cell range ”” ⇒ ““ WorkCell ”=“ cell range ”” in this example.

(C) It is determined whether or not conversion processing has been performed on all cell names of the “pre-conversion file” 103 existing on the server 101 (step S412). If not implemented for all, the process moves to the next cell name (step S413), and the conversion process (cell name setting) is repeatedly executed.

(4) Conversion Process (Line Display Setting) Phase This phase is a line display setting conversion processing phase performed by the format conversion processing unit 107 of the version conversion means 104.

(A) A line display attribute is acquired from the “file before conversion” 103 existing on the server 101 (step S414). An example of acquiring an attribute that an arbitrary line in the file of version “2000” is “non-display” is shown in “”.

{Process 1} [Format element name setting table] 435 is searched to acquire the format element name.

  The search conditions in this case are the <function group> column: the value “line display setting” “line display setting”, the <version> column: the “file before conversion” version “2000”, and the acquired value As a result, a <format element name> column ““ Line ”” is obtained.

{Process 2} The setting information of the “file before conversion” 103 existing on the server 101 is searched, and the value set in the format element name is acquired.

  The search condition in this case is the format element name “Line” acquired in the format element name {process 1}, and the value set in the format element value as the acquired value = format element value “NO” ] Is obtained.

{Process 3} [Format element value setting table] 435 is searched to acquire an attribute group.

  The search conditions in this case are as follows: <Function group> column: “Line display setting” value “Line display setting”, <Version> column: “File before conversion” version “2000”, <Format element value > Column: The value “NO” acquired in {Process 2}, and the <attribute group> column “Hidden” is obtained as the acquired value.

(B) A line display attribute is set in the “post-conversion file” 105 created on the client PC 102 (step S415). In addition, an example in which the attribute of “non-display” is set in an arbitrary line in the file of version “2003” is shown in “”.

{Process 4} [Format element name setting table] 435 is searched to acquire the format element name.

  The search conditions in this case are the <function group> column: the value “line display setting” “line display setting”, the <version> column: the version ““ 2003 ”” of “converted file”, and the acquired value As a result, a <format element name> column “Column” is obtained.

{Process 5} [Format element value setting table] 435 is searched to acquire a format element value.

  The search conditions in this case are as follows: <function group> column: “row display setting” value “row display setting”, <attribute group> column: value ““ hidden ”” acquired in {processing 3}, < Version> column: version ““ 2003 ”” of “converted file”, and <format element value> column “FALSE” is obtained as an acquired value.

{Process 6} The setting information of the “converted file” 105 created on the client PC 102 is searched, and the format element value is set in the format element name.

  The search condition in this case is the format element name: the format element name ““ Column ”” acquired in {Process 4}, and the value ““ FALSE ”” acquired in {Process 5} is obtained as the setting value.

  Therefore, in this example, the processing performed in the conversion processing (line display setting) phase is ““ Line ”=“ NO ”” → ““ Column ”=“ FALSE ””.

(C) It is determined whether or not the conversion process has been performed on all the rows of the “file before conversion” 103 existing on the server 101 (step S416). If not implemented for all, the process moves to the next line (step S417), and the conversion process (line display setting) is repeatedly executed.

(5) Conversion processing (column display setting) phase This phase is a column display setting conversion processing phase performed by the format conversion processing unit 107 of the version conversion means 104.

(A) A column display attribute is acquired from the “file before conversion” 103 existing on the server 101 (step S418). An example of acquiring an attribute that an arbitrary column in the file of version “2000” is “display” is shown in “”.

{Process 1} [Format element name setting table] 436 is searched to acquire the format element name.

  The search condition in this case is <function group> column: “column display setting” value “column display setting”, <version> column: “file before conversion” version “2000”, and acquired value As a result, a <format element name> column “Sequence” is obtained.

{Process 2} The setting information of the “file before conversion” 103 existing on the server 101 is searched, and the value set in the format element name is acquired.

  The search condition in this case is the format element name ““ Sequence ”” acquired in the format element name {process 1}, and the value set in the format element name as the acquired value = format element value ““ YES ” ] Is obtained.

{Process 3} [Format element value setting table] 436 is searched to acquire an attribute group.

  The search conditions in this case are as follows: <Function group> column: Value “column display setting” “column display setting”, <version> column: “file before conversion” version “2000”, <format element value > Column: The value “YES” acquired in {Process 2}, and the <attribute group> column “Display” is obtained as the acquired value.

(B) A column display attribute is set in the “converted file” 105 created on the client PC 102 (step S419). An example in which the attribute “display” is set in an arbitrary column in the version “2003” file is shown in “”.

{Process 4} [Format element name setting table] 436 is searched to acquire the format element name.

  The search condition in this case is <function group> column: “column display setting” value “column display setting”, <version> column: “converted file” version “2003”, and acquired value As a result, a <format element name> column ““ Row ”” is obtained.

{Process 5} [Format element value setting table] 436 is searched to acquire a format element value.

  The search conditions in this case are as follows: <Function group> column: “column display setting” value “column display setting”, <attribute group> column: value “display” acquired in {processing 3}, <version > Column: “Converted file” version “2003”, and <format element value> column “TRUE” is obtained as an acquired value.

{Process 6} The setting information of the “converted file” 105 created on the client PC 102 is searched, and the format element value is set in the format element name.

  The search condition in this case is the format element name: the format element name ““ Row ”” acquired in {Process 4}, and the value ““ TRUE ”” acquired in {Process 5} is obtained as the setting value.

  Therefore, in this example, the processing performed in the conversion processing (column display setting) phase is ““ Sequence ”=“ YES ”” → ““ Row ”=“ TRUE ””.

(C) It is determined whether or not conversion processing has been performed on all columns of the “file before conversion” 103 existing on the server 101 (step S420). If not implemented for all, the process moves to the next column (step S421), and the conversion process (column display setting) is repeatedly executed.

(6) Conversion processing (cell value setting / setting information) phase This phase is a cell value setting conversion processing phase (A) performed by the format conversion processing unit 107 of the version conversion means 104 and a setting information conversion processing phase. (B).

(A) Phase of conversion process (cell value setting) (a) A cell value is acquired from the “file before conversion” 103 existing on the server 101 (step S422). An example of obtaining a value “character string” set in an arbitrary cell in the file of version “2000” is shown in “”.

{Process 1} [Format element name setting table] 437 is searched to acquire the format element name.

  The search condition in this case is <function group> column: “cell value setting” value ““ cell value setting ””, <version> column: “file before conversion” version “2000”, A <format element name> column ““ Variable ”” is obtained as an acquired value.

{Process 2} The setting information of the “file before conversion” 103 existing on the server 101 is searched, and the value set in the format element name is acquired.

  The search condition in this case is the format element name: “format variable” acquired in {process 1}, and the value ““ character string ”” set in the format element name is obtained as the acquired value. (See (b) of FIG. 5A).

(B) The cell value is set in the “converted file” 105 created on the client PC 102 (step S423). An example in which a value “character string” is set in an arbitrary cell in the file of version “2003” is shown in “”.

{Process 3} [Format Element Name Setting Table] 437 is searched to acquire the format element name.

  The search condition in this case is <function group> column: “cell value setting” value “cell value setting”, <version> column: “file after conversion” version “2003”, The <format element name> column ““ Value ”” is obtained as the acquired value.

{Process 4} The setting information of the “post-conversion file” 105 created on the client PC 102 is searched, and a value is set to the format element name.

  The search condition in this case is the format element name: “format element name“ Value ”” acquired in {process 3}, and the value ““ character string ”” acquired in {process 2} is obtained as the setting value. (See (b) of FIG. 5B).

  Therefore, the processing performed in the conversion processing (cell value setting) phase so far is ““ Variable ”=“ character string ”” ⇒ ““ Value ”=“ character string ”” in this example.

(B) Conversion processing (cell setting information)
(A) Cell setting information (attributes) is acquired from the “file before conversion” 103 existing on the server 101 (step S424). An example of acquiring an attribute that the color of an arbitrary cell in the file of version “2000” is “red” is shown in “”.

{Process 5} [Format element name setting table] 438 is searched to acquire the format element name.

  The search condition in this case is as follows: <Function group> column: Arbitrary function group name (* Function group names not used in the conversion processing phases (2) to (5) and (6) above are [format "Sequentially read from the element name setting table]" "Cell color setting" ", <version> column: Version" "2000" "of" file before conversion ", <format element name> column as the acquired value “Tone” is obtained.

{Process 6} The setting information of the “file before conversion” 103 existing on the server 101 is searched, and the value set in the format element name is acquired.

  Search conditions in this case. Format element name: The format element name “Tone” acquired in {Process 5}, and the value set in the format element name = format element value “# FF0000” is obtained as the acquired value.

{Process 7} [Format element value setting table] 438 is searched to obtain an attribute group.

  The search conditions in this case are as follows: <function group> column: function group name “cell color setting” used in {Process 5}, <version> column: “file before conversion” version “2000”, <Format element value> column: The value “# FF0000” acquired in {Process 6}, and the <attribute group> column “Red” is obtained as the acquired value.

(B) Cell setting information (attributes) is set in the “converted file” 105 created on the client PC 102 (step S425).
An example in which the attribute of “red” is set as the color of an arbitrary cell in the file of version “2003” is shown in “”.

{Process 8} Search the [format element name setting table] 438 to obtain the format element name.

  The search conditions in this case are <function group> column: function group name ““ cell color setting ”” used in {process 5}, <version> column: “file after conversion” version “2003” Yes, the <format element name> column “Color” ”is obtained as an acquired value.

{Process 9} [Format element value setting table] 438 is searched to acquire the format element value.

  The search conditions in this case are as follows: <Function group> column: Function group name “cell color setting” used in {Process 5}; <Attribute group> column: Value acquired in {Process 7} “Red” ], <Version> column: version ““ 2003 ”” of “file after conversion”, and <format element value> column “RED” ”is obtained as an acquired value.

{Process 10} The setting information of the “post-conversion file” 105 created on the client PC 102 is searched, and the format element value is set in the format element name.

  The search condition in this case is the format element name: the format element name “Color” acquired in {Process 8}, and the value ““ RED ”” acquired in {Process 9} is obtained as the setting value.

  Therefore, the processing performed in the conversion processing (cell setting information) phase thus far is ““ Tone ”=“ # FF0000 ”” → ““ Color ”=“ RED ”” in this example.

(C) It is determined whether the conversion process has been performed on the setting information (attributes) of all the cells of the “pre-conversion file” 103 existing on the server 101 (step S426). If not implemented for all, the process moves to the setting information (attribute) of the next cell (step S427), and the conversion process (cell setting information) is repeatedly executed.

(D) It is determined whether or not the conversion process has been performed on all the cells of the “file before conversion” 103 existing on the server 101 (step S428). If not implemented for all, the process moves to the next cell (step S429), and the conversion process (cell value setting / setting information) is repeatedly executed.

(7) Reflection processing to all sheets (a) Determination of whether each conversion processing of (4) to (6) has been performed on all sheets of the “file before conversion” 103 existing on the server 101 Is performed (step S430). If not implemented for all, the process moves to the next sheet (step S431), and the conversion processes (4) to (6) are repeated.

(B) If conversion processing has been performed for all sheets, the processing of this program ends.

  The types of format elements in the embodiment described above are merely examples, and other format elements may be included, and it is not necessary to include all the format elements shown in the embodiment. Not too long.

  In the above embodiment, the format information database 108 includes three format element name setting tables (FIG. 2-A), format element value setting tables (FIG. 2-B), and software information registration tables (FIG. 2-C). Although the case where it consists of a table was demonstrated, it is not restricted to this, As long as the same content is contained, it may have what kind of database form.

  Note that the processing and functions performed by the version search unit 106 (version information acquisition processing unit 109) shown in the flowchart of FIG. 3 and the version conversion unit 104 (format) shown in the flowcharts of FIGS. The processing and functions performed in the conversion processing unit 107) are implemented by each means (each processing unit) using hardware resources such as a CPU, memory, and various registers built in the computers that constitute the client PC 102 and the server 101. This is realized by executing a program corresponding to the processing to be performed. Further, these programs can be widely distributed in the market via computer-readable recording media such as FD, CD-ROM, and DVD, and networks such as the Internet.

101: Server on which a version conversion system is installed 102: Client computer (client PC)
103: Spreadsheet to be converted (pre-conversion file)
104: Version conversion means (means for converting format elements of a spreadsheet file)
105: Spreadsheet file after conversion (converted file)
106: Virgin search means (means for searching for spreadsheet software installed in the client PC)
107: Format conversion processing unit (processing unit for converting format elements of a spreadsheet file)
108: Format information database (a database for registering software information of a master and client PC that manages format element information)
109: Version information acquisition processing unit (processing unit for acquiring the version of the spreadsheet software installed in the client PC)
110: Spreadsheet software (Spreadsheet software installed on the client PC)
306, 432: Format information database (software information registration table)
433, 434, 437: Format information database (format element name setting table)
435, 436, 438: Format information database (format element name setting table and format element value setting table)

Claims (3)

A version conversion system for automatically converting a spreadsheet file existing on a server into a spreadsheet software version installed on a client PC,
A format information database that manages information for absorbing differences between versions of spreadsheet files;
Version search means for collecting the version of the spreadsheet software installed in the client PC referring to the spreadsheet file existing on the server;
The spreadsheet that exists on the server based on the version of the spreadsheet software collected by the version search means, the version and setting information of the spreadsheet file that exists on the server, and the contents of the format information database. Version conversion means for automatically converting a file into a version of spreadsheet software installed on a client PC that refers to the spreadsheet file;
Have
The format information database is provided for absorbing differences between versions of format element names (names uniquely identifying format elements that define formats), and format elements defined for each version of spreadsheet software. Specified for each version of the spreadsheet software provided to absorb the differences between the version of the format element name setting table for registering the name and the version of the format element value (value that uniquely identifies the attribute of the format element) A format element value setting table for registering format element values, and a software information registration table for registering the type (name) and version of the spreadsheet software installed on the client PC,
The version conversion means includes the version and setting information of a spreadsheet file existing on the server, the version of spreadsheet software installed on the client PC collected by the version search means, and the format element name setting table. And automatically converting the spreadsheet file existing on the server into the spreadsheet file of the spreadsheet software version of the client PC based on the format element value setting table and the contents of the software information registration table. Version conversion system. A version conversion method for automatically converting a spreadsheet file existing on a server into a spreadsheet software version installed on a client PC,
A version search procedure for collecting the version of the spreadsheet software installed in the client PC referring to the spreadsheet file existing on the server;
Format for managing said version search procedure was collected in the spreadsheet software version, and version and configuration information for the spreadsheet file that exists on the server, the information for absorbing differences between the versions of the spreadsheets Based on the contents of the information database, the format information database is referred to, and the spreadsheet file existing on the server is automatically converted to the version of the spreadsheet software installed on the client PC that references the spreadsheet file. Version conversion procedure to
The format information database is provided for absorbing differences between versions of format element names (names uniquely identifying format elements that define formats), and format elements defined for each version of spreadsheet software. Specified for each version of the spreadsheet software provided to absorb the differences between the version of the format element name setting table for registering the name and the version of the format element value (value that uniquely identifies the attribute of the format element) A format element value setting table for registering format element values, and a software information registration table for registering the type (name) and version of the spreadsheet software installed on the client PC,
The version conversion procedure, and version of the version search hand spreadsheet software installed on the client PC that has been collected by the order, and version and configuration information for the spreadsheet file that exists on the server, the format element name setting This is a procedure for automatically converting a spreadsheet file existing on the server into a spreadsheet file of the spreadsheet software version of the client PC based on the table, the format element value setting table, and the contents of the software information registration table. A version conversion method characterized by that.   The program for making a computer perform each procedure in the version conversion method of Claim 2.

Images