Abstract:
An automated typesetting system is disclosed for use in the production of commercially-printed products, such as engraved, embossed, or lithographed letterhead, envelopes, business cards, and the like. The automated typesetting system is a computerized system for accurately and efficiently typesetting copy and includes a graphic template containing text and object blocks and a database containing information to be populated into the template blocks as well as instructions on how to format each of the blocks. Information from the database is optionally electronically proofchecked, populated into the template fields, formatted and typeset according to design specifications, arranged in maximally-efficient production format, and sent to print. The system may be interactively coupled with an order tracking, billing, shipping, and inventory control system.

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
   This application claims the benefit of U.S. Provisional Application No. 60/105,977, filed Oct. 28, 1998. 

   STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT 
   Not Applicable. 
   REFERENCE TO A “MICROFICHE APPENDIX” 
   Not Applicable. 
   BACKGROUND OF THE INVENTION 
   (1) Field of the Invention 
   The present invention relates generally to the art of layout and typesetting and, more particularly, to a computerized method and system of automated layout and typesetting for the production of engraved, embossed, and lithographed materials, such as stationery, envelopes, paper, and business cards. 
   (2) Description of the Prior Art 
   Since the early days of the commercial printing industry, and continuing through present day, the production of professionally printed goods-such as engraved, embossed, and lithographed stationery, envelopes, paper, business cards, and the like-has required extensive, time-consuming human design, layout, and typesetting expertise, proofing, and supervision. Today&#39;s commercial printing industry, however, requires even more time and attention to detail, as corporations invest millions of dollars developing highly-detailed corporate identities. Engraved, embossed, and lithographed stationery, envelopes, paper, business cards, and other goods are an integral part of a company&#39;s corporate identity campaign, and a major business expense. It is crucial that commercial printing technology advance in parallel to more effectively and efficiently handle the increasing industry demand. 
   Traditionally, a high level of human interaction in the production process has been required to ensure the final product satisfies high-detailed corporate identity specifications. Corporate identity specifications include customer-specific details including, among other things, font type, font size, precise font colors, logo size, logo placement, precise logo color, precise positioning measurements, character kerning and leading, and the like. Companies often publish extensive corporate identification manuals providing detailed guidelines governing the proper appearance of a company&#39;s corporate identity. Therefore, many time-consuming steps are required to produce an acceptable and accurate final product. It has therefore become necessary to dedicate considerable time and expense for obtaining experts in the art of layout, typesetting, proofing, and production. With such an increase in detail and required supervision, overhead, and ultimately consumer cost, have necessarily risen. 
   Under traditional prior art production systems, orders for printed products were typically placed via fax machine, in often-difficult-to-read hand-written format. An order would typically include the customer&#39;s name and internal identification number, identification of the goods being ordered (i.e., business cards), the quantity being ordered, the information to appear on the ordered goods (i.e., name, title, address, phone and fax numbers), and billing and shipping information. The orders would be gathered together at regular intervals throughout the day and manually keystroked into an order processing system to produce an order summary ticket. The orders would then be directed to typesetting experts for typesetting scheduling. 
   Typically, orders would be scheduled for typesetting within a day or two after receipt, depending on backlog. The typesetting expert would review the order, keystroke the information from the order into the proper customer template (a template contains a customer&#39;s specific product layout information based on the customer&#39;s corporate identity specifications), manually adjust fonts, sizing, kerning, colors, and the like where necessary, and print out the draft typeset order for a proofreader&#39;s review. The proofreader would then isolate any typographical errors or formatting changes required by the customer&#39;s corporate identity specifications, and send those changes back to the typesetter for corrections. The typesetter would then manually correct the order. Once the corrections were made, the order would again be printed and reviewed a second time by the proofreader. If the proofreader determined that all of the customer&#39;s corporate identity specifications had been met and no typographical errors existed, the order was transmitted to the customer for approval. 
   Often times, after customer review, changes would need to be made due to poor fax quality, or because the typesetter or proofchecker overlooked an error. This time-consuming typesetting and proofing cycle was repeated until the order was approved by the customer and no further changes were required. Once the final approval was received, the order would be sent on to the printing department for preparation of the production plate or film. At its fastest, the entire process would typically take a minimum of three business days, and if further information was changed by the customer during the approval process, it would take even longer. Therefore, preparation of a single engraved business card order under using traditional prior art methods, for example, from receipt of order to creation of engraving production plate, may have taken anywhere from 3 to 5 days, or longer, with multiple and repeated levels of detailed, human proofing, and therefore, high overhead and increased consumer cost. 
   In addition to increased overhead and consumer cost, the extensive and repeated human supervision required under traditional prior art systems introduced multiple opportunities for error. Therefore, the inherent faults of prior art systems for receiving, processing, typesetting, and printing commercial engraved, embossed, and lithographed materials create a substantial demand for an automated typesetting system to increase efficiency, accuracy, and productivity, while decreasing production time, errors, and costs. 
   BRIEF SUMMARY OF THE INVENTION 
   The present invention solves the problems plaguing the prior art commercial engraved, embossed, and lithographed printing systems by providing a system that automatically typesets information into a production-ready format without the need for manual typesetting and proofing. The present invention is a novel integration of computerized hardware and software that permits an order for engraved, embossed, and lithographed materials to be received and processed electronically. The invention allows a template to be created containing the detailed criteria of a customer&#39;s corporate identity specifications, a database of customer-specific information to be created based on a customer&#39;s desired product and corporate identity specifications, order information to be automatically imported into the database, the fields of the template to be auto-populated by the order information in the database, the auto-populated data to be autotypeset according to the customer&#39;s corporate identity specifications, and the autotypeset template to be sent directly to the printing machinery for creation of the production plates. One embodiment of the invention includes an integrated electronic proofchecking option to allow orders to be proofchecked prior to printing the production plate or film. In another embodiment of the invention, the automated typesetting system is interactively coupled with a computerized order tracking, billing, shipping, and inventory control system. 
   Therefore, it is a general object of the present invention to provide a novel and useful computerized automated typesetting system for use in the commercial engraved, embossed, and lithographed printing industry. 
   Other more specific objects of the present invention are to decrease commercial printing order turnaround time, improve order processing efficiency, increase productivity, increase product quality, eliminate order errors, minimize repetitive order proofing, decrease overhead and administrative costs, and create substantial cost savings for customers. 
   A further object of the present invention is to provide a system in which no human adjustments or corrections to the information submitted by the customer are necessary before the information passes through the production process. 
   Another object of the present invention is to provide a system whereby order processing time, from receipt of order through typesetting, may be achieved within 1 day instead of 3 to 5 days. 
   It is also an object of the present invention to provide simple integration with an automated order tracking, billing, shipping, and inventory control system. 
   An additional object of the invention is to provide users of the system the ability to place orders for engraved, embossed, and lithographed materials, such as stationery, envelopes, paper, business cards, and the like, directly and electronically via a computer network, such through a Web site on the Internet, on a computer platform-independent basis, rather than relying on prior art error-prone ordering systems. 

   
     BRIEF DESCRIPTION OF THE DRAWINGS 
       FIG. 1  is a diagram outlining the automated typesetting system taught by the preferred embodiment of the present invention. 
       FIG. 2  is a sample PageMaker template for business cards created using the preferred embodiment of the present invention. 
       FIG. 3  is a sample PageMaker page setup dialog used to set a template&#39;s printing parameters using the preferred embodiment of the present invention. 
       FIG. 4  is an illustration showing the setting of the zero-point of a template in PageMaker using the preferred embodiment of the present invention. 
       FIG. 5  is an illustration showing the creation of a text block in a template in PageMaker using the preferred embodiment of the present invention. 
       FIG. 6  is a sample PageMaker save menu used to save a completed template using the preferred embodiment of the present invention. 
       FIG. 7  is an abridged sample FileMaker Pro Database File Program under the preferred embodiment of the present invention (redacted to remove confidential information unrelated to the disclosure of the present invention). 
       FIG. 8  is a sample Web Site Program listing HyperText Markup Language code that allows a user of the preferred embodiment of the present invention to enter populating data via an Internet Web site (redacted to remove confidential information unrelated to the disclosure of the present invention). 
       FIG. 9  is a sample Web Import Script listing the AppleScript code that allows data inputted via a Web site to be imported into a database file in the preferred embodiment of the present invention. 
       FIG. 10  is a sample FileMaker Pro Web Import Script listing the FileMaker Pro script code that allows data inputted via a Web site to be imported into a database file in the preferred embodiment of the present invention (redacted to remove confidential information unrelated to the disclosure of the present invention). 
       FIG. 11  is a computer screen shot showing a sample electronic proofchecking screen for proofchecking and correcting the populating data in a database file record in the preferred embodiment of the present invention. 
       FIG. 12  is a sample Database File Search Script listing the FileMaker Pro script code that searches a database file to locate unprinted records in the preferred embodiment of the present invention. 
       FIG. 13  is a sample Template Populating Script listing the FileMaker Pro script code that sends a found set of unprinted database file records to PageMaker for printing in the preferred embodiment of the present invention (redacted to remove confidential information unrelated to the disclosure of the present invention). 
       FIG. 14  is a code listing from a sample FileMaker Pro database file instructing PageMaker, under the preferred embodiment of this invention, to print a template. 
       FIG. 15  is a sample series of Template Format Scripts listing the FileMaker Pro script code that instructs FileMaker Pro to create duplicate or dummy records where appropriate to fully populate a template in the preferred embodiment of the present invention. 
       FIG. 16  is a sample the Order Tracking, Billing, Shipping, and Inventory Control System Export Script listing the FileMaker Pro script code that instructs FileMaker Pro export data from a customer&#39;s database file to an external, interactively coupled order tracking, billing, shipping, and inventory control system in the preferred embodiment of the present invention. 
   

   DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT 
   A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever. 
   An outline of the preferred embodiment of the present invention is shown in FIG.  1 . The preferred embodiment of the present invention operates on Apple Computer, Inc.&#39;s Macintosh computer operating system, using Apple Computer&#39;s standard operating software (System  7  or newer) and a combination the off-the-shelf software packages FileMaker Pro by Apple Computer&#39;s Claris division and Adobe PageMaker by Adobe Systems Inc. FileMaker Pro and PageMaker may reside on the same physical computer, or may reside of different computers, connected together using traditional, prior art networking technology. 
   FileMaker Pro is a scriptable database software program capable of receiving, storing, and manipulating data and allowing a user to create, design, and program customized databases; PageMaker is a graphics software program capable of receiving, storing, and manipulating text and graphics to create documents for publication and printing; and, Apple Computer&#39;s operating software is a scriptable computer software operating system capable of controlling events-compatible applications such as FileMaker Pro and PageMaker, allowing FileMaker Pro and Adobe PageMaker to communicate and exchange information with each other, and allowing multiple computers and peripherals to communicate and exchange information with each other either directly or over a network. FileMaker Pro and PageMaker are compatible with the Apple Computer operating system&#39;s AppleScript and Apple events scripting and events technology. Apple events-compatible programs can communicate with and control one another, allowing for the transfer and exchange of data and instructions. Those skilled in the art of graphic design are intimately familiar with the graphics software and hardware systems used in this invention, as a majority of such work is performed on Apple Macintosh computers using these programs. Those skilled in the art of events and script programming are intimately familiar with the programming techniques used in this invention. 
   The automated typesetting system of the present invention begins with the creation of an electronic template. The template is a set of coordinates and guides, for a certain document size and layout, used for production purposes. The template is created in a graphics software program that allows for creating, designing, storing, accessing, and updating a template and that is compatible with events and script technology, such as PageMaker in the preferred embodiment. The template is based on the design specifications of the customer&#39;s corporate identity and how the production process of the particular product is going to be run. The type of product design (stationery, envelopes, paper, business cards, etc.) and the customer&#39;s desired production run (engraved, embossed, lithographed, etc.) will dictate how the parameters of the template will be set up. Different production runs call for different layouts based on the type of product, the dimensions of that specific product, and how that particular product will be run for best production and cost efficiencies. 
   It will be appreciated that dozens of combinations of product designs and production runs are possible under the present invention, but by way of example only, this disclosure will often refer to the production of lithographed business cards. The present invention may be appropriately configured and programmed to allow for processing of myriad product designs and production runs as needed (i.e., embossed letterhead, engraved envelopes, lithographed stationery, etc.). 
   In the preferred embodiment of the present invention, the template is created using the PageMaker software program. A template is created for every individual customer and order on an as-needed basis, wherein each template contains the specific design and layout characteristics for that specific customer and that specific product design and production run. Using standard prior art design principles, the template is designed and configured in such a way so as to make production of the order possible while minimizing any potential loss of production time and production material waste. By way of example, a template for business cards may be created in a 3-up format, as shown in  FIG. 2 , since the size of a standard business cards permits at least 2 columns of 3 business cards to fit on a printing plate. 
   To create a template with the proper configuration and layout for a specific order, the document size (the size of the production plate, for example), printing parameters, place locations (x-and-y coordinates) for text and object blocks, and any other related parameters are set in the PageMaker template using the PageMaker menus and resulting dialogs,  FIG. 3 , to set the document size (the size of the production plate), the document&#39;s printing parameters (i.e., portrait or landscape layout, printing resolution, etc.), and the template&#39;s text and object block locations. 
   The text and object block locations are entered into the PageMaker template by first establishing the x-and-y coordinates of the template based on a fixed zero-point location (0,0), which resides in the upper left-hand corner of the template. To set the zero-point in the preferred embodiment of this invention, the pointer tool is positioned on the cross section in the zero-point window,  FIG. 4 , and the zero-point is dragged to the proper location. Releasing the mouse button to resets the zero-point to the new location. 
   Once the fixed zero-point location for the template is set, creation of the template continues by plotting the various x-and-y coordinates for the location of each text and/or object block required by the product design, production run, and the customer&#39;s corporate identity specifications. Each location on the template has its own unique x-and-y coordinates. Based on the specific design, there may be as few as one text block for all of the required information, or various combinations of text and/or object blocks, each block designed to hold different information (such as name, title, address, phone number, company logo, etc.). 
   Setting the x-and-y coordinates for the text and object blocks is done manually, using the PageMaker standard design tools to establish the size and location of each block, FIG.  5 . As shown in  FIG. 2 , dummy text may be placed in the blocks as place holders to help determine the size and positioning of each block. For example, for a 5-up lithographed business card template, the template would contain the layout specifications of 25 individual business cards or, as shown in  FIG. 2 , a template could contain the layout specifications for 6 individual business cards in a 3-up format. The template layout, as mentioned above, is determined using prior art graphic design techniques to minimize production waste. The time required to establish all of the x-and-y coordinates for each block will vary depending on the desired product design, production run, and corporate identity specifications, however, the coordinates need only be established once per template. Once a template for a specific product design, production run, and corporate identity specification is created, it may be saved and reused indefinitely until that customer&#39;s corporate identity specifications are changed or updated. 
   Once the x-and-y coordinates for all text and object blocks on the template have been established, the template is given a name and path (the specific location of a file on a computer&#39;s storage media) and saved so as to permanently maintain the zero point location, the various x-and-y coordinates, and the other document and print parameters that have been established. Saving the template may be accomplished using Adobe PageMaker&#39;s standard save menu, FIG.  6 . 
   In addition to the creation of an appropriate template, a database file is created and programmed to receive and store the populating data (such as name, title, address, phone number, etc.) that will ultimately populate a template and to store the instructions that will be used to format the populating data that will appear in a template&#39;s blocks (font, size, kerning, color, etc.). In the preferred embodiment of the present invention, the database software program FileMaker Pro is used to create, design, program, store, access, and update the database file and store, access, and update the file&#39;s records. FileMaker Pro&#39;s internal scripting language, in combination with Apple Computer, Inc.&#39;s system software&#39;s AppleScript and Apple events technology, allows FileMaker Pro to communicate and interact with PageMaker. 
   FileMaker Pro allows the creation and customization of a database file to receive, store, and manipulate data. A database file is created on a customer-by-customer basis. Therefore, each database file contains the database fields needed to process any order for any product needed by that specific customer. By way of example, the database file for a customer who only orders lithographed business cards will contain, at a minimum, the fields necessary to receive the data that will ultimately populate the lithographed business card template created for that customer. The database file may also contain supplemental fields to hold other information about an order. Database files for other customers may include alternate or additional fields depending on the product designs and production runs desired by that specific customer. Like templates, database files may be changed and updated as necessary to reflect a customer&#39;s changing corporate identity and/or desired product designs or production runs. 
   Creating and programming a database file to include the necessary fields uses standard prior art FileMaker Pro database programming techniques intimately familiar to those skilled in the art of database programming. For example, the database file for a customer who orders business cards is programmed using the preferred embodiment of the present invention to contain, at a minimum, the following indexed text fields to represent the information that typically appears on a business card: Address1, Address2, Address3, and Address4 (representing the up to four lines of an address); City (representing the city); Company Name (representing the company name); Country (representing the country); Email (representing the email address); Fax (representing the fax number); Name (representing the name), State (representing the state), Title (representing the title), and Zip Code (representing the Zip code), as shown in the abridged sample Database File Program, FIG.  7 . The abridged sample Database File Program,  FIG. 7 , also shows examples of other fields, describe below in further detail, that may be used in the preferred embodiment of the present invention to allow the present invention to be interactively coupled with an order tracking, shipping, billing, and inventory control system. An unabridged sample Database File Program under the preferred embodiment of the present invention is appended (redacted to remove confidential information unrelated to the disclosure of the present invention). 
   As further shown in FIG.  7  and in the appended unabridged sample Database File Program, the database file is programmed to include a number of calculation fields. Calculation fields, as known to those skilled in the art of FileMaker Pro database programming, perform calculations or otherwise manipulate data based on the instructions contained within the calculation field. Of significant importance in the preferred embodiment of the present invention are the database file calculation fields containing the instructions and parameters to be transmitted to and performed by PageMaker in the population of a template and the formatting of the populating data on the template. In FIG.  7  and in the appended unabridged sample Database File Program, an example of one such a field is BCard01. The BCard01 calculation field is programmed to contain the PageMaker instructions and parameters needed to populate and format the first business card on a template. Likewise, BCard02 contains the PageMaker instructions and parameters needed to populate and format the second business card on a particular template. BCard03 contains the instructions and parameters for the third card, and so on. Enough calculation fields are programmed into the database file to provide for the population and formatting for an entire template. A more detailed explanation of such instructions and parameters is presented later is this description. 
   In operation, populating data is entered into a customer&#39;s database file through various front end mechanisms, including manual entry of the data into the database file, but preferably by automated electronic means such as through an Internet Web site, remote access, File Transfer Protocol (FTP), or e-mail. In the preferred embodiment of the present invention, an Internet Web site is used to receive the populating data. Web site entry is preferred because it allows for worldwide, computer-platform independent access to the automated typesetting system taught by the present invention. 
   Using standard prior art HyperText Markup Language (HTML) programming language, specific Web pages are created for each customer and are programmed to allow the user of the Web site to place orders for products created by the present invention by permitting electronic entry of the populating data and other order parameters. The HTML programming code, as shown in the sample Web Site Program in  FIG. 8 , allows the data received from a Web site user. The Web site may be hosted on the same physical computer as FileMaker Pro and/or PageMaker or, in the preferred embodiment of the present invention, may be connected to the FileMaker Pro-hosting computer using standard, prior art computer networking technology. The data is automatically imported, field by field, into the customer&#39;s database file using a combination of AppleScript and FileMaker Pro script programming, as shown in their preferred embodiments in  FIG. 9 , the sample AppleScript Web Import Script, and  FIG. 10 , the sample FileMaker Pro Web Import Script. 
   After the populating data is entered into the database file, in one embodiment of the present invention, the populating data may be optionally electronically proofchecked for design specification verification. FileMaker Pro may be programmed, to display the populating data in the appropriate product design format, FIG.  11 . If it is then found that some type of error has been inputted that would compromise the customer&#39;s design, or a typographical error has occurred, the record can be immediately fixed by correcting the populating data in the appropriate database file record&#39;s field, as shown in FIG.  11 . To preserve the integrity of the original data that was inputted into the customer database file by the customer, the original information may be maintained in one set of database file fields and the modified information in separate set of fields. Alternatively, the populating data, in the form of database records, may be checked by a human proofreader to confirm grammatical and contextual correctness. Records that then receive proofreader approval may continue on through the production process. 
   The remainder of the present invention involves execution of appropriate scripts to allow PageMaker and FileMaker Pro to exchange the information required to produce a final product ready for production. In the preferred embodiment of the present invention, a FileMaker Pro script is created, using FileMaker Pro&#39;s internal scripting language, and as shown in  FIG. 12 , the sample Database File Search Script, to instruct FileMaker Pro to locate customer database file records that have not yet been populated into a template, and therefore, not yet printed. This is accomplished using fields created in each customer&#39;s database file that will flag when a record is sent to a template. As shown in FIG.  7  and in the appended unabridged sample Database File Program, the SenttoFilm indexed text field is programmed into the database file and initially set to a value of “No.” 
   As shown in  FIG. 12 , the FileMaker Pro database program is instructed to search a customer database file and locate, for like records (such as by division, address, city, etc.), those records that have not yet been printed by looking for unflagged records, or records where the SenttoFilm field contains the “No” value. After FileMaker Pro finds such unprinted records in a customer database file, the found set of records is sent to PageMaker for population of the appropriate template by the Template Populating Script, FIG.  13 . 
   Beginning with the first record in a found set of unprinted records, the Template Populating Script,  FIG. 13 , using events technology, sends the populating data from the first found record to PageMaker. When programming the communication of commands between FileMaker Pro and PageMaker, it is crucial to encapsulate the commands within quotation marks followed by a calculation field (the Quote field, as shown in FIG.  7  and in the appended unabridged sample Database File Program) that contains a calculation to produce quotation marks. The exact syntax of the FileMaker Pro to PageMaker commands is essential for, if the syntax is incorrect, the script will cease operation at the first indication of missing or additional quotation marks. 
   As shown in  FIG. 7 , in the appended unabridged sample Database File Program, and in  FIG. 13 , the populating data is sent from FileMaker Pro to PageMaker through the BCard01 calculation field, mentioned above. The programming in the BCard01 calculation field first instructs PageMaker to open (using the “open” command) the correct template created for the specific product design and production run. The template is identified by the name and path assigned to it when it was created, as discussed above. The path can reside on a local hard drive or can be located on a networked drive. 
   The Database File Program calculation field is programmed to set the measurement units of the PageMaker template (using the “measureunits” command). The Database File Program calculation field is further programmed to select the x-and-y coordinate locations of the template&#39;s first block, enter a text edit mode, select all of the information that currently resides in that block of the template (the dummy text entered in the template) as place holders, and then place the populating data from identified database file field into the block that is currently selected in the template. This is accomplished using the “select,” “textedit,” “selectall,” and “textenter” commands as shown in the BCard01 calculation filed in FIG.  7  and in the appended unabridged sample Database File Program. 
   After the populating data is entered into the first block of the template, the various design specifications for that block, such as kerning, leading, font styles, font sizes, colors, etc., are adjusted. This is accomplished by programming the design specification commands into the Database File Program&#39;s calculation field. Using the appropriate PageMaker commands, such as “select,” “textedit,” “textselect,” “font,” “sizebump,” “KernText,” and “Color,” as shown in the BCard01 calculation field in FIG.  7  and in the appended unabridged sample Database File Program, FileMaker Pro instructs PageMaker to select the appropriate x-and-y coordinates of the block that needs to be adjusted, resets PageMaker into a text edit mode, and transmits to PageMaker the commands necessary to complete the desired formatting. For example, to set the kerning for a given text block, PageMaker is instructed by FileMaker Pro to set the cursor within the appropriate text block (identified by its x-and-y coordinates), highlight the text that needs to be kerned, and adjust the kerning as required. The design parameters are based on a customer&#39;s corporate identity specifications as programmed into the Database File Program. 
   The present invention can set any formatting that a human operator could set manually. The great advantage is that a human operator could accidentally move or change something incorrectly, where the present invention cannot—it only moves or adjusts the data it is programmed to change. 
   When the first set of x-and-y coordinates have been fully populated and formatted, Database File Program&#39;s calculation field is programmed to continue on to the x-and-y coordinates of the next block on the template and perform the identical functions as stated above for the populating of the block and the formatting of the populating data according to the programmed design specifications. Once all of the populating data from the first found record is populated and formatted, the Template Populating Script instructs FileMaker Pro to move on to the next found record and to repeat the process for the next set of blocks on the template (for example BCard02), as shown in FIG.  7  and in the appended unabridged sample Template Populating Script. Only after all of the populating data from all of the found records have been fully populated with all formatting design specifications followed, is PageMaker instructed by FileMaker Pro (using the “printoptionsps” and “print” commands, as shown in  FIG. 14 ) to send the template direct to the appropriate device, either directly connected or connected over a computer network using standard, prior art networking technology, for the manufacture of production-ready plates or films. 
   In the event that the number of found records in a customer&#39;s database file does not match the available space on the appropriate template, the system will compensate to ensure the most efficient production run. For example, if multiple found records exist, and the total count exceeds the number of set x-and-y coordinates on the appropriate template, FileMaker Pro instructs PageMaker to populate the first template as stated above and then instructs PageMaker to open subsequent templates until all records in the found set are populated on templates, as shown in  FIG. 15 , the Template Format Scripts. 
   Similarly, if the number found records is of an odd number, in which the whole template cannot be populated, the Template Format Scripts instruct FileMaker Pro to duplicate records or make a dummy records as appropriate to finish the process. An example of the preferred embodiment of this process is shown in FIG.  15 . Examples of the process are explained below. 
   If the production will be engraving printed on a three-up plate, the programming ensures that FileMaker Pro properly populates the appropriate template as follows. When the number of found records to be printed is equal to one, four, seven or ten, FileMaker Pro is programmed to duplicate the last record two times to make a complete three-up plate of that record. If the number of sets is equal to two, five, eight or eleven, FileMaker Pro is programmed to create a dummy blank record to complete the three-up plate. 
   The same philosophy applies to lithography orders. For instance, if a lithographic plate accommodates thirty business cards running five-up, FileMaker Pro is programmed to perform counts based on multiples of five to properly populate the appropriate template with minimum waste. If the number of sets is one, it would populate the whole plate by itself. For a count of two, FileMaker Pro duplicates the first record fourteen times and duplicates the second record fourteen times, sorts the records by name so the records would be properly placed together, and then populates the template. For a count of three, each record is duplicated nine times, then sorted by name so the records would be properly placed together when populating the template. A count of four would result in duplication the each of the four records six times, and creation of two dummy records. 
   Similarly, a count of five would duplicate the first five records five times. A count of six would duplicate the first six records four times. A count of seven would duplicate the first seven records three times each then create two dummy records. A count of eight would duplicate the first eight records two times each then create six dummy records. A count of nine would duplicate the first nine records two times each then create three dummy records. A count of ten would duplicate the first ten records two times each. A count of eleven would duplicate the first eleven records one time each then create eight dummy records. A count of twelve would duplicate the first twelve records one time each then create six dummy records. A count of thirteen would duplicate the first thirteen records one time each then create four dummy records. A count of fourteen would duplicate the first fourteen records one time each then create two dummy records. A count of fifteen would duplicate the first fifteen records one time each. If the number of sets is greater then fifteen but less than thirty, one dummy record is created to fill up the production plate. The Template Format Scripts programming creates a production fail-safe system in that an order will not be produced in excess, while production materials such as film, plates, and stock are saved. 
   In one embodiment of the present invention, the automated typesetting system is interactively coupled with an automated order tracking, billing, shipping, and inventory control system. Such tracking, billing, shipping, and inventory control systems are generally known in the prior art. The interactive relationship between the automated typesetting system and the tracking, billing, shipping, and inventory control system is built based on the transfer of the information from the FileMaker Pro customer database file fields into the appropriate fields of the order tracking system. Therefore, when a new order is processed by the FileMaker Pro database, FileMaker Pro simultaneously communicates with the tracking, billing, shipping, and inventory control system and populates various analogous fields in the tracking, billing, shipping, and inventory control system, such as a customer number (specific for each customer), a shipment due date, and the type of shipping required. In response, the tracking, billing, shipping, and inventory control system then creates and communicates a job ticket number to the FileMaker Pro customer database file where it is stored in a specific field, the indexed text field JobTicket as shown in the FIG.  7  and in the appended unabridged sample Database File Program. A template may also be created with an appropriate text block to hold an order&#39;s job number, so the template may be easily identified during production. 
   Once all found records have been sent to templates for printing, information from fields in a customer&#39;s database file is transmitted to the tracking system for inclusion on the job ticket. Such fields, which may be programmed in the customer&#39;s Database File Program, include item codes, shipping name, address, phone number and ship method, billing codes, quantity of order, item(s) being ordered, billing information, and any other required data. A preferred embodiment of such an interactive relationship between the automated typesetting system and the tracking system appears in  FIG. 16 , the Order Tracking, Billing, Shipping, and Inventory Control System Export Script. 
   While a specific embodiment of the present invention has been shown and described, it is to be understood that numerous changes and modifications may be made therein without departing from the scope, spirit, and intent of the invention as set forth in the appended claims.