JP7821640B2 - Information processing systems, printers, programs - Google Patents

Description

The present invention relates to an information processing system, a printer, and a program.

Conventionally, to prevent discrepancies in the content printed on labels affixed to products at multiple chain stores, the content printed by multiple printers has been centrally managed by a server. This centrally managed printing data is updated periodically or irregularly.
For example, Patent Document 1 discloses that a management server acquires registered image data stored in a connected representative printer from the representative printer, and updates registered image data stored in printers other than the representative printer based on the acquired registered image data, thereby maintaining the identity of the registered image data stored in the representative printer and the registered image data stored in the other printers.

JP 2013-210727 A

Even when printing content from multiple chain stores is centrally managed by a server, some stores may have unique products, and store staff may create data for printing labels to be affixed to such unique products and save it on the printer. However, in the past, there was a problem in that data created independently by stores was overwritten and deleted when the server updated the data.

The present invention aims to prevent data edited by a printer from being deleted when updating the printer's data based on data received from an information processing device.

One aspect of the present invention is an information processing system including an information processing device and a printer capable of communicating with the information processing device.
The information processing device includes:
The printer includes a storage unit that stores layout data indicating a layout when printing is performed by the printer, and reference data that is associated with the layout data and that is referenced when printing is performed.
The printer
a storage unit having a first storage area and a second storage area;
a data updating unit that updates the layout data and reference data in the first storage area with the layout data and reference data received from the information processing device at a predetermined data update timing;
The data editing unit edits the reference data in the first storage area based on a user's operation input, and records edited data, which is the edited reference data, in the second storage area.

According to one aspect of the present invention, when updating printer data based on data received from an information processing device, it is possible to prevent data edited by the printer from being deleted.

1 is a system configuration diagram of an information processing system according to an embodiment. FIG. 10 is a diagram illustrating an example of a project file creation screen of the information processing apparatus according to the embodiment. 10A and 10B are diagrams showing a procedure for displaying a call table definition in the information processing device according to the embodiment. 10A and 10B are diagrams showing a procedure for displaying a call table in the information processing device according to the embodiment; 10A and 10B are diagrams showing a procedure for displaying a kanji table and a store name table in the information processing device according to the embodiment. 10 is a diagram showing a procedure for uploading a project file to a server in the information processing apparatus according to the embodiment. FIG. FIG. 4 is a diagram illustrating an operation procedure of the printer according to the embodiment. FIG. 1 is a diagram illustrating a hardware configuration of an information processing system according to an embodiment. FIG. 1 is a functional block diagram of an information processing system according to an embodiment. 10 is an example of a sequence chart when a label is printed by a printer in the information processing system according to the embodiment. 10A to 10C are diagrams showing a procedure for editing a call table in the printer according to the embodiment. FIG. 2 is a diagram showing an example of the configuration of a directory of storage in a printer according to an embodiment. 10A and 10B are diagrams illustrating an example of a display of an object property setting section when each table is selected on a project file creation screen of the information processing apparatus according to the embodiment. 10 is a flowchart showing a process when the printer according to the embodiment refers to a table. 10A and 10B are diagrams illustrating a procedure for setting up an automatic backup in a printer according to an embodiment. FIG. 2 is a diagram illustrating an example of a directory configuration of storage in a server according to an embodiment. 10 is a sequence chart showing an automatic backup process of an edited table in the information processing system according to the embodiment. 10A and 10B are diagrams illustrating a procedure for setting up a manual backup in a printer according to an embodiment. FIG. 10 is a diagram showing a procedure for restoring data in a printer according to an embodiment. FIG. 10 is a diagram illustrating another example of the configuration of a directory of storage in the server according to the embodiment. 10 is a sequence chart showing an automatic backup process of differential data of an edited table in the information processing system according to the embodiment.

The "storage device" in this disclosure may be a memory or storage built into the printer, or may be a device external to the printer (for example, an external storage device such as an HDD (Hard Disk Drive) or USB (Universal Serial Bus) storage, or a database server).
"Reference data" in this disclosure may refer to any data that is referenced when printing. Examples include data that references layout data and text that are referenced when printing, data that is referenced when retrieving character data to be printed, and data that indicates the distribution destination of layout data used when printing. Setting information that is referenced when printing can also be reference data.

(1) System Overview An information processing system 1, which is an embodiment of the information processing system of the present invention, will be described below with reference to Fig. 1. Fig. 1 is a system configuration diagram of the information processing system 1 according to this embodiment.

As shown in FIG. 1, in the information processing system 1 of this embodiment, a computer device 2 and a plurality of printers 3-A, 3-B, 3-C, 3-D, 3-E, etc. are connected to a server 5 via a network NW such as the Internet or a LAN (Local Area Network).
In this embodiment, the information processing system 1 is a system operated by a retailer that operates multiple stores, and is used to issue labels to products sold at each store. Note that, although this embodiment will be described taking as an example a case where labels are issued at a store, in reality, labels may be issued at a factory or the like.

A computer device 2 is located at the retailer's headquarters. The computer device 2 (hereinafter referred to as "PC2" as appropriate) is a computer device such as a personal computer or tablet terminal. At least one printer is located in each store. For example, printers 3-A, 3-B, 3-C, 3-D, and 3-E are located in stores A, B, C, D, and E, respectively. In the following description, when referring to matters common to multiple printers, the printer will be referred to as "printer 3."
The headquarters designs the basic layout design of the labels using PC 2. Each store issues labels to be affixed to products based on the label layout design provided by the headquarters.

A label creation application program (hereinafter referred to as the "label creation application") is installed on PC 2. This program creates a project file that includes data about the label layout design, as well as data about each item included on the label, various settings, store information, etc. The project file created by running the label creation application is distributed as a format file from PC 2 to printer 3 via server 5. In other words, the project file is uploaded as a format file from computer device 2 to server 5 in response to a specified user operation, and then downloaded from server 5 to printer 3 at a specified time.

A label issuance application program (hereinafter referred to as the "label issuance application") that prints labels based on a format file is installed on the printer 3. By executing the label issuance application, it is possible to select printing data that specifies the label layout design and data for each item included on the label, or to edit the selected printing data as needed, and print labels based on the printing data. Store employees affix the labels printed by the printer 3 to products in the store.
Project files and publishing data are described below.

(2) Flow up to Label Issuance Next, with reference to FIGS. 2 to 7, a series of flows from when a project file is created by the PC 2 to when a label is issued by the printer 3 will be described.
Fig. 2 shows an example of a project file creation screen on PC 2. Fig. 3 shows the procedure for displaying a call table definition on PC 2. Fig. 4 shows the procedure for displaying a call table on PC 2. Fig. 5 shows the procedure for displaying a kanji table and a store name table on PC 2. Fig. 6 shows the procedure for uploading a format file to a server on PC 2. Fig. 7 shows the operating procedure for printing labels on printer 3.

(2-1) Creating a Project File Figure 2 shows an example of a PC screen G1 (project file creation screen) that is displayed on the PC 2 when the label creation application is launched. On the project file creation screen, the user can design the label to be printed by the printer 3 by setting objects to be placed in the effective print area of the label.

In the label creation application, data is managed using project files. Project files are files that indicate the management units for data created by the label creation application, and are distributed to each printer 3 as a format file via the server 5.

As shown in FIG. 2, the PC screen G1 includes a group of instruction buttons 101, a group of object buttons 102, a design window 103, a project setting section 104, and an object property setting section 105.
The project setting section 104 displays the data contained in the project file in a hierarchical structure. As shown in this hierarchical structure, the project file includes a call table, layout data, a kanji table, and a store name table. Although not shown, the project file also includes table information files. The table information files are files that contain information about various settings for each table.

The call table is data for printing labels in the label issuing application of the printer 3. The call table is an example of reference data for referencing layout data and text that are referenced when printing by the printer 3.
The layout data is design data for printing labels by the printer 3 in combination with a call table, and is displayed in the design window 103 on the PC screen G1 during editing, for example.
The kanji table is a table for converting input numerical values into registered character data. Character data can be registered in the kanji table in association with a registration number. For example, by setting the kanji table to be referenced when inputting characters into a string object (described later), it is possible to specify a registration number instead of inputting character data. The kanji table is an example of reference data for calling up text when printing based on layout data.
The store name table stores information corresponding to the printer IDs (printer identification information) of printers located in stores to which the format file is to be distributed. The store name table is an example of reference data that includes the printer IDs of printers 3 that print based on the layout data.

Note that while Figure 2 shows a case where one kanji table and one store name table are set, this is not the only case. Multiple kanji tables and multiple store name tables can be set. For example, it is possible to set up Kanji Table 1, Kanji Table 2, Kanji Table 3, ..., Store Name Table 1, Store Name Table 2, Store Name Table 3, ..., etc.

The design window 103 corresponds to a label creation/editing area, and labels are designed by placing and moving objects within this creation/editing area. In other words, the design window 103 is a window for designing the layout of a label. In this embodiment, an example is shown in which a label is designed including four objects: object OBJ1 corresponding to the "product name" item, object OBJ2 corresponding to the "name" item, object OBJ3 corresponding to the "content volume" item, and object OBJ4, a date and time object corresponding to the "expiration date" item.
When button b2 ("input screen") is operated, a window (not shown) for inputting the character string or code contained in each object is displayed in place of the design window 103. When button b1 ("layout") is operated while this window is displayed, the display returns to the design window 103.

The object button group 102 is a section for performing an operation to select and move an object on the design window 103 or an operation to set a new object. The object button group 102 allows the selection of objects such as a character string object, a price object, a barcode object, a date and time object, and a graphic object. Various settings for the object can be made in the object property setting section 105.
2, various settings for the selected object OBJ1 can be made in the object property setting unit 105. For example, the item name ("Product Name" in this example) in the object property setting unit 105 sets the item to be used in the layout design in the design window 103. "Fixed" or "At Printing" can be selected as the input method. When "Fixed" is selected as the input method, it indicates that the value set in the "Data" field ("Chicken Cutlet Sandwich" in this example) is set to be printed, and when "At Printing" is selected as the input method, it indicates that the initial value set in the "Data" field can be changed in the label printing application of the printer 3.

By operating the buttons in the instruction button group 101, it is possible to read a project file from storage, save a project file to storage, or upload a project file to the server 5 as a format file.

Next, the call table, the kanji table, and the store name table will be described with reference to FIGS.
To register data to be printed on labels in the call table, the data must be defined in advance. To define the data, as shown in Figure 3, operate the "Call Table" in the project setting unit 104 (for example, by right-clicking and selecting "Define") to display the call table definition window W1. The call table definition data TL1 in window W1 shows an example in which four item names, "Product Name,""Name,""ContentAmount," and "Expiration Date," are defined. Values for fields such as "Number of Digits,""Number of Digits Check," and "Character Type Check" are entered into the records corresponding to each item name in the call table definition data TL1.

The values of each field, such as "Number of digits,""Number of digits check," and "Character type check," are provided to check the character strings corresponding to each item name entered by the user from the standpoint of label layout, consistency of the content displayed on the label, etc., but are not required.
The value of the "Number of digits" field indicates the maximum number of digits in the string corresponding to each item name. The value of the "Number of digits check" field indicates whether or not to check whether the string corresponding to the item name has been entered in the call table, or whether or not to check whether the number of digits in the string corresponding to the item name is less than or equal to the value of the "Number of digits" field. The value of the "Character type check" field indicates whether or not to check the character type (numeric or non-numeric) of the string corresponding to the item name, and specifies the character type if checking.
The user inputs data in window W1 and creates call table definition data TL1, whereby the item names to be printed on the label are registered in the call table (that is, the items are defined).

After creating the call table definition data TL1, the user registers print data in the call table. As shown in Fig. 4, by operating "Call Table" in the project setting section 104 (for example, by double-clicking or right-clicking and selecting "Open" (see Fig. 3)), the call table TL2 is displayed.
The call table TL2 has fields for the four item names defined in the call table definition data TL1 (see Figure 3), namely "item name,""name,""contentvolume," and "expiration date," as well as fields for "call number" and "layout designation."

Each record in the call table TL2 indicates the label layout for printing one label and the data (character strings) for each defined item name. Hereinafter, this data for each record will be referred to as "printing data." By inputting the character strings corresponding to each item name into the call table TL2, the user can associate the label layout with the character strings corresponding to each item name. The call table TL2 does not need to have multiple records; it can have only one record (i.e., one piece of printing data).
In the call table TL2, print data is specified by a call number. In the label printing application of the printer 3, print data is called by the call number.

In call table TL2, the value of the "Layout Designation" field indicates one or more pieces of layout data created in design window 103 (see Figure 2). In this example, if two pieces of layout data have been created, [1] Content Display Label and [2] Expiration Date Label, the value of the "Layout Designation" field indicates which of these two pieces of layout data each piece of printing data corresponds to.

For example, in the label design in the design window 103 shown on the PC screen G1 in FIG. 2, the issuing data corresponding to the record of call No.: 1 (call name: "chicken cutlet sandwich") in the call table TL2 is displayed.
In this example, the label design in the design window 103 corresponds to the value of the "Layout Designation" field of the record corresponding to call No.: 1 ([1] Content Display Label). The character string in object OBJ1 corresponding to the product name corresponds to the value of the "Product Name" field of the record of call No.: 1 in the call table TL2. The character string in object OBJ2 corresponding to the name corresponds to the value of the "Name" field of the record of call No.: 1 in the call table TL2. The character string in object OBJ3 corresponding to the content volume corresponds to the value of the "Content Volume" field of the record of call No.: 1 in the call table TL2.

The value of the "Best Before Date" field of the record corresponding to call number 1 indicates the maximum number of digits for the date in object OBJ4, which is the date and time object corresponding to the best before date. In the label design in design window 103, the date in object OBJ4 corresponding to the best before date is displayed as, for example, the base date or current date of PC2.

In this way, by registering data in call table TL2, the user of PC2 can design labels with different layouts, or labels with the same layout but with different printed content for each item. For example, in the example shown in Figure 4, the printing data corresponding to each of call numbers 1 to 3 corresponds to labels with the same layout ([1] content display label) but different printed content for each item. The printing data corresponding to call number 100 corresponds to a label with a different layout ([2] expiration date label) from call numbers 1 to 3.

As shown in FIG. 5, by operating (for example, double-clicking) "Kanji Table" in the project setting section 104, the kanji table TL3 can be displayed.
In the illustrated example, each record in the kanji table TL3 includes values in the fields "registration number" and "character data." The value in the "registration number" field is, for example, a number specified when entering characters into a character string object. The value in the "character data" field is character data entered when the corresponding registration number is specified.

As shown in FIG. 5, by operating (for example, double-clicking) the "Store Name Table" in the project setting section 104, a store name table TL4 can be displayed.
In the illustrated example, each record in the store name table TL4 includes values in the fields of "registration number,""storename,""address," and "telephone number." The registration number is a value that identifies the printer 3 to which the format file is to be delivered, and is associated with a printer ID (printer identification information). Because some stores may have multiple printers 3, there is not necessarily a one-to-one correspondence between registration numbers and store names. The example in FIG. 5 shows that two printers 3 with registration numbers 6 and 7 are located in store F. Although not illustrated in FIG. 5, it is possible to add a record with a new registration number to the store name table TL4 or delete an existing record from the store name table TL4 based on a specific user operation.
The store name table TL4 is data for identifying the printer 3 to which the format file is to be distributed, and does not necessarily need to include the "address" and "telephone number" fields for each store.

As described above, the layout data, call table, kanji table, and store name table are created in the label creation application of PC 2. Then, by operating the output button in command button group 101, a project file including the layout data, call table, kanji table, store name table, and each table information file is uploaded to server 5 as a format file.
Specifically, when the output button in the instruction button group 101 is operated, a data output window W2 is displayed as shown in FIG. 6. In the output destination selection section 204 of the window W2, the storage in the PC 2 ("Devices and Drives") or the server 5 ("Server") can be selected as the output destination. If "Server" is selected, a window W3 is displayed. In the window W3, the address (URL) corresponding to the server 5, the login ID, and the file name of the project file are entered, and the OK button is pressed to upload the format file corresponding to the project file (window W4). Note that in the window W3, password authentication may be performed for security reasons.
In the example shown in FIG. 6, a format file with the file name “sandwich” is uploaded to the server 5 .

(2-2) Issuing a Label The procedure for issuing a label in the printer 3 is as follows.
First, the label printing application on the printer 3 is started and an operation is performed to download a format file from the server 5. Next, as shown on the printer screen g1 in Figure 7, from among the downloaded format files, the user selects "sandwich" as the format file corresponding to the label they wish to print.
The printer screen g2 that is then displayed includes an input box bx1 for inputting a call number in the selected format file. The call number input here corresponds to the call number in the call table (see FIG. 4) in the format file. For example, if call number 003 is input in input box bx1, the issuing data of the record corresponding to call number 003 in the call table of FIG. 4 is called up, and the printer screen g3 is displayed.

On the printer screen g3, the values of each item of the issuance data corresponding to the call number: 003 are displayed as initial values in the issuance data display section 206. In the issuance data display section 206, the value corresponding to the expiration date is the reference date of the printer 3.
When the Confirm button is pressed on the printer screen g3, the printer screen g4 is displayed. The printer screen g4 includes a preview button b4, a confirm button b5, an input box bx2 for inputting the number of sheets to be printed, and an input box group 207.
The input box group 207 consists of input boxes corresponding to the various printing data items. If the data input method in the label creation application is set to "at printing" (see the object property setting unit 105 in FIG. 2), the user can edit the character string by selecting an input box and operating the software keyboard SK, for example.
A label is printed by pressing the Confirm button b5 on the printer screen g4. Before printing a label, a preview image of the label can be displayed by pressing the Preview button b4.

As will be described later, the user of the printer 3 can individually edit the call table, kanji table, and store name table contained in the format file downloaded by the printer 3.
In the following, the call table, kanji table, and store name table contained in the format file distributed by the PC 2 and downloaded by the printer 3 from the server 5 will be referred to as the "master call table,""master kanji table," and "master store name table," respectively, as appropriate. The master call table, master kanji table, and master store name table may be collectively referred to as the "master file."
Furthermore, the tables obtained after the user of printer 3 has edited the master call table, master kanji table, and master store name table will be referred to as the "edited call table,""edited kanji table," and "edited store name table," respectively. The edited call table, edited kanji table, and edited store name table may be collectively referred to as the "edited table" or "master edit file."

(3) Configuration of Information Processing System 1 Next, the configuration of the PC 2, printer 3, and server 5 included in the information processing system 1 will be described with reference to FIG.

(3-1) PC2
As shown in FIG. 8, the PC 2 includes a control unit 21, a storage 22, an operation input unit 23, a display unit 24, a LAN interface 25, and a USB interface 26.

The control unit 21 is mainly configured with a microprocessor and controls the entire PC 2. For example, the microprocessor included in the control unit 21 loads and executes a label creation application program recorded in the storage 22, and displays the execution results on the display unit 24.
The storage 22 is a non-volatile memory and may be, for example, an SSD (Solid State Drive) such as a flash memory. In addition to the label creation application program, the storage 22 stores project files created by executing the label creation application, printer IDs of the printers 3 installed in each store (printer IDs corresponding to the registration numbers in the store name table), etc.
The project file includes layout data, a call table, a kanji table, a store name table, and each table information file, where the call table, kanji table, and store name table are each an example of reference data.

By executing the label creation application, the control unit 21 may set whether or not the master file can be edited. Setting whether or not the master file can be edited will be described later.

The operation input unit 23 includes, for example, input devices such as a pointing device, a touch panel, etc. When the display unit 24 includes a display panel for touch panel input, the display unit 24 constitutes a part of the operation input unit 23.
The display unit 24 includes, for example, a liquid crystal display panel, and displays the results of the execution of the label creation application.
The LAN interface 25 is a communication interface for communicating with the server 5 .
The USB interface 26 is an interface for direct communication with the printer 3 .

(3-2) Printer 3
As shown in FIG. 8, the printer 3 includes a control unit 31, a storage 32 (an example of a memory unit), an operation input unit 33, a display unit , a conveying unit 35, a printing unit , a LAN interface 37, and a USB interface .

The control unit 31 is mainly configured with a microprocessor and controls the entire printer 3. The storage 32 is a non-volatile memory, for example, an SSD such as a flash memory.
For example, the microprocessor included in the control unit 31 loads and executes firmware and a label issuance application program recorded in the storage 32 .
The control unit 31 requests the server 5 to transmit a format file, receives the format file transmitted in response to the request via the LAN interface 37, and stores it in the storage 32. There are no limitations on the timing at which the control unit 31 requests the server 5 to transmit a format file, but it may be, for example, when the printer 3 is started up, at a predetermined time each day, or when a predetermined download operation is performed by the user.

The storage 32 stores firmware, a label printing application program, and the printer ID of the printer 3. This printer ID corresponds to the registration number in the store name table recorded in the PC 2.
The storage 32 stores one or more format files downloaded from the server 5 .

The control unit 31 executes firmware to convert the issuance data into bitmap data for printing (print data), and sequentially sends line data, which is data for each line of the print data, to the printing unit 36. The transport unit 35 and the printing unit 36 perform printing based on the line data that is sequentially sent out.
The transport unit 35 includes a platen roller, a motor drive circuit, and a stepping motor (not shown), and transports the continuous paper within the printer 3. For example, based on a transport request from the firmware, the motor drive circuit drives the stepping motor, which controls the rotation of the platen roller, to transport the continuous paper.
The printing unit 36 includes a thermal head and a head drive circuit (not shown). The head drive circuit selectively applies current to each heating element of the thermal head based on line data, thereby printing on the continuous paper label.

The operation input unit 33 includes a touch panel input provided on the display panel of the printer 3 and its input circuit.
The display unit 34 has a display panel, and displays the execution results of the label printing application on the display panel.
The LAN interface 37 is a communication interface for communicating with the server 5 .
The USB interface 38 is an interface for direct communication with the computer device 2 .

(3-3) Server 5
The server 5 includes a control unit 51 , a storage 52 , and a communication unit 53 .
The storage 52 is a large-capacity storage device such as an HDD, and stores the format file sent from the PC 2 in association with the login ID.
The control unit 51 is mainly configured with a microprocessor, and executes a server program to control the entire server 5. The control unit 51 controls the communication unit 53 to transmit a format file in response to a request from the printer 3, for example.
The communication unit 53 is a communication interface that communicates with the PC 2 and the printer 3 .

Further explanation will be given with reference to Fig. 9. Fig. 9 is a functional block diagram of the printer 3 and the server 5 of the information processing system 1.
Referring to Figure 9, the control unit 31 of the printer 3 executes the label issuance application and functions as a data update unit 311, a data editing unit 312, a printing control unit 313, an automatic backup processing unit 314, a manual backup processing unit 315, a backup generation setting unit 316, and a restore processing unit 317.
The control unit 51 of the server 5 executes a server program to function as a data recording unit 511 and a data deleting unit 512 .

In printer 3, the layout data and master files (i.e., master call table, master kanji table, master store name table) recorded in storage 32 are updated regularly or irregularly based on the format file downloaded from server 5. At this time, the data update unit 311 updates the layout data and master files in the first memory area of storage 32 with the layout data and master files received from computer device 2 via server 5 at the data update timing. The timing of data updates is not limited, but may be, for example, when printer 3 is started up, at a specified time each day, or when a specified download operation is performed by the user.

When a user edits a master file included in a downloaded format file, storage 32 stores the edited master edit file (i.e., at least one of the edited call table, edited kanji table, and edited store name table). At this time, the master edit file is recorded in a memory area (second memory area) different from the memory area (first memory area) in storage 32 where the original master file is stored. In other words, the data editing unit 312 edits the master file in the first memory area of storage 32 based on user input, and records the edited master edit file in the second memory area of storage 32.

In one embodiment, whether or not editing of the master file is permitted can be set by the label creation application on PC2. If editing of the master file is set to permitted, the print control unit 313 prints based on the master edit file; if editing of the master file is set to not permitted, the print control unit 313 prints based on the master file.

In one embodiment, in case the printer 3 fails, the master edit file created by the user of the printer 3 can be backed up to the server 5 and external USB storage.
The automatic backup processor 314 (an example of a first backup processor) periodically backs up the master edit file in the storage 32 to the server 5 .
The manual backup processor 315 (an example of a second backup processor) backs up the master edit file in the storage 32 to an external USB storage device when triggered by a user operation.

In one embodiment, the printer 3 can be restored based on the backed-up data.
The restore processing unit 317 restores the printer 3 based on the backup data stored in the external USB storage or the server 5 .

As will be described later, when automatically backing up data, the server 5 does not simply record the data to be backed up in the printer 3, but records any differences from the previous backup data. If the data to be backed up is a master edit file, the data recording unit 511 records the master edit file resulting from the most recent edit in the storage 52 if there are differences between the master edit file resulting from the most recent edit on the printer 3 and the master edit file resulting from the previous edit.

The backup generation setting unit 316 sets the maximum number of master edit files that can be stored in the storage 52 of the server 5 based on an operation input by the user of the printer 3 .
The data deletion unit 512 deletes master edit files previously recorded in the storage 52 based on the maximum value set by the backup generation setting unit 316. That is, master edit files that are old backup data are sequentially deleted from the storage 52.

Referring to FIG. 10, the label printing operation is as follows.
In response to a user operation, the label creation application on the PC 2 sends a format file including each table (master file) to the server 5 (step S2). The server 5 stores the format file received from the PC 2 in the storage 52 (step S4).
The server 5 transmits the format file to the printer 3 in response to a request from the printer 3 (for example, a request for data update) (step S6), and the printer 3 stores the received format file in the storage 32 (step S8).

Then, as shown in FIG. 7, the printer 3 reads the format file selected in response to user operation (step S10) and accepts the input of a call number (step S12). The printer 3 then displays the printing data called up by the input call number as shown on printer screen g3 (FIG. 7) (step S14), and is ready to print labels. Once the format file has been obtained from the server 5, the printer 3's label printing application can print labels corresponding to each call number even in an offline environment.

(4) Management of Edited Tables Next, management of edited tables in the printer 3 will be described with reference to FIGS.
As described above, the format file downloaded by the printer 3 includes a call table, a kanji table, and a store name table (i.e., a master file). This master file contains data corresponding to labels that are generally used in all stores managed by the headquarters. On the other hand, a user of the printer 3 at a store can edit the master file and save it in the storage 32 as an edited master file. This allows the store user to create and save data for printing labels to be affixed to unique products that are unique to the store.

FIG. 11 shows an example of a procedure followed by a user of the printer 3 in a store to edit a call table (master call table).
Referring to Figure 11, when the "Master Edit" item is selected on the printer screen g5 related to settings, the screen switches to printer screen g6, where a screen for editing the master file (master edit) for each format file appears. In master edit, the master call table, master kanji table, and master store name table can be edited individually. Here, for example, when the master call table is selected as the table to be edited, a printer screen g7 for editing the master call table appears.
On the printer screen g7, for example, by selecting "New Registration," it is possible to add issuance data corresponding to a new call number to the master call table. In other words, it is possible to create an edited call table in which new issuance data has been added to the master call table. In this case, as displayed on the printer screens g8 and g9, the user can create new issuance data by entering values for each item included in the issuance data.

Although not shown, when "Copy and register new" is selected on the printer screen g7, new issuance data can be created by copying the issuance data contained in the master call table and changing the values of some of the items. When "Change" is selected on the printer screen g7, some of the items of the issuance data contained in the master call table can be changed. When "Delete" is selected on the printer screen g7, at least one piece of issuance data contained in the master call table can be deleted. In either case, a new master edit file is created by editing the master file.
FIG. 11 shows the procedure for editing the master call table, but the master kanji table and the master store name table can also be edited individually in the same way.

FIG. 12 shows an example of the directory configuration in the storage 32 of the printer 3 according to this embodiment.
As mentioned above, the master edit file created as shown in Figure 11 is recorded in a memory area (second memory area) in storage 32 that is different from the memory area (first memory area) in which the original master file is stored.

As shown in FIG. 12, the storage 32 includes a FormatFiles folder, a Histories folder, a LocalTables folder, a Logs folder, and a Settings folder.
The FormatFiles folder is a folder that stores layout data, a master call table, a master kanji table, and a master store name table for each format file.
The Histories folder contains a printing history file for each format file. The printing history file contains data such as the printing history of past labels (such as when, what types of labels were printed, and how many labels were printed).
The LocalTables folder is a folder that stores the edited call table, edited kanji table, and edited store name table for each format file.
The Logs folder is a folder in which error information that occurs in the label printing application is recorded for later troubleshooting.
The Settings folder is a folder that contains setting information files.

12, the master files (master call table, master kanji table, and master store name table) and the master edit files (edited call table, edited kanji table, and edited store name table) are stored in different folders in the storage 32. In other words, the master files and the master edit files are stored in different memory areas in the storage 32.
If the master edit file is further edited, the edited file will be overwritten and saved to the master edit file already in the LocalTables folder.

When updating data, the control unit 31 of the printer 3 overwrites and updates the master file contained in the corresponding format file in the FormatFiles folder of the storage 32 with the master file contained in the format file downloaded from the server 5. When updating data in this way, the master edit file in the LocalTables folder of the storage 32 is not updated. Therefore, in the information processing system 1 of this embodiment, when updating data on the printer 3 based on a format file received from the PC 2 via the server 5, the master edit file, which is data edited on the printer 3, can be prevented from being deleted.

In one embodiment, the head office may use a label creation application on the PC 2 to set whether or not master editing is permitted on the printer 3 in the store.
Fig. 13 shows an example of the display of the object property setting unit 105 when each table is selected on the project file creation screen of the PC 2 according to this embodiment. Fig. 13 shows the display state of the object property setting unit 105 when, from left to right, a call table, a kanji table, and a store name table are selected in the project setting unit 104. As shown in Fig. 13, each table is provided with edit permission/deny buttons 211 to 213, which are buttons for "Allow master editing in Print." By operating these buttons, it is possible to set whether or not to allow master editing by the label issuance application of the printer 3.

The settings made using the edit permission buttons 211 to 213 are reflected in the edit permission flag included in each table information file. The label printing application of the printer 3 determines whether editing is permitted for the call table, kanji table, and store name table individually by referencing the edit permission flag in each table information file included in the format file received via the server 5. In other words, the label printing application obtains each table information file from the server 5, and does not permit master editing if the edit permission flag included in each obtained table information file indicates that editing is not permitted.
By allowing or disallowing editing, the headquarters can decide, on a table-by-table basis, which tables are allowed to be edited by the store and which are not.

If multiple kanji tables or multiple store name tables are provided, master editing permission can be set for each individual table. For example, if kanji table 1, kanji table 2, kanji table 3, etc. are set, master editing permission can be set individually by specifying the corresponding table number (1, 2, 3, etc.). By individually setting master editing permission, stores can flexibly set the freedom to issue their own unique labels.

14 is a flowchart showing the process for determining the table to be referenced when printing a label based on printing data in the printer 3. The flowchart in FIG. 14 is executed by the control unit 31 of the printer 3.
As shown in Figure 12, when a master file is edited on a printer 3 in a store, the master file and the edited master file coexist. In this case, the priority of the tables to be referenced when reading printing data from the corresponding format file and printing labels is defined by the flowchart in Figure 14.

In Figure 14, if any format file is selected, for example, on the printer screen g1 in Figure 7 (step S20: YES), the control unit 31 first reads the edit permission flag from each table information file included in the selected format file (step S22). As mentioned above, the edit permission flag indicates whether master editing is permitted for each table, and is set for each of the call table, kanji table, and store name table.

The processes in steps S24 to S30 are performed for each table in turn, with reference to the edit permission flag (step S32). Specifically, if the edit permission flag corresponding to the table to be processed indicates "permitted," the LocalTables folder in storage 32 is referenced first. That is, if there is an edited table in the LocalTables folder (step S26: YES), control unit 31 references the edited table in the LocalTables folder (step S28).
If the edit permission flag corresponding to the table to be processed indicates "not permitted" in step S24, or if there is no edited table in the LocalTables folder (step S26: NO), the control unit 31 refers to the table in the FormatFiles folder (i.e., the master call table, master kanji table, or master store name table) (step S30).

As shown in the flowchart in Figure 14, when a label is printed based on printing data on Printer 3, if an edited table exists in the LocalTables folder, that edited table is referenced first. Therefore, users of Printer 3 in a store can update data for labels that are generally used in all stores managed by headquarters, while also printing labels that are different from the generally used labels (labels to be affixed to products specific to that store).

As explained with reference to FIG. 13, allowing the headquarters to set whether or not to permit master editing by the printer 3 at the store has the following advantages.
For example, some retail stores may change their operations so that, at a certain point, headquarters will centrally manage all tables. In this case, even if headquarters wants all stores to issue labels based on a master file, if a master edit file exists in the store's printer 3, the master edit file will be referenced preferentially, as shown in the flowchart in Figure 14, and the master file will not be referenced. Therefore, by allowing headquarters to set, on a table-by-table basis, whether or not to allow master editing by the printer 3 at the store, it is possible to control the system so that the master file (data in the FormatFiles folder) is referenced preferentially, even if a master edit file exists.

In one embodiment, the control unit 31 deletes from the storage 32 the master edit file corresponding to the format file deleted from the printer 3 at the data update timing.
When data is updated, format files that are no longer needed at all stores managed by the headquarters may be deleted. In such cases, the printer 3 deletes one of the format files stored in the storage 32 based on instructions from the PC 2 via the server 5. At this time, the format file to be deleted and the master edit file created based on that format file are stored in different folders, so it is possible to store the format file in the storage 32 as is even after it has been deleted. However, if the master edit file remains on its own, it will be unusable and will take up space in the storage 32, so it is preferable to delete it.

As described above, in one embodiment of the information processing system 1, the printer 3 records the master file that is the subject of data updates between the printer 3 and the server 5, and the master edit file created by the printer 3 user by editing the master file, in different memory areas of the storage 32. This allows the store to maintain the ability to update the master file between the printer 3 and headquarters, while preventing the master edit file used for the store's unique products from being deleted from the printer 3 when data is updated.

(5) Backing Up and Restoring Master Edit File Next, the backing up and restoring of data in the printer 3 will be described with reference to FIGS.
If the printer 3 breaks down, for example, the master edit files (edited call table, edited kanji table, and edited store name table) created by store users will be lost. Therefore, the system is configured to ensure that the master edit files can be backed up. Backup methods include automatic backup and manual backup. However, as will be described later, the data that can be backed up is not limited to the master edit files.
In the following description, data recorded on the backup destination server 5 or USB storage by the backup process performed by the printer 3 may be referred to as "backup data."

Automatic backup involves backing up data by sending and recording data to the server 5 periodically (for example, at a specified time each day) or when the printer 3 is started. Because automatic backup is performed without the user's knowledge, it is possible to prevent the user from forgetting to manually back up data, which could cause problems with printer 3 recovery.

Manual backup is a process in which the user performs an operation to record data in the printer 3 in a USB storage, thereby backing up the data.
Manual backup is provided for the following reasons: First, it is more convenient for the user of the printer 3 to be able to perform manual backups when using the printer 3 without connecting to the server 5. Second, when a serviceman from the manufacturer or distributor of the printer 3 comes to investigate the cause of a malfunction or other problem with the printer 3 at a store, he or she can back up the data on the printer 3 to USB storage and take it home, thereby enabling a quick resolution.
Another advantage of performing manual backup is that it makes it easier to use USB storage to perform kitting work for multiple printers 3. For example, by repeatedly performing tasks such as backing up data to USB storage on the first printer 3 and then using the data backed up on the USB storage to restore data on the second printer 3, the burden of kitting work for setting up multiple printers 3 can be reduced.

As described below, manual backups back up all data that is targeted for backup, while automatic backups only back up data that is targeted for backup if there is a difference between the data targeted for backup and the previous backup data.

The data backup destination is not limited to USB storage or the server 5, but may also be the internal storage 32 of the printer 3. By using the storage 32 as the data backup destination, it becomes possible to easily restore data if the user makes a mistake in changing settings or changes the master file.

(5-1) Automatic Backup Next, automatic backup will be further explained with reference to FIGS.
FIG. 15 shows the procedure for setting up automatic backup on the printer 3.
15, when the "External Storage Linkage Management" item is selected on the printer screen g10 related to settings, the screen switches to printer screen g11. Next, when the "Linked Data" item is selected, printer screen g12 is displayed, allowing the user to set details of data download and upload between the server 5 and the printer 3. Note that printer screen g12 can be displayed when "External Storage Linkage" is enabled in "External Storage Linkage Management" on the printer screen g11.
On the printer screen g12, the "Upload" item has items for "Backup Master Edit File" and "Backup Settings Information File," and buttons are provided for enabling or disabling automatic backup of the master edit file and the settings information file. By operating these buttons to enable them, automatic backup of the master edit file and the settings information file can be performed separately. Although not shown, the timing of automatic backup (for example, a specified time each day) can be set by user operation.

Data that is automatically backed up includes, for example, format files, master edit files (edited call tables, edited kanji tables, edited store name tables), and setting information files.

FIG. 16 shows an example of the directory configuration in the storage 52 of the server 5 according to the embodiment.
As shown in FIG. 16, the storage 52 includes a FormatFiles folder, a Logs folder, a BackupFiles folder, and a Settings folder.
The FormatFiles folder is a folder that contains the format files uploaded from PC2.
The Logs folder is a folder that contains printing history files uploaded from the printer 3 .
The BackupFiles folder is a folder that contains data that has been backed up for each printer ID (for example, “0001-SX-5555”) of the printer 3 that can be connected to the server 5 .
The Settings folder is a folder that contains setting information files.

16, a folder (YYYYMMDD-hhmmss folder) indicating the time when an automatic backup was performed for a specific printer 3 is automatically generated in the BackupFiles folder. For example, if an automatic backup was performed at 21:08:38 on April 25, 2022, the automatically generated folder name will be "20220425-210838."
The YYYYMMDD-hhmmss folder contains a LocalTables folder and a Settings folder. The LocalTables folder contains data that has been backed up from master edit files for each format file. The Settings folder contains backed up setting information files.

Automatic backups are performed periodically, for example, and at this time the printer 3 uploads the master edit file stored in the LocalTables folder to the server 5. If there is a difference between the master edit file uploaded last time and the master edit file uploaded this time, the server 5 creates a folder indicating the time of the current upload (YYYYMMDD-hhmmss folder) and records the master edit file uploaded this time in the YYYYMMDD-hhmmss folder (see Figure 16).

Next, automatic backup processing in the information processing system 1 will be described with reference to FIG.
FIG. 17 is a sequence chart showing the sequence when the information processing system 1 performs automatic backup processing of an edited table.

The sequence chart in Figure 17 also includes the data update process by the printer 3. That is, at the timing of a data update, the printer 3 sends a data update request to the server 5 (step S38). In response to the data update request, the server 5 sends update data for the format file (including, for example, a master file for update) to the printer 3 (step S40), and the printer 3 performs a data update process based on the update data (step S42). In the data update process, for example, the master file stored in the storage 32 is overwritten and updated with the master file included in the update data.

At the preset automatic backup time, the printer 3 transmits the master edit file and/or the setting information file stored in the storage 32 to the server 5 (step S44). The files to be transmitted are in accordance with the settings on the printer screen g12 in FIG. 15.
The server 5 determines whether there is difference data between the data (master edit file or setting information file) at the time of the previous automatic backup (e.g., the previous day) and the data (master edit file or setting information file) received in step S44 (step S46). If there is a difference between both files or either one of the files, the server 5 creates a YYYYMMDD-hhmmss folder (see FIG. 16) based on the time the files were received in step S44, and records the data received in step S44 (master edit file and setting information file) in the created YYYYMMDD-hhmmss folder as new backup data (step S48). The setting information file received in step S44 is recorded as is in the YYYYMMDD-hhmmss folder.
In one embodiment, the server 5 erases old backup data (step S50). That is, if old backup data is stored indefinitely, it will take up space in the storage 52, so it is preferable to erase old backup data in order.

(5-2) Manual Backup Next, manual backup will be further explained with reference to FIG.
18 is a diagram showing the procedure for setting up a manual backup on the printer 3. Note that when performing the procedure shown in FIG. 18, it is assumed that a USB storage device to be used as the backup destination is connected to the printer 3.
18, when the "System Management" item is selected on the printer screen g13 related to settings, the screen switches to printer screen g14. Next, when the "Backup/Restore" item is selected, printer screen g15 is displayed. Here, when the "Backup" item is selected, a screen for performing backup is displayed as shown in printer screen g16. The printer screen g16 includes an input area 301 where the user can input comments.

Entering a comment in the input area 301 is useful when restoring the printer 3. When manual backups are performed multiple times, a comment (text) can be associated with the data backed up each time. In other words, the control unit 31 of the printer 3 accepts text input by the user when backing up a master edit file, and associates the input text with the master edit file to be backed up. This allows the user, when there is multiple backup data, to select the data to use during restore based on the content of the comment. For example, entering "Data after XX setting" as a comment makes it easier to select data during restore.

In the case of manual backup, as in the case of automatic backup, a YYYYMMDD-hhmmss folder is generated in the backup destination USB storage, and backup data is recorded in the YYYYMMDD-hhmmss folder. At that time, the generated YYYYMMDD-hhmmss folder is associated with the text entered in the input area 301.
Manual backup is not limited to master edit files and setting information files, but covers all folders.

(5-3) Restoration Next, the procedure for restoring (recovering) the printer 3 based on data backed up by automatic backup or manual backup will be described with reference to Fig. 19. Fig. 19 shows the procedure for restoring data in the printer 3. Note that when the backup data is stored in USB storage, it is assumed that the USB storage is connected to the printer 3.

Referring to Figure 19, when the "Restore" item is selected on the printer screen g15 related to settings, the screen switches to printer screen g17. The printer screen g17 is configured so that the user can operate a selection button 302 for selecting the printer 3 to be restored and a selection button 303 for selecting backup data. Note that, to ensure the security of manual backups, it is preferable that the printer screen g15 (settings screen) be displayed only after successful authentication using the user's ID and password.

The selection button 303 allows the user to select the name of the YYYYMMDD-hhmmss folder on the server 5, which is the automatic backup destination, or the name of the YYYYMMDD-hhmmss folder on the USB storage, which is the manual backup destination, and text indicating a comment.
After selecting the printer 3 and backup data to be restored, pressing the OK button displays the printer screen g18 as a restore confirmation screen. The select button 303 displays the name of the selected YYYYMMDD-hhmmss folder along with associated text (e.g., "Backup"), making it easy for the user to select the desired backup data when multiple backup data exist.
The printer screen g18 has a group of check boxes 304. The group of check boxes 304 allows the user to select a folder (at least one of the FormatFiles folder, LocalTables folder, and Settings folder) to be used during restore from among the YYYYMMDD-hhmmss folders. Operating the OK button on the printer screen g18 executes the restore.

In addition, the printer screen g15 for settings in FIG. 19 has an item for "Backup Generation Setting," and by selecting this item, the generation of backup data to be saved on the server 5 can be set. For example, any value from 1 to 9 can be selected as the generation setting. That is, the control unit 31 of the printer 3 sets the maximum number of backup data items to be stored in the storage 52 of the server 5 based on the user's input. This maximum value is notified to the server 5, for example, when an automatic backup is executed.
For example, if "3" is selected as the generation setting, this means that three backup data generations will be saved. In step S50 of Fig. 17, the server 5 determines the backup data to be deleted based on the value of the backup generation setting acquired from the printer 3. In other words, the control unit 51 of the server 5 functions as a data deletion unit that deletes backup data previously recorded in the storage 52 based on the maximum value set by the printer 3.
The backup generation setting can be performed for both automatic backups and manual backups. By setting the backup generation, backup data that is too old to be needed at the time of restoration is not stored in the backup destination, which prevents pressure on the capacity of the storage 52 or USB storage.

As described above, in one embodiment of the information processing system 1, the printer 3 automatically backs up data to the server 5 on a regular basis, and can also manually back up data to USB storage in response to a user's own operation as needed, ensuring that data created on the printer, such as master edit files, can be backed up reliably. With automatic backups, data is only saved to the server 5 when changes are made through editing on the printer 3, so the capacity of the server 5 is not strained. With manual backups, users of the printer 3 who cannot access the server 5 can back up data by connecting USB storage directly to the printer 3, and this is also convenient for service personnel to download data from the printer 3 when diagnosing a malfunction of the printer 3.

In automatic backups, the master edit file may be backed up as differential data. That is, automatic backups are performed, for example, periodically, and at these times the printer 3 uploads the master edit file stored in the LocalTables folder to the server 5. The server 5 records data (differential data) indicating the difference between the master edit file uploaded last time and the master edit file uploaded this time. At this time, the server 5 creates a folder (YYYYMMDD-hhmmss folder) indicating the time of the current upload, and records the differential data in the YYYYMMDD-hhmmss folder.
Figure 20 shows an example of the directory configuration in the storage 52 of the server 5 according to one embodiment. What differs from Figure 16 is that differential data is stored in the storage 52 as backup data. In Figure 20, the difference between the current edited call table and the previous edited call table is referred to as the "differential call table," the difference between the current edited kanji table and the previous edited kanji table is referred to as the "differential kanji table," and the difference between the current edited store name table and the previous edited store name table is referred to as the "differential store name table."
Since the master file is already known to the server 5, the latest master edit file can be reproduced at the time of restoration, which will be described later, based on the master file and one or more pieces of differential data that are automatically backed up each time.

Fig. 21 is a sequence chart showing the automatic backup process when backing up differential data. In Fig. 21, steps S38 to S44 are the same as those in the sequence chart of Fig. 17, so a duplicated explanation will be omitted.
When the server 5 receives the master edit file from the printer 3, it extracts the difference data between the latest file already backed up in the storage 52 and the master edit file received in step S44 (step S52). The server 5 creates a YYYYMMDD-hhmmss folder (see FIG. 20) based on the time the file was received in step S44, and records the difference data in the created YYYYMMDD-hhmmss folder (step S54). The setting information file received in step S44 is recorded as is in the YYYYMMDD-hhmmss folder.
In one embodiment, the server 5 erases the old differential data (step S56). That is, if old differential data is stored indefinitely, it will take up space in the storage 52, so it is preferable to erase the old differential data in order.

The above provides a detailed description of one embodiment of the information processing system, printer, and program of the present invention, but the present invention is not limited to the above embodiment. Furthermore, the above embodiment can be subject to various improvements and modifications without departing from the spirit and scope of the present invention.

REFERENCE SIGNS LIST 1... Information processing system 2... Computer device 21... Control unit 22... Storage 23... Operation input unit 24... Display unit 25... LAN interface 26... USB interface 3... Printer 31... Control unit 311... Data update unit 312... Data editing unit 313... Printing control unit 314... Automatic backup processing unit 315... Manual backup processing unit 316... Backup generation setting unit 317... Restore processing unit 32... Storage 33... Operation input unit 34... Display unit 35... Transport unit 36... Printing unit 37... LAN interface 38... USB interface 5... Server 51... Control unit 511... Data recording unit 512... Data deletion unit 52... Storage 53... Communication unit 101... Instruction button group 102... Placement setting button group 103... Design window 104... Project setting unit 105... Object property setting unit 204...Output destination selection section 206...Issuance data display section 207...Input box group 211-213...Edit permission/denial button 301...Input area 302, 303...Selection button 304...Check box group OBJ1-OBJ4...Object SK...Software keyboard TL1...Call table definition data TL2...Call table TL3...Kanji table TL4...Store name table

Claims (10)

An information processing system including an information processing device and a printer capable of communicating with the information processing device,
The information processing device includes:
a storage unit for storing layout data indicating a layout when printing is performed by the printer, and reference data associated with the layout data and referenced when printing is performed;
The printer
a storage unit having a first storage area and a second storage area;
a data updating unit that updates the layout data and reference data in the first storage area with the layout data and reference data received from the information processing device at a predetermined data update timing;
a data editing unit that edits the reference data in the first storage area based on a user's operation input and records edited data, which is the edited reference data, in the second storage area,
Information processing system. the information processing device includes a setting unit that sets whether the reference data is editable;
the data editing unit acquires setting information indicating whether the reference data is editable from the information processing device, and if the acquired setting information indicates that the reference data is not editable, does not permit editing of the reference data.
2. An information processing system according to claim 1. a storage unit of the information processing device stores a plurality of the reference data;
a first storage area of the storage unit of the printer stores a plurality of the reference data;
the setting unit individually sets whether or not each of the plurality of reference data is editable,
3. An information processing system according to claim 2. The printer
When the setting unit has set that the reference data can be edited, printing is performed based on the edited data in the second storage area;
a print control unit that performs printing based on the reference data in the first storage area when the setting unit has set that editing of the reference data is not allowed;
4. An information processing system according to claim 2 or 3. the data updating unit deletes, from the second storage area, edited data corresponding to the layout data deleted at the data update timing;
5. An information processing system according to claim 1. The reference data is data for referencing a print layout and text that are referenced when printing by the printer.
6. An information processing system according to claim 1. The reference data is data for calling up text when printing based on the layout data.
6. An information processing system according to claim 1. The reference data is data including identification information of a printer that performs printing based on the layout data.
6. An information processing system according to claim 1. A printer capable of communicating with an information processing device,
a storage unit having a first storage area and a second storage area;
a data update unit that receives, from the information processing device at a predetermined data update timing, layout data indicating a layout when printing and reference data that is associated with the layout data and is referenced when printing, and updates the layout data and reference data in the first storage area using the received layout data and reference data;
a data editing unit that edits the reference data in the first storage area based on a user's operation input and records edited data, which is the edited reference data, in the second storage area;
A printer equipped with A program executed in a printer capable of communicating with an information processing device,
the printer includes a storage unit having a first storage area and a second storage area;
The program causes a computer to:
a data update unit that receives, from the information processing device at a predetermined data update timing, layout data indicating a layout when printing and reference data that is associated with the layout data and is referenced when printing, and updates the layout data and reference data in the first storage area using the received layout data and reference data; and
a data editing unit that edits the reference data in the first storage area based on a user's operation input and records edited data, which is the edited reference data, in the second storage area;
A program to function as a