JPH04260263A - Document processor - Google Patents

Abstract

PURPOSE:To simplify the operation by inserting a data of a prescribed field of a selected record to a commanded position of a document so as to generate a transmission document, reading an opposite identification number and automatically dialing the number. CONSTITUTION:A generating section 28 reads a data from a document data memory 26 by a transmission document generation command from a control section 20 to generate the transmission document. When a data read from the document data memory 26 is a mail merge command especially, the generating section 28 reads a field data commanded by the command from a mail list data memory 27 and inserts the data to a position commanded by the command in the transmission document to generate the transmission document. Then a telephone number (FAX number) used for dialing is read from a data group in a same record and sent.

Description

[Detailed description of the invention]

0001

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a document processing device capable of creating, editing, and transmitting various documents.

0002

2. Description of the Related Art Conventionally, when it is desired to send a document created using a document processing device to a remote location, it has generally been done to print out the created document and then send the image as an image using a facsimile device. There is.

[0003] Recently, however, with the decline in the cost of modems and the like, documents with a communication function that allows documents created with document processing devices to be sent directly to facsimile machines at remote locations via telephone lines without having to be printed have become available. Processing devices are emerging.

[0004] Such document processing devices convert a desired document into a facsimile image and send it to the recipient's telephone number (Facsimile image).
AX number) or by selecting the recipient from a list of recipients registered in an electronic telephone directory or the like to make a dial call and send a message.

[0005]

[Problem to be Solved by the Invention] However, in the above-mentioned conventional device, in order to send a common document to multiple destinations, for example, it is necessary to change only the address and address in the transmitted document for each destination. In this case, each time a part of the document must be changed/edited before being sent, there is a problem in that the operation is complicated.

[0006] In addition, in such a case, it is not only necessary to change/edit the document for each destination, but also to repeatedly specify the telephone number (FAX number) of each destination, which makes the operation even more complicated. Since it is complicated, it is easy to cause erroneous operations, and in the worst case, a problem arises in which another document is sent to the desired recipient by mistake.

SUMMARY OF THE INVENTION An object of the present invention is to provide a document processing device that can easily and reliably send a created or edited document with proper address information and the like.

[0008]

[Means for Solving the Problems] The present invention provides a document processing device that creates and edits various types of documents. a first storage means for storing a document; a second storage means for storing a data group in a record format made up of one or more fields; and at the time of transmission, selecting an arbitrary record stored in the second storage means. a selection means for detecting a merge instruction command in a document stored in the first storage means; and a detection means for inserting data in a predetermined field of the selected record based on the merge instruction command. The present invention is characterized by comprising a transmission document generating means for generating a transmission document, and a transmission control means for reading a partner station identification number from a predetermined field in the record and automatically dialing and transmitting the transmission. Note that, in the present invention, the above-mentioned documents include not only those mainly composed of ordinary sentences, but also those mainly composed of line drawings, multi-gradation images, and the like.

[0009] With the above configuration, if you want to change part of the document to be sent depending on the recipient, enter only the merge instructions in the changed parts such as the address and address when creating the document. . When sending the document, the recipient is specified by selecting a record such as mail list data, the variable part is created by inserting the data group in the specified record, and the telephone number (FAX) used for dialing is created by inserting the data group in the specified record.
number) is read from the data group in the same record and transmitted.

0010

[Embodiment] FIG. 1 is a block diagram showing the configuration of a document processing device with a communication function in an embodiment of the present invention, and FIG.
FIG. 2 is a perspective view showing the appearance of the device.

The keyboard 1 has various input key groups,
This is used to input documents, etc.

The display unit 2 displays documents input from the keyboard 1, and in this embodiment, it is a liquid crystal display (LCD).
CD) is used.

The printer 3 prints documents on recording paper, and in this embodiment an inkjet printer is used.

[0014] Flexible disk drive (hereinafter referred to as F
4 (referred to as DD) stores data such as input and created documents and mail list data.

The facsimile communication section 5 includes a modem, an NCU
etc., and transmits image data to the other party's facsimile machine.

The ROM 11 stores various programs for the operation of the CPU 10, and the RAM 12 is used as a work area for the CPU 10, and is also used to store mail list data, document data, etc., which will be described later. .

[0017] Each of the above units is connected to the CPU 10 via a CPU bus 13 or the like, and by a reset operation after the device is powered on, the CPU 10 reads out the microprogram stored in the ROM 11 via the CPU bus 13 and executes it. If necessary, it can display input characters/documents on the display 2, control the printer 3 to print desired characters/documents, etc.
The entire apparatus is controlled by reading documents and mail list data created and edited in advance from the DD 4 into the RAM 12, and storing changed and edited documents and the like in the FDD 4.

FIG. 3 is a block diagram showing the configuration of the control system in this embodiment.

The input unit 21 manages and controls the operating state of the keyboard 1 and the like, and operates so that the control unit 20 can acquire input characters and the like.

The display section 22 displays characters input from the input section 21 on the display 2 described above, and controls the display based on information from the control section 20.

The printing section 23 controls the operation of the printer 3 described above to print documents, etc., and operates in response to requests from the control section 20.

The control section 20 includes the input section 21 and the display section 2.
2. Controls the printing unit 23, FDD 4, etc. to input, edit, print, output, store and fax desired documents, mail list data, etc.

The converting unit 24 converts a desired document generated by a generating unit 28, which will be described later, into facsimile image data. The data is converted and encoded (for example, MH encoded) in order to be sent to the facsimile G3 line.

The communication unit 25 performs communication control according to the facsimile transmission procedure in order to transmit the encoded image data generated by the conversion unit 24 from the facsimile communication unit 5 to a desired facsimile device. Part 20
Transmission control is performed by instructing the other party's station identification number (FAX number or telephone number).

The memory 26 is a document data memory for reading and storing documents inputted from the input unit 21 or stored in the FDD 4 and used for editing work, etc., and is read and written by the control unit 20. At the same time, data required by the generation unit 28 can be read out.

The memory 27 is a mail list data memory that stores and edits mail list data by reading characters/symbols etc. input from the input section 21 or data stored in the FDD 4, and stores and edits mail list data. 20 performs reading and writing, and also allows the generation unit 28 to read data required.

Each of these memories 26 and 27 is the RAM
12 in a predetermined area.

The generation unit 28 reads data from the document data memory 26 in response to a transmission document generation instruction from the control unit 20 and generates a transmission document. In particular, when the data read from the document data memory 26 is a mail merge command, this generation unit 28 reads field data specified by the command from the mail list data memory 27, and uses the field data specified by the command in the sending document to create a mail merge command. A process is performed to insert the document into the specified position and generate a transmission document.

Next, FIG. 4 is a schematic diagram showing the structure of mail list data.

[0030] The mail list data in this embodiment is as follows:
It is made up of multiple records, and each record is made up of multiple fields.

[0031] Each field has predetermined items to be input. For example, the first field is gender,
The second field is the first name, the third field is the middle name, the fourth field is the last name, and the eleventh field is the FAX number, and so on.

[0032] Each record having such a structure corresponds to each transmission destination.

Next, the operation when transmitting a document in the above configuration will be explained.

First, prior to transmission, the operator inputs a desired document from the keyboard 1 or instructs to call up a previously created document from the FDD 4.
Create document data to be sent. The created document data is then stored in the TX area of the RAM 12 (the memory 2
6).

At this time, a mail merge command for inserting desired mail list data into the text is input.

FIG. 5 is a schematic diagram showing a specific example of document data.

In FIG. 5, each mail merge command [
M1] to [M10] indicate the insertion position of the mail list data, and the number following M indicates the field number to be inserted in the record. This mail merge command can be input by a predetermined operation from the keyboard 1.

Then, in order to select a destination, the operator instructs a record of mail list data corresponding to the destination. Here, a case will be described in which the first record described in FIG. 4 is selected and the document data shown in FIG. 5 is transmitted.

FIG. 6 is a flowchart showing the document sending operation in the above configuration.

The transmission operation shown in FIG. 6 is started by the record selection instruction.

First, the selected record is read from the RAM 12 or the FDD 4 and stored in the ML area of the RAM 12 (memory 27) (S1).

[0042] Then, the document data stored in the TX area is read out, and it is determined whether or not the data is data designated to be merged from the mail list data (S2).
, if it is not merge designation data, it is stored in the row buffer area provided in the RAM 12 (S3).

If the data is merge designated data in S2, the data string corresponding to the designated field number is read from the ML area and stored in the row buffer (S4).

Then, it is determined whether the data in the row buffer generated in S3 and S4 has reached a predetermined amount of rows (S5).

For example, in the case of a one-line buffer, the data stored in the line buffer is a line feed code, or the total width of character data, etc. in the line buffer has reached a preset transmission record width. When detected, it is determined that the line has ended.

Next, if it is determined in S5 that the line has not ended, the above-mentioned S2 to S4 are repeatedly executed.

[0047] When the end of a line is detected, the document data in the line buffer can be sent to the facsimile machine.
In this embodiment, the ROM is
The font data is read from the character generator (CG) in 11, developed in RAM 12, converted to the dot density of a facsimile image, generated a compressed code (MH code, etc.), and stored in RAM 12 or FDD 4 (S6 ).

[0048] When the data in the line buffer has been converted into transmission image data in this way, it is determined whether all the documents in the TX area have been converted into transmission images (S7);
If it is not completed, the above-mentioned S2 to S7 are repeatedly executed.

When the process is completed, the 11th field, which is the identification number data of the partner station, is read from the ML area (S8).

In this embodiment, since the first record is selected, the partner station identification number data is "538-2917".
”.

[0051] Then, this data is transmitted to the facsimile communication section 5. In accordance with the instruction, the facsimile communication unit 5 makes a dial call via the NCU and transmits the transmission image data generated in the above-mentioned S6 via a predetermined transmission protocol (S9).

As described above, by performing the operations S1 to S9, it is possible to send a document (image) as shown in FIG. 7 to the facsimile machine of the other party of the first record shown in FIG. .

As described above, according to this embodiment, even when changing the address, address, etc. in a document to be sent depending on the recipient, there is no need to change or edit the underlying document. , the desired document can be sent to the desired party.

[0054] In the explanation of this embodiment, the case where the first record is selected has been described, but when the second record or other records are selected, the desired address,
Of course, a document incorporating a destination can be sent to a desired recipient.

Furthermore, the image generation of the transmission document in S6 is not limited to the method described in the above embodiment, and it goes without saying that any method may be used as long as desired document characters, etc. can be converted into an image.

Next, FIG. 8 is a flowchart illustrating the operation of broadcasting to a plurality of destinations as a second embodiment.

[0057] In this second embodiment, the operator arbitrarily specifies a field number and a character string to select and transmit records that have a corresponding character string in the corresponding field. For example, a case where the fifth field and the character string "President" are selected will be explained.

The hardware configuration in this second embodiment is the same as that in the first embodiment described above. Also,
The program shown in FIG. 8 is stored in the ROM 11,
It is read and executed as necessary. On the other hand, the configurations of the mail list data and document data are the same as in the first embodiment, but the RAM 12 has an area for storing field numbers for selecting records and character string data as keywords. The difference is that it has been established.

FIG. 9 is a flowchart showing the operation of setting field numbers and keywords for such record selection.

First, prior to transmission, the operator stores document data obtained by inputting from the keyboard 1 or calling from the FDD 4 in the TX area of the RAM 12 (S50). Note that this operation is the same as in the first embodiment.

[0061] Then, input the field number to search for the keyword to select the transmission destination, store the field number in the RAM 12 (S51), input the character string data to be used as the keyword, and input the character string data to use as the keyword. The column is stored in the RAM 12 (S52). In this way, the fifth field and the character string "President" described above are set.

After the above settings are completed, the transmission operation shown in FIG. 8 is executed by a predetermined start operation.

[0063] At the time of this transmission, first in S20, RAM1
2 or read one record from the mail list data in FDD 4 and store it in the ML area of RAM 12, and in order to determine whether the record corresponds to the above specification, the data in the 5th field is the character string "Presiden".
t'' (S21).

[0064] If the record is not a corresponding record, the process skips to S30, and it is determined whether or not the next record exists in the mail list data.
Returns to 0, and if it does not exist, the transmission process ends.

[0065] If the record is found to be a corresponding record in S21, processing is performed on this record as a transmission target in S22 and thereafter. For example, as shown in FIG. 4, since the fifth field of the first record is "President," the first record is the target of transmission.

[0066] Hereinafter, S22 to S27 are processes for creating a transmission document to be sent to a designated destination.
The document data stored in the TX area of RAM 12 is read out, and it is determined whether the data is merge specification data from mail list data (S22). If it is not merge specification data, the line provided in RAM 12 is read out. Store it in the buffer area (S23), and if it is merge specified data, ML the data string according to the specified field number.
Read from the area and store in the row buffer (S24
).

[0067] Then, it is determined whether the line buffer generated in S23 and S24 has reached a predetermined number of lines, and the end of the line is monitored (S25). Note that this determination method is the same as in the above embodiment.

[0068] If the line does not end, the above S22
- S25 is repeated, and if the line ends, the document data in the line buffer can be sent to the other party's facsimile machine.
Font data is read from the CG area of the ROM 11 according to the character data in the line buffer, expanded to the RAM 12, converted to the dot density of a facsimile image, generated a compressed code, and stored in the RAM 12 or FDD 4 ( S26).

[0069] When the data in the line buffer has been converted into transmission image data, it is determined whether all the documents in the TX area have been converted into transmission images (S27), and if the conversion is not completed, the steps from S22 to S27 is repeatedly executed, and when the conversion of all documents is completed, a data string is read from the 11th field as partner station identification number data in the ML area of the RAM 12 (S28).

That is, in this embodiment, since the first record is selected at this time, the data to be read is "53".
8-2917". Then, when the data is transmitted to the facsimile communication section 5, the facsimile communication section 5
According to the instruction, a dial call is made via the NCU, and the transmission image data generated in the above S26 is transmitted via a predetermined transmission protocol (S29).

[0071] When the transmission is completed, it is determined whether the transmission process is complete (S30). If there are any remaining records in the mail list data, the process returns to S20 and reads the following records.

By repeating this operation, the fifth fields of the second and third records become the character string "Pre".
These records are not subject to transmission, and then the process returns to S20 to read the fourth record.The fifth field of this fourth record is the character string “President” (S21).
), and in the same manner as the first record described above, transmit image data is generated while inserting field data into the document data in S22 to S27, and in S28, the data in the 11th field of the fourth record " 234-56
97'' and transmits it to the facsimile communication section 5. The facsimile communication unit 5 makes a dial call via the NCU according to the instruction, and transmits the transmission image data via a predetermined protocol (S29).

As described above, in this second embodiment, if the record read in S20 is the target of transmission,
While inserting field data in the record as necessary, generate the image data to be sent, dial the desired recipient, and repeat the automatic sending process until the mail list data is completed. finish.

Next, FIG. 10 is a flowchart showing the operation of a third embodiment in which transmission error processing is added to the second embodiment.

In the second embodiment described above, the dialing in S28 calls the other party's facsimile machine in order to send a document to the desired party, but if the other party is receiving or transmitting, the line is disconnected. Busy and unable to connect.

Furthermore, even if the line is connected and transmission is started in S29 described above, the transmission may not be completed due to the condition of the line or the destination machine running out of recording paper.

[0077] Therefore, a transmission operation including error processing when a transmission error occurs will be explained below.

The hardware configuration is the same as that of the previous embodiment, and the program shown in FIG.
It is stored in the file and read out and executed as needed. Furthermore, although the structure of the mail list data and document data is the same as in the above embodiment, an area (hereinafter referred to as EL area) is provided on the RAM 12 to store the record number at the time of detection of a transmission error. This is a difference.

First, prior to transmission, the operator stores document data obtained by inputting from the keyboard 1 or calling from the FDD 4 in the TX area of the RAM 12.

[0080] Then, in order to select a record corresponding to the desired recipient from among the mail list data, after setting the field number and character string data, an instruction is given to start transmission. The above processing is executed according to the procedure shown in FIG. 9 above.

In other words, in this embodiment as well, by the operator arbitrarily specifying the field number and character string,
The record having the corresponding character string in the corresponding field is selected and transmitted. For example, a case will be explained in which the fifth field and the character string "Mgr" are selected and instructed.

[0082] At the time of transmission, first, the RAM 12 or F
One record is read from the mail list data in the DD4 and stored in the ML area of the RAM 12 (S30a). Then, it is determined whether the data in the fifth field is the character string "Mgr" (S31).

For example, the first record is not applicable, so S
After proceeding to step 42, the process returns to step S30a again and the second record is read.

The fifth field of this second record is “M
gr", it is determined that this is the applicable record (S3
1), S32 to S37, S22 to S37 of the second embodiment described above
Similarly to S27, a transmission document to be sent to the specified destination is generated.

First, the document data stored in the TX area is read out (S32), and if it is not merge specified data, the data is stored in the line buffer area provided in the RAM 12 (S33), and if it is not merge specified data, it is If there is, a data string is read from the ML area according to the specified field number and stored in the row buffer (S34
).

Then, it is determined whether the line buffer has reached a predetermined number of lines, and the end of the line is monitored (S35). In addition,
This determination method is the same as in the above embodiment.

Next, if the line does not end, S32 to S
Repeat step 35. Also, when the end of a line is detected,
The document data generated in the line buffer is converted into transmission image data to be transmitted to the facsimile machine (S36).
.

For example, font data is read from the CG area of the ROM 11 according to the character data in the line buffer, expanded to the RAM 12, converted to the dot density of a facsimile image, generated a compressed code, and stored in the RAM 12 or FDD 4. do.

[0089] When the data in the line buffer has been converted into transmission image data, it is determined whether all the documents in the TX area have been converted into transmission images (S37), and if not, the above-mentioned process is performed. Repeat steps S32 to S37,
When the conversion of all documents is completed, the data string of the 11th field in the ML area is read out as the partner station identification number data, and the data is transmitted to the facsimile communication section 5.
A dial call is made via the CU (S38). For example, the second
If a record is selected, "179-0208"
to make a dial call.

[0090] Then, it is determined whether the line is connected by this dialing (S39), and if the line is connected, transmission of the transmission image data is started (S40).
. Thereafter, if there is no transmission error (S41), the process returns to S30a to process the third record (S42).

[0091] Also, when line tangent cannot be established in S39,
Or, if a transmission error is detected in S41, the record number that could not be transmitted is treated as an unsent record number.
The data is stored in the EL area of the AM 12 (S43), and the transmitted image data is erased from the RAM 12 or FDD 4 (S44) so that memory etc. can be used at a high rate. If there is a next record (S42), Returning to S30a above, the processes of S32 to S44 are executed as necessary.

[0092] When the record in the mail list data is completed (S42), the EL area is referred to, and due to the transmission failure in S39 and S41, S43
to determine whether the unsent record number has been memorized (S
45) If there is an unsent record, read that record and store it in the ML area (
S46), delete this record number from the EL area and generate transmission image data again (S32 to S37);
S32 to S39 are repeatedly executed until the transmission is completed in S40. Then, when all transmissions are completed, the transmission process is ended.

As explained above, even if transmission is not possible due to a busy line or poor line condition, the record number can be memorized and the transmission can be attempted again later to achieve the desired result. You can accurately send the desired document to the other party.

FIG. 11 is a flowchart showing the setting operation before transmission in the fourth embodiment of the present invention.

The above embodiments have been described on the assumption that the partner station identification number data of each record in the mail list data is stored in the 11th field.

However, the meaning and purpose of each field in the mail list data may differ depending on the operator who uses this device.

For example, if it is desired to provide a field for storing a telephone number in each record of the mail list data shown in FIG. 4, the telephone number can be set in the 11th field and the facsimile telephone can be set in the 12th field.

Therefore, in the fourth embodiment, the operator can arbitrarily specify the reference field of the facsimile number (destination station identification number) to be dialed at the time of transmission.

Note that the hardware configuration is the same as that of the previous embodiment, and the program shown in FIG.
It is stored in the file and can be read and executed as needed. Furthermore, the structures of the mail list data and document data are the same as those in the second and third embodiments described above, and
They are common in that they store field numbers and keywords (character string data) for selecting records on AM12, but they differ in that they also have an area to store field numbers to be referenced when dialing. ing.

First, prior to transmission, the operator stores document data obtained by inputting from the keyboard 1 or by calling from the FDD 4 in the TX area of the RAM 12 (S60).

[0101] Then, a field number for searching for a keyword for selecting a recipient is input, and the field number is stored in the RAM 12 (S61).

Next, the character string data to be used as the keyword is input, and the character string is stored in the RAM 12 (S6
2).

Note that the above processing in S60 to S62 is common to the second and third embodiments (FIG. 9).

[0104] Then, at the time of transmission, the field number to refer to the facsimile number (destination station identification number) for dialing is input, and the number is stored in the RAM 12 (S63). Then, the above-described transmission process is performed (S64).

When this transmission operation is applied to the second embodiment (FIG. 8), the corresponding record determination process in S21 above determines whether the character string data specified in S62 exists in the field specified in S61. In the dialing process in S28, the field number designated in S63 is referred to and the data in that field is used as the partner station identification number to dial.

[0106] When applied to the third embodiment, the corresponding record determination process in S31 above determines whether or not the character string data specified in S62 is present in the field specified in S61. In the dialing process of S38, the field number specified in S63 is referred to and the data in that field is used as the partner station identification number to dial.

[0107] If there is no specification in S63 described above, the 11th field used in the second and third embodiments, for example, is selected as the default value.

[0108] As explained above, the facsimile number (
By making it possible to arbitrarily specify the reference field number (of the partner station identification number), for example, even if the fields in the mail list data have different meanings, this can be effectively processed.

Further, such designation of reference field numbers may be applied to the first embodiment described above.

[0110] If the field number specified in S63 is stored for each mail list data as control information of the mail list data, the S
63 is no longer necessary. In that case, the field number may be input in S63 only if the field number of the facsimile number is not stored in the mail list data.

[0111] Furthermore, in the second to fourth embodiments described above, when the destination to which the message should be sent is selected by selecting a record in the mail list data, the operator can specify the destination in any field specified by the operator. Although the selection is made on the condition that there is a character string, for example, it may be possible to directly specify and select a plurality of record numbers.

[0112] Furthermore, a plurality of function keys are provided that allow field numbers and character strings for record selection to be registered in advance, and by operating these keys, a desired combination of field number and character string can be specified with a single touch. Accordingly, the transmission may be performed by selecting a record.

[0113]

[Effects of the Invention] According to the present invention, even when a part of a document is changed and sent by the recipient, the desired document can be sent to the desired recipient without changing/editing the document each time. can be transmitted, which has the effect of simplifying the operation for transmission.

[0114] Furthermore, even when such transmission is performed to a plurality of recipients, the desired document can be accurately and easily sent to the desired recipients, and erroneous transmission due to erroneous operation can be prevented.

[Brief explanation of the drawing]

FIG. 1 is a block diagram showing the configuration of a document processing device with a communication function in an embodiment of the present invention.

FIG. 2 is a perspective view showing the appearance of the device of the same embodiment.

FIG. 3 is a block diagram showing the configuration of a control system in the same embodiment.

FIG. 4 is a schematic diagram showing the structure of mail list data in the same embodiment.

FIG. 5 is a schematic diagram showing a specific example of document data in the same embodiment.

FIG. 6 is a flowchart showing a document sending operation in the same embodiment.

FIG. 7 is a schematic diagram showing a specific example of a transmission document in the same embodiment.

FIG. 8 is a flowchart illustrating a broadcast transmission operation in a second embodiment of the present invention.

FIG. 9 is a flowchart showing a transmission preparation operation in the second embodiment.

FIG. 10 is a flowchart illustrating a broadcast transmission operation in a third embodiment of the present invention.

FIG. 11 is a flowchart showing a transmission preparation operation in a fourth embodiment of the present invention.

[Explanation of symbols]

1...Keyboard, 2...Display section, 3...Printer, 4...FDD, 5...Facsimile communication department, 10...CPU, 11...ROM, 12...RAM, 13...CPU bus, 20...control unit, 21...input section, 22...display section, 23...printing section, 24...conversion section, 25...Communication Department, 26...Document data memory, 27...Mail list data memory, 28...Generation section.

Claims (2)

[Claims] 1. A document processing device that creates and edits various documents, comprising: an input means for inputting at least data for creating and editing documents; a first storage means for storing documents created and edited by the input means; a second storage means for storing a data group in a record format composed of one or more fields; a selection means for selecting an arbitrary record stored in the second storage means at the time of transmission;
Detection means for detecting a merge instruction command in a document stored in a storage means; Transmission document generation for generating a transmission document by inserting data in a predetermined field of the selected record based on the merge instruction command; A document processing device comprising: means; and a transmission control means for reading a partner station identification number from a predetermined field in the record and automatically dialing and transmitting. 2. In claim 1, when a plurality of records are selected at the time of transmission, a transmission document is generated for each record, and a partner station identification number is read out from a predetermined field in each record. A document processing device characterized in that a transmission operation is performed sequentially for each selected record.