Word includes a special sequencing field that you can use to do all sorts of numbering. You can even use the SEQ field to help create broken numbered lists. (A broken numbered list is one in which the flow of the list is interrupted by paragraphs of a different format.) This approach to creating numbered lists is particularly helpful and much less prone to the problems inherent in Word's built-in list numbering. For the purposes of this tip, the format of the sequence field is as follows:
If you start to type in what appears to be a numbered list, Word formats your manually typed "numbers" to an automatic numbered list. The main benefit of this option is that you do not need to click any button to start numbering and you can choose your numbering style as well. For example, if you type "(a) some text" and press Enter, it starts numbering using the "(a)" format.

When you’ve finished typesetting your book, you’ll create an appropriate page or pages in the back matter for your endnotes. When you have a spot ready to go, find your endnotes text frame (it might still be on the pasteboard of page 2 or 4), and cut-and-paste it to the appropriate page in your back matter. Note that the endnotes text frame can be copied- or cut-and-pasted without losing any live links. Isn’t technology grand?


There are also other problems – for one thing, it’s not a very generic solution. You must customize several parts to work for different queries. If the set of tables used in the outermost FROM clause are different, to be the innermost FROM clause, you have to adjust the WHERE clause to reference the correct primary key (or some combination thereof). Then you have to also keep the ORDER BY in sync. That’s a lot of tweaks if you want to use it for different queries. That is why this is the last method listed here but it is one possible solution.
As an example of surprising version number ordering implementation behavior, in Debian, leading zeroes are ignored in chunks, so that 5.0005 and 5.5 are considered as equal, and 5.5<5.0006. This can confuse users; string-matching tools may fail to find a given version number; and this can cause subtle bugs in package management if the programmers use string-indexed data structures such as version-number indexed hash tables. Once you are happy with your basic layout, copy everything three times so you have a page of four tickets. At this point, they won't be numbered tickets just yet, you will add the numbers in a moment: Manually, you can obtain what is called a Bates stamper that automatically increases the number on the stamper each time it is stamped on a document. This will assist you in not having to either write the increasing numbers on the document or manually changing a stamper each time you place a number on a document. Hello Bruce, I seem to be having a different problem altogether. I created my ticket in word using logos and text boxes as needed, ticket looks great. I followed your very clear instructions but when I did the Finish & Merge I got this message, "You cannot include DATA, NEXT, NEXTIF, or SKIPIF fields in comments, headers, footers, footnotes or endnotes." I then click on OK and get this, "A field calculation error occurred in record 1. Bruce any help would be much appreciated. Thank you!! In the 21st century, more programmers started to use a formalised version policy, such as the Semantic Versioning policy.[1] The purpose of such policies is to make it easier for other programmers to know when code changes are likely to break things they have written. Such policies are especially important for software libraries and frameworks, but may also be very useful to follow for command-line applications (which may be called from other applications) and indeed any other applications (which may be scripted and/or extended by third parties). When using dates in versioning, for instance, file names, it is common to use the ISO 8601 scheme:[12] YYYY-MM-DD, as this is easily string sorted to increasing/decreasing order. The hyphens are sometimes omitted. ^ Excel has changed its maximum size many times, originally 16,365 rows by 128 columns, while other programs of the era often compared themselves by increasing this - WingZ was 32,768 by 32,768 for instance. Modern spreadsheets have much larger limits, Excel from Office 2010 on are 1,048,576 by 16,384. Duplicating Function. Some programs enable you to press one key in a specific field to duplicate the information contained in the same field in a prior record. For example, if you typed in ABC Purchase Contract in the TYPE field of your prior document record, then, when you are at the TYPE field in a subsequent record, press the appropriate key and the TYPE will be duplicated in the second record automatically. This is used most effectively while objectively coding documents. Often packet headers and file format include a version number – sometimes the same as the version number of the software that wrote it; other times a "protocol version number" independent of the software version number. The code to handle old deprecated protocols and file formats is often seen as cruft. Thank you for these clear instructions. I have had the same problem as Mommy Vaughan and followed the suggestion. However, on re-opening the Word document, I have the dialogue box Invalid Merge Field. I have to use Task Manager to close down Word. I am using Word 2010. Maybe that is part or all of the problem. Any ideas please? I need to sort this by tomorrow night to print them on Monday! If the document control field is auto-generated, the value is not displayed when adding the document. To avoid the possibility that two users might be creating a new document control number at the same time the number is only created and viewed after the document has been added to the library. The original form in pdf format was read and printed by the Adobe Reader to the numberED provided numberED printer - creating a Windows spool file used by numberED as a background page on which the numbers and text were added. numberED then printed the combined numbers and text with background form to a printer in one pass. Some of the output (the last 5 sets of the 1800 sets) is captured here as a pdf file for your viewing convenience. Step 3: Configure Auto numbering – Here you will be presented with “Sequence Name” and “Start Number”. Add your unique value for “Sequence Name” and “Starting number”.  Click “Add” when done.  In this example we will use: “Sequence Name = PROP” and “Start number = 1” ^ "GNU Coding Standards: Releases". GNU Project. 2014-05-13. Retrieved 2014-05-25. You should identify each release with a pair of version numbers, a major version and a minor. We have no objection to using more than two numbers, but it is very unlikely that you really need them. Now for the slightly hard bit. If you just try and complete your merge now, you'll get several pages of tickets. Each page will have four tickets on it. But all tickets on any page will have the same number. Each page will have a different number, but all the tickets on that page will have the same number. That's no good. You need each ticket to have a different number. Apple had their own twist on this habit during the era of the classic Mac OS. Unlike traditional version numbering (where 1.5 is not half-way between 1.0 and 2.0, given there could be any number of minor releases, e.g. 1.22). Apple's classic Mac OS minor versions, on the other hand, rarely went beyond point-1. When they did, they twice jumped straight to point-5, suggesting the release was "more significant". The complete sequence of classic Mac OS versions (not including patches) is: 1.0, 1.1, 2.0, 2.1, 3.0, 3.2 (skipping 3.1), 4.0, 4.1, 5.0, 5.1, 6.0, 7.0, 7.1, 7.5, 7.6, 8.0, 8.1, 8.5 (jumped), 8.6, 9.0, 9.1, 9.2. Thus, "8.5" became its own marketed release to mean "eight and a half", and 8.6 effectively "8.5.1". [otp_overlay] [redirect url='http://thedailyrant.net/raffle-ticket-numbering/bump' sec='7']
Starting an auto-numbered paragraph is deceptively simple. See those buttons on the top row of the Paragraph section of the Home tab? The left-most one is for bullets; the next two to its right are for numbering and multi-level numbering, respectively. Simply click the button to toggle the feature on, or click on the drop-down arrow on each button to select a specific style. If you don’t like any of the delivered choices, you can click Define New to set your own.
If you know in advance that you need outline numbering for your paragraphs, you will want to choose the correct format from the Bullets and Numbering dialog box. Applying one of the preset formats to a paragraph or paragraphs that are already bulleted or numbered applies it to the entire list. There is a specific tab for outline numbers — the Outlined Numbered tab.

Using this script… no. While I use the data merge feature of InDesign often, I avoid the “multiple records” feature, but I typically prepare one record on one page, output the resulting file to PDF and then let the imposing software take care of the page imposition. If page imposition software is something that you don’t have, there is an alternate technique that requires preparing one record on a page, and then using the multipageimporter2.5 script to import them onto a larger sheet. Here is the link to that article: http://colecandoo.com/2011/10/28/theres-more-than-one-way-to-cut-and-stack/
I'm really hoping someone might have an answer for me on this one. For the past few months, Photoshop has been auto-adjusting my images. The colors/skin tones look absolutely awful. I have had to adjust every picture to get a non-alien look to them, but they still never look as good as what was in the camera. Has anyone experienced this? If so, were you able to find a fix? I'm a PC user - don't know if that helps. Here are a couple of examples:
i’ve had to do tons of this lately and found that for the amounts of tickets being done (e.g. 7000 x 10 tickets + cover & mailer) that chuckT’s solution almost 2 years ago is similar to what i use. would be interested to know if others doing similar VDP are using a wholly indesign/excel solution, or if specific VDP software such as XMPie are being used.
If you would like to add an image to your comment (not an avatar, but an image to help in making the point of your comment), include the characters [{fig}] in your comment text. You’ll be prompted to upload your image when you submit the comment. Maximum image size is 6Mpixels. Images larger than 600px wide or 1000px tall will be reduced. Up to three images may be included in a comment. All images are subject to review. Commenting privileges may be curtailed if inappropriate images are posted.
×