Image processing apparatus, control method therefor, and storage medium

Abstract

In a case where the name of the address book to be imported is a default name, the name of a stored address book is set as the name of the address book to be imported. A control method for an image processing apparatus includes storing, in a storage, an address book, importing an address book from an external apparatus, determining whether a name of an address book imported by the importing is a default name or not, and in a case where the name of the address book imported by the importing is a default name, setting a name of an address book stored in the storage as the name of the address book to be imported by the importing.

Claims

1. A communication apparatus, comprising: a storage device that stores a plurality of destination tables, wherein the plurality of destination tables includes a first destination table, and each of the plurality of destination tables has an identifier, a name and destination data; at least one memory storing instructions; and at least one processor executing the instructions causing the communication apparatus to: receive an input of an import destination; receive a second destination table to be imported into the storage device from an external apparatus; perform, in a case where destination data included in the second destination table is imported while deleting data of the first destination table stored in the storage device and designated as an import destination, a first determination process for determining whether a name of the second destination table is a default name, wherein the default name is not a name set according to a user instruction; and import the destination data included in the second destination table into the storage device, wherein, in a case where it is determined that the name of the second destination table is the default name, a name of the first destination table which has been stored in the storage device is used as a name of a destination table of the imported destination data, and wherein, in a case where the destination data included in the second destination table is imported while being added to data of the first destination table stored in the storage device and designated as an import destination, the first determination process is not performed.

2. The communication apparatus according to claim 1, wherein the instructions further cause the communication apparatus to perform a second determination process for determining whether a type of the second destination table is matched with a type of the first destination table stored in the storage device or not, and wherein, in a case where it is determined that the type of the second destination table is matched with the type of the first destination table, the name of the second destination table is used as the name of destination table of the imported destination data.

3. The communication apparatus according to claim 1, wherein, in a case where it is determined that the type of the second destination table is not matched with the type of the first destination table, the first determination process is further performed.

4. A method for controlling a communication apparatus including a storage device that stores a plurality of destination tables, wherein the plurality of destination tables includes a first destination table, and each of the plurality of destination tables has an identifier, a name and destination data, comprising: receiving an input of an import destination; receiving a second destination table to be imported into the storage device from an external apparatus; performing, in a case where destination data included in the second destination table is imported while deleting data of the first destination table stored in the storage device and designated as an import destination, a first determination process for determining whether a name of the second destination table is a default name, wherein the default name is not a name set according to a user instruction; and importing the destination data included in the second destination table into the storage device, wherein, in a case where it is determined that the name of the second destination table is the default name, a name of the first destination table which has been stored in the storage device is used as a name of the imported destination table, and wherein, in a case where the destination data included in the second destination table is imported while being added to data of the first destination table stored in the storage device and designated as an import destination, the first determination process is not performed.

5. The method according to claim 4, further comprising performing a second determination process for determining whether a type of the second destination table is matched with a type of the first destination table stored in the storage device or not, and wherein, in a case where it is determined that the type of the second destination table is matched with the type of the first destination table, the name of the second destination table is used as the name of destination table of the imported destination data.

6. The method according to claim 4, wherein, in a case where it is determined that the type of the second destination table is not matched with the type of the first destination table, the first determination process is further performed.

7. The communication apparatus according to claim 1, wherein, in a case where it is determined that the name of the second destination table is not the default name, the name of the second destination table is used as the name of the destination table of the imported destination data.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) The attached drawings illustrate embodiments of the present disclosure.

(2) FIG. 1 illustrates a configuration of an entire system according to a first embodiment of the present invention.

(3) FIG. 2 is a block diagram illustrating a hardware configuration of an image processing apparatus according to the first embodiment.

(4) FIG. 3 illustrates an exemplary configuration of an address book related module in the image processing apparatus according to the first embodiment.

(5) FIG. 4 illustrates a display example of a name list in address books displayed on an operating unit in the image processing apparatus according to the first embodiment.

(6) FIGS. 5A to 5D illustrate management of destination table data managed in a destination table DB, a personal destination table DB and a group destination table.

(7) FIG. 6 illustrates an example of a management table describing which user is associated with which user group according to the first embodiment.

(8) FIG. 7 illustrates a relationship among user groups, group destination tables, and destination data according to the first embodiment.

(9) FIGS. 8A to 8C illustrate example data (destination table data for import) as a result of export of the destination table data illustrated in FIGS. 5A to 5D.

(10) FIG. 9A illustrates an import screen example in a case of import to an image processing apparatus displayed on a web browser in a computer according to the first embodiment, and FIG. 9B illustrates a data structure of destination table data for import.

(11) FIG. 10 is a flowchart illustrating import processing to be performed on destination table data in the image processing apparatus according to the first embodiment.

(12) FIG. 11 illustrates destination table data under SYSTEM FIRST DESIGN DIVISION after the import processing is completed.

(13) FIG. 12 is a flowchart illustrating import processing to be performed on destination table data in an image processing apparatus according to a second embodiment.

(14) FIG. 13 illustrates an example confirmation window to be displayed on an operating unit in an image forming apparatus according to a third embodiment.

DESCRIPTION OF THE EMBODIMENTS

(15) Embodiments of the present disclosure will be described in detail below with reference to the attached drawings. It is not intended that the following embodiments limit the scope of the present disclosure, and all the combinations of features according to the described embodiments are not necessary in all embodiments of the present disclosure.

First Embodiment

(16) FIG. 1 illustrates a configuration of an entire system according to a first embodiment of the present disclosure.

(17) Image processing apparatuses 103 and 105 are multifunction peripherals (MFPs) which may have a scan function, a print function, a facsimile function, and a box function, for example. Each of the image processing apparatuses 103 and 105 may be configured to digitize image data scanned from a document, for example, and transmit it to a shared folder, for example, in a computer 101, which is an example of an external apparatus, over a network 104. Each of the image processing apparatuses 103 and 105 has a user authentication function, and when a user operates the image processing apparatus 103 or 105, an administrator of the apparatus can set whether the user is to be authenticated or not. User names, passwords and so on to be used for such user authentication can be managed by the image processing apparatuses 103 and 105 but may be managed by an authentication server 102 over the network 104.

(18) The image processing apparatus 103 can export destination data, including a destination table list (which will be described with reference to FIG. 4) stored in the image processing apparatus 103, from a web browser on the computer 101 over the network 104. The destination table data (hereinafter, called destination table data for import) including the thus exported destination table list is imported to the other image processing apparatus 105 by the computer 101 over the network 104. Alternatively, the image processing apparatus 103 may be connected to the image processing apparatus 105 over the network 104 so that the destination data can be directly distributed from the image processing apparatus 103 to the image processing apparatus 105 without going through the computer 101.

(19) The following description assumes that destination table data is imported from the image processing apparatus 103 to the computer 101 and is imported from the computer 101 to the image processing apparatus 105 but may be vice versa.

(20) FIG. 2 is a block diagram illustrating a hardware configuration of the image processing apparatus 103 according to the first embodiment. The following description is also applicable to the image processing apparatus 105.

(21) The CPU 201 decompresses a program stored in a ROM 209 into a RAM 208 and controls operations of the entire image processing apparatus 103 by executing the decompressed program. The CPU 201 communicates with components in the image processing apparatus 103 through a bus 202. A printer 204 is configured to print on recording paper (or sheet) an image based on image data input thereto. A scanner 205 is configured to scan an image on a document placed on a platen glass by a user and store the image data acquired by the scanning in an HDD 203 or the RAM 208. The scanner 205 includes a document conveying device, not illustrated, which can sequentially convey a plurality of documents loaded in the document conveying device onto the platen glass for scanning. The HDD 203 is a hard disk drive and can save image data input from the scanner 205 and user data (such as an address book). An operating unit 206 may include a plurality of keys usable by a user for giving an instruction and a display unit configured to display information to be notified to the user. A network I/F 207 is configured to connect the image processing apparatus 103 to the network 104 and is configured to control transmission of image data acquired by scanning performed by the scanner 205 to a file shared server (not illustrated) on the network. A FAX 210 is configured to transmit and receive image data through a telephone line.

(22) FIG. 3 illustrates a configuration example of address book related modules in the image processing apparatus 103 according to the first embodiment. The modules illustrated in FIG. 3 correspond to programs stored in the ROM 209, and the programs may be decompressed into the RAM 208 for execution. The CPU 201 executes the decompressed programs to implement the functions of the modules.

(23) An address book administration module 301 is configured to manage destination table data (including names of destination tables and destination data). Among destination table data managed by the address book administration module 301 is the destination table data which can be accessed by all users, which is saved in a destination table DB (database) 310 in the HDD 203.

(24) A user personal/group module 302 is configured to manage user information (login IDs (or user IDs) and passwords) of users and manage which user is associated with which user group (which will be described with reference to FIG. 6). A personal/group destination table administration module 303 is configured to manage personal destination table data which can be accessed by a user only and group destination table data which can be accessed by users belonging to a certain user group only. Among destination table data (including names of destination tables and destination data) managed by the personal/group destination table administration module 303 is personal destination table data which is saved in the personal destination table DB 311 in the HDD 203. The group destination table data is saved in a group destination table DB 312 in the HDD 203.

(25) The address book administration module 301 is configured to manage personal destination table data and group destination table data through the personal/group destination table administration module 303.

(26) In various embodiments, a plurality of destination tables can be registered with the destination table DBs 310 to 312.

(27) FIG. 4 illustrates a display example of a name list of destination tables displayed on the operating unit 206 in the image processing apparatus 103 according to the first embodiment. The list 401 displays a list of names of destination tables stored in the destination table DB 310, the personal destination table DB 311, and the group destination table DB 312.

(28) The address book administration module 301 in response to a request to display the name list 401 of destination tables from the operating unit 206 obtains names of destination tables from the destination table DB 310, the personal destination table DB 311 and the group destination table DB 312 in the HDD 203. The obtained name list 401 is displayed on the operating unit 206. The request to display the name list 401 of destination tables from the operating unit 206 can include an instruction to display a name list of destination tables in a specific destination table DB among the destination table DB 310, the personal destination table DB 311, the group destination table DB 312.

(29) The names of destination tables to be registered with the destination table DB 310, the personal destination table DB 311 and the group destination table DB 312 may be arbitrarily set by users. However, in a case where a user does not explicitly set a name, the address book administration module 301 sets a default destination table name. The default destination table name is set by the address book administration module 301 so as not to overlap with names in the destination table DB 310, the personal destination table DB 311 and the group destination table DB 312. For example, DESTINATION TABLE may be set as a destination table name in the destination table DB 310, PERSONAL DESTINATION TABLE may be set as a destination table name in the personal destination table DB 311, and GROUP DESTINATION TABLE may be set as a destination table name in the group destination table DB 312.

(30) Next, a user may select an arbitrary destination table name from the name list 401 of destination tables displayed on the operating unit 206. Thus, the address book administration module 301 obtains destination data from the destination table DB storing the selected destination table and displays it on the destination display unit 402. In the example in FIG. 4, DESTINATION TABLE 1 is selected from the list 401, and the name (\\smhost\user1) of the destination table and destination data (user1@test.com) are displayed on a destination display region 402. Referring to FIG. 4, the names of group destination tables excluding the name displayed as SYSTEM FIRST DESIGN DIVISION are default destination table names.

(31) FIGS. 5A to 5C illustrate management of destination table data in the destination table DB 310, the personal destination table DB 311, and the group destination table DB 312.

(32) FIG. 5A illustrates example destination table data managed in the destination table DB 310. The destination table DB 310 stores a total of ten destination tables, and 1 to 10 are uniquely allocated as destination table IDs 501 of the destination tables. A name 502 of a destination table and destination data 503 are stored in the HDD 203 in association with the corresponding destination table.

(33) FIG. 5B illustrates example destination table data managed in the group destination table DB 312.

(34) Group destination table IDs 504 of 1 to N (where N varies dynamically according to the corresponding setting) are uniquely allocated to corresponding group destination tables. A group destination table name 505, an accessible affiliation group 506, and destination data 507 are stored in the HDD 203 in association with the corresponding group destination table. Referring to FIG. 5B, the name having 2 as a group destination table ID 504 is not a default name.

(35) FIG. 5C illustrates example destination data managed in the personal destination table DB 311.

(36) Personal destination table IDs 508 of 1 to N (where N varies dynamically according to the corresponding setting) are uniquely allocated to corresponding personal address books. A personal destination table name 509, an accessible affiliation user 510, and destination data 511 are stored in the HDD 203 in association with the corresponding personal address book. Here, no number for uniqueness is given at the end of a default name for the personal destination table name 509. This is because each personal destination table is a destination table owned by a user and is not accessible by other users.

(37) FIG. 5D illustrates example data saved as destination data which may include a destination name and a source host name, for example.

(38) FIG. 6 illustrates an example management table describing which user is associated with which user group according to the first embodiment. The management table is stored in the HDD 203.

(39) A unique group ID 601 is allocated to each user group. Under USER GROUP 602, a name of the corresponding user group is given. An affiliation user 603 for user authentication for accessibility is allocated to each user group. For example, UserA, UserB, and UserC allocated to GroupA having 1 as group ID 601 are affiliation users 603 for user authentication for accessibility.

(40) The user personal/group module 302 is configured to search a name of a user received from the address book administration module 301 through the management table and return a list of all user groups to which the user belongs to the address book administration module 301.

(41) FIG. 7 illustrates a relationship among user group, group destination table, and destination data according to the first embodiment.

(42) The relationship is managed in a tree structure having a node of each user group (such as GroupA) associated with a destination table of the group thereunder and further having destination data thereunder.

(43) FIG. 8A illustrates an example of data (destination table data for import) acquired by exporting destination table data with 1 as a destination table ID 501 illustrated in FIG. 5A.

(44) A name (DESTINATION TABLE 1 here) of a destination table is set under AddressBook Name. If a default destination table name is set, the default destination table name can be directly set under the item. However, if no name is set, it is handled as a default destination table name. The identifier under AddressBook ID indicates the type of destination table. Here, 1 under AddressBook ID indicates a normal destination table stored in the destination table DB 310.

(45) Referring to FIGS. 8A to 8C, data enclosed by < and > correspond to one destination data set. Destination table data for import in FIG. 8A include three destination data sets (destination 1, destination 2, and destination 3).

(46) FIG. 8B illustrates an example of data (destination table data for import) acquired by exporting destination data of a group destination table having 2 as a destination table ID in FIG. 5B.

(47) A name (SYSTEM FIRST DESIGN DIVISION here) of the group destination table is set under GroupAddressBook Name. If a default destination table name is set here, the default destination table name may directly be set. However, if no name is set there, it is determined as a default destination table name. The identifier for GroupAddressBook ID indicates the type of destination table. A type 2 indicates a group destination table stored in the group destination table DB 312 illustrated in FIG. 5B. Referring to FIG. 5B, the destination table data for import include two destination data sets (destination C and destination D).

(48) FIG. 8C illustrates an example of data (destination table data for import) acquired by exporting destination table data of a personal destination table having 1 as a destination table ID in FIG. 5C.

(49) Under MyAddressBook Name, a name (PERSONAL DESTINATION TABLE here) of a destination table in a personal destination table is set. If a default destination table name is set here, the default destination table name may directly be set. However, if no name is set there, it is determined as a default destination table name. The identifier under MyAddressBook ID indicates the type of destination table, and 1 indicates a personal destination table stored in the personal destination table DB 311. Referring to FIG. 5C, the destination table data for import include two destination data sets (destination A1 and destination A2).

(50) The destination table data for import illustrated in FIGS. 8A to 8C are stored in a storage device (such as an HDD) in the computer 101.

(51) FIG. 9A illustrates a screen example to be displayed by a web browser of the computer 101 in a case where the destination table data for import in FIGS. 8A to 8C, for example, is to be imported to the image processing apparatus 105 over the network 104.

(52) Destination tables in import destination 901 displays a list of destination table data sets managed in the destination table DB 310, the personal destination table DB 311 and the group destination table DB 312 obtained from the image processing apparatus 105 being an import destination. Here, the destination tables 901 display a list of destination tables in the image processing apparatus 105 to which the destination table data for import illustrated in FIGS. 8A to 8C, for example, is to be imported and are usable for designating a destination table as an import destination. The list may be scrolled with a scroll bar 904 to designate an arbitrary destination table. In the example in FIG. 9A, SYSTEM FIRST DESIGN DIVISION 910 is selected as an import destination.

(53) A destination table in import source 902 corresponds to a designated location of the destination table data for import which is exported from the image processing apparatus 103 and is saved in the computer 101. An import method 903 corresponds to a mode selected for importing the destination table data for import illustrated in FIGS. 8A to 8C, for example. If ADD is selected, the destination table data in the import destination is kept, and the destination data of the destination table data for import, which is designated at the destination table in import source 902, is imported by adding it to the destination table data in the destination table data in the import destination 901.

(54) On the other hand, if DELETE AND OVERWRITE is selected as illustrated in FIG. 9A, all of destination table data designated in the destination tables in the import destination 901 are deleted, and the destination table data for import, which is designated at the destination table in import source 902, is then imported.

(55) When a START IMPORTING button 905 is pressed after the items are set on the screen as illustrated in FIG. 9A, the importing with a data structure illustrated in FIG. 9B is executed to the image processing apparatus 105 over the network 104.

(56) The data structure in FIG. 9B has the items set in FIG. 9A so that the destination table data can be imported to the image processing apparatus 103. Referring to FIG. 9B, DELETE AND OVERWRITE as an import method and AddressBook ID:2 stored in the destination table DB 310 as an import destination are designated.

(57) FIG. 10 is a flowchart illustrating destination table data import processing in the image processing apparatus 105 according to the first embodiment. The processing illustrated in the flowchart can be implemented by the CPU 201 executing programs stored in the ROM 209 in the image processing apparatus 105 and decompressed into the RAM 208.

(58) According to the first embodiment, the destination table data for import in FIG. 8A is to be imported to SYSTEM FIRST DESIGN DIVISION designated at the destination table in import destination 901. It is assumed here that the destination table data in SYSTEM FIRST DESIGN DIVISION in an import destination before the importing is the destination table data illustrated in FIG. 5B, for example.

(59) The processing illustrated in the flowchart is started in response to press of the START IMPORTING button 905 on the screen in FIG. 9A and reception of the destination table data for import from computer 101 in the data structure in FIG. 9B.

(60) First, the CPU 201 in S1001 functions as the address book administration module 301 and receives destination table data for import in the data structure illustrated in FIG. 9B and advances the processing to S1002. In S1002, the CPU 201 identifies the import method set at the import method 903. If the import method is ADD, the processing moves to S1011 where the CPU 201 obtains the destination table in the import destination from the data in FIG. 9B. Destination data is obtained from the destination table data in FIG. 9B for the obtained destination table, and the add import processing is performed on the existing destination table data. Then, the processing ends. If the import destination table is a personal destination table or a group destination table, the import processing is performed through the personal/group destination table administration module 303.

(61) On the other hand, if the CPU 201 in S1002 identifies DELETE AND OVERWRITE as the import method, the processing moves to S1003 where the type of destination table is obtained from the destination data in FIG. 9B. The type of destination table can be obtained by obtaining the identifier AddressBook ID/GroupAddressBook ID/MyAddressBook ID which is described with reference to FIGS. 8A to 8C. Next, in S1004, the CPU 201 determines whether the type of import source destination table obtained in S1003 is matched with the type of destination table in the import destination in FIG. 9B. If it is determined that they are not matched, the processing moves to S1005 where the name of the destination table is obtained from the destination table data in FIG. 9B. The name of the destination data can be obtained by obtaining the name set in the identifier AddressBook Name/GroupAddressBook Name/MyAddressBook Name described with reference to the destination table data in FIGS. 8A to 8C. In S1006, the CPU 201 determines whether the obtained destination table name is a default name or not. It is a default name if it is matched with one of default names for destination tables or if no name is set, as illustrated in FIGS. 8A to 8C. If the CPU 201 in S1006 determines that a default name is set, the processing moves to S1007 where the destination table designated as the import destination in FIG. 9B is obtained, and the destination table data in the import destination is only deleted. In S1008, the CPU 201 obtains only the destination data from the destination table data in FIG. 9B and imports the destination data to the destination table in the import destination. Then, the processing ends.

(62) In DELETE AND OVERWRITE mode, if the destination table name in the destination table data for import is a default name, the name of the destination table in the import destination is kept, and the destination data is only overwritten.

(63) FIG. 11 exemplarily illustrates destination table data of SYSTEM FIRST DESIGN DIVISION after the import processing in S1008 completes. Like numbers refer to like parts in FIG. 5B and FIG. 11.

(64) The destination data having 2 as a group destination table ID in FIG. 11 keeps the name (SYSTEM FIRST DESIGN DIVISION) of the group destination table before importing as the name 505 of the group destination table. On the other hand, in the destination data 507, the destination data included in the destination table data for import in FIG. 8A is changed from DESTINATION C, DESTINATION D in FIG. 5B to DESTINATION 1, DESTINATION 2, DESTINATION 3.

(65) If the CPU 201 in S1006 determines that no default name is set, the processing moves to S1009 where the import destination table in the data in FIG. 9B is obtained, and the destination table name in the destination table data and destination data in the import destination are deleted. In S1010, the CPU 201 obtains the destination table data in the data in FIG. 9B and imports it to the import destination table. Then, the processing ends.

(66) If it is determined in S1004 that the types of the destination tables are matched, the processing in S1009 and S1010 is executed. Then, the processing ends.

(67) According to the first embodiment, as described above, overlapping of identical default destination table names can be prevented when destination data for import having the default destination table name is imported to a different type of destination table in the delete and overwrite mode.

(68) If the destination table name is a default name or is not set, the name of the destination table in the import destination is saved. Thus, a user can identify the type of destination data from the name of the destination table for improved usability.

Second Embodiment

(69) FIG. 12 is a flowchart illustrating import processing on destination table data in the image processing apparatus 105 according to a second embodiment. The processing illustrated in the flowchart can be implemented by execution, by the CPU 201, of programs stored in the ROM 209 and decompressed into the RAM 208. Like numbers refer to like parts in FIG. 10 and FIG. 12, and any repetitive description will be omitted. Because the system configuration and the configurations of the image processing apparatuses 103 and 105 according to the second embodiment are the same as those of the first embodiment, any repetitive description will be omitted.

(70) Because the processing according to the second embodiment is the same as the processing illustrated in FIG. 10 except for processing in S1201 added to the processing in the flowchart illustrated in FIG. 10, differences will only be described.

(71) If it is determined in S1004 that the types of the destination tables are matched, the processing moves to S1201 where the CPU 201 determines whether the ID set for the type of destination table in destination data for import is matched with the ID set for the type of the destination table in the import destination or not.

(72) The ID set for the type of destination table may be a value set for the identifier AddressBook ID/GroupAddressBook ID/MyAddressBook ID illustrated in FIGS. 8A to 8C, for example. Referring to FIG. 8A, the AddressBook ID being an identifier of the destination table is 1. The ID is the same as the destination table ID (501, 504, 508) illustrated in FIGS. 5A to 5C. If the CPU 201 in S1201 determines that the value of the ID set for the type of destination table is different, the processing moves to S1005 where, if the name of the destination table in the destination data for import is a default name, the destination data of the import destination address book is only updated. On the other hand, if it is determined in S1201 that the ID set for the type of destination table in the destination data for importing is matched with the ID set for the type of the destination table in the import destination, the processing moves to S1009, and the destination table in the import destination is updated with the destination table data in the destination data for import.

(73) According to the second embodiment, as described above, when the destination data for import having a default destination table name is to be imported in the delete and overwrite mode, a destination table name which is not of a specific type can be prevented from being changed to the default name. This can prevent overlapping setting of an identical default destination table name.

Third Embodiment

(74) According to the first and second embodiments, the destination table name in the import destination is not set when it is determined in S1006 in FIG. 10 and FIG. 12 that a default name is set as the name of the destination table included in the destination table data for import. According to the third embodiment, on the other hand, the name of the destination table in the import destination may be prevented from being deleted at all times without performing the default name determination processing in S1006. In other words, after the processing in S1005, the processing in S1007 and S1008 may be performed at all times. Because the system configuration and the configurations of the image processing apparatuses 103 and 105 according to the third embodiment are the same as those of the first embodiment, any repetitive description will be omitted.

(75) According to the third embodiment, the name of the destination table in the import destination can be kept at all times, which can prevent overlapping setting of an identical default destination table name.

Fourth Embodiment

(76) According to the first to third embodiments, whether the destination table name included in the destination table data for import or the name of the destination table in the import destination is to be used is selected in the import destination image processing apparatus. According to a fourth embodiment on the other hand, the processing in S1006 is replaced by processing for determining whether the name of the destination table included in the destination table data for import is matched with the name of the import destination table or not. If the names of the destination tables are not matched, a confirmation window as illustrated in FIG. 13 may be displayed on the operating unit 206 so that a user can select which destination table name is to be used. Because the system configuration and the configuration of the image processing apparatuses 103 and 105 according to the fourth embodiment are the same as those of the first embodiment, any repetitive description will be omitted.

(77) FIG. 13 illustrates an example of the confirmation window to be displayed on the operating unit 206 in the image forming apparatus 105 according to the fourth embodiment.

(78) Referring to FIG. 13, names of destination tables in an import source and in an import destination are simultaneously displayed for improved usability.

(79) If NAME OF DESTINATION TABLE IN IMPORT SOURCE is selected on the screen in FIG. 13, the processing in S1009 and S1010 is performed so that the name of the destination table in the import source can be set as the name of the destination table in the import destination.

(80) If NAME OF DESTINATION TABLE IN IMPORT DESTINATION is selected on the screen in FIG. 13, the processing in S1007 and S1008 is performed so that the name of the destination table in the import destination can be kept.

(81) According to the fourth embodiment, a user can select the name of the destination table in the import source or the name of the destination table in the import destination to be kept. Thus, the name of the destination table in the import destination can be set to the destination table name intended by the user.

(82) According to the aforementioned embodiments, the destination table data for import only contain one type of destination table and one destination table name. However, embodiments of the present disclosure are also applicable to a case where there is a plurality of types of destination table and a plurality of destination table names, and a plurality of destination data sets are included for each of them. In other words, in a case where a plurality of types of destination table, the processing in S1003 and S1004 is performed on the plurality of types of destination table. If even one type is different, the processing in and subsequent to S1005 is performed.

(83) The same is true for destination table names, and the processing in S1005 and S1006 is performed on a plurality of destination table names. If even one default name is included therein, the processing in and subsequent to S1007 may be performed.

Other Embodiments

(84) Various embodiments of the present disclosure can be implemented by processing of reading out and executing, by one or more processors in a computer in a system or an apparatus, a program implementing one or more functions according to the aforementioned embodiments which are supplied to the system or the apparatus over a network or through a storage medium. An embodiment of the present disclosure can also be realized by a circuit (such as an ASIC) which implements the one or more function.

(85) Embodiment(s) of the present disclosure can also be realized by a computer of a system or apparatus that reads out and executes computer executable instructions (e.g., one or more programs) recorded on a storage medium (which may also be referred to more fully as a non-transitory computer-readable storage medium) to perform the functions of one or more of the above-described embodiment(s) and/or that includes one or more circuits (e.g., application specific integrated circuit (ASIC)) for performing the functions of one or more of the above-described embodiment(s), and by a method performed by the computer of the system or apparatus by, for example, reading out and executing the computer executable instructions from the storage medium to perform the functions of one or more of the above-described embodiment(s) and/or controlling the one or more circuits to perform the functions of one or more of the above-described embodiment(s). The computer may comprise one or more processors (e.g., central processing unit (CPU), micro processing unit (MPU)) and may include a network of separate computers or separate processors to read out and execute the computer executable instructions. The computer executable instructions may be provided to the computer, for example, from a network or the storage medium. The storage medium may include, for example, one or more of a hard disk, a random-access memory (RAM), a read only memory (ROM), a storage of distributed computing systems, an optical disk (such as a compact disc (CD), digital versatile disc (DVD), or Blu-ray Disc (BD)), a flash memory device, a memory card, and the like.

(86) While exemplary embodiments have been described, it is to be understood that the disclosure is not limited to the disclosed exemplary embodiments. The scope of the following claims is to be accorded the broadest interpretation so as to encompass all such modifications and equivalent structures and functions.

(87) This application claims the benefit of Japanese Patent Application No. 2016-186140 filed Sep. 23, 2016, which is hereby incorporated by reference herein in its entirety.