Note this works only because we create a brand new table, add an autonumber column to it as well any other columns we need then insert records into it. It’ll be contiguous – as long we don’t delete any records from the table. Unfortunately, creating a brand new table every time we run this will result in bloat of the Access file – if you can do it in a separate Access file, all the better so that you can compact it when you need to.
Thanks very much for your prompt reply, which reassured me that I was on the right path. From having read various Help topics, I suspected that I'd have to use an Excel data source for the numbers. Fortunately, my knowledge of Excel was good enough to know about the drag and drop facility to create automatic sequential numbering, so the data source creation was easy. In the end, it was the mail merge (no surprises?) which proved a tad tricky, but I got there in the end. I've used MM many times and quite happily in Word documents, but for Publisher label format, it was of course a bit different. The important bit that I had to discover for myself was the significance of, after getting to the Print stage, going into Print options, to Publication & Paper Settings, and selecting Multiple Pages per Sheet (& in my case, also "Single-sided" cos my default of duplex printing had come up). But TA-DA! All is fine now. Thanks very much again.
Hi, is there any limit on the number of E-Mails ? I created an archive of 270000 E-Mails (IMAP) and it caused trouble. Can I have that amount in a local folder ? Are there any recommended number ? It locked that 50000 starts being a problem on IMAP already. How else would you handle an archive that you need frequently ? Thanks for your help Stephan If it were me... exporting them(selectively) to user created properly named Windows Explorer blank folders on the hard drive and backing up to a different drive(internal/external/cd/dvd) outside of Windows Live Mail woul...
If the second number on your raffle ticket is one higher than the first number, you must have accidentally put the <> tag after the first number (causing the next number, on the same ticket, to increase by one). You only need the <> after the second number on each ticket, so the next ticket gets a new number. (But you don’t need it on the final ticket on the **page**, because the next **page** automatically gets a new number)
Apple has a formalized version number structure based around the NumVersion struct, which specifies a one- or two-digit major version, a one-digit minor version, a one-digit “bug” (i.e. revision) version, a stage indicator (drawn from the set development/prealpha, alpha, beta and final/release), and a one-byte (i.e. having values in the range 0–255) pre-release version, which is only used at stages prior to final. In writing these version numbers as strings, the convention is to omit any parts after the minor version whose value are zero (with “final” being considered the zero stage), thus writing 1.0.2 (rather than 1.0.2b12), 1.0.2 (rather than 1.0.2f0), and 1.1 (rather than 1.1.0f0).
I've also been using NumberPress for about a year and it is awesome. You can easily position numbers as many up per form and as many up on a sheet as you will ever need. Easily change font, color, point size, angle, number of digits and can even customize prefix-ex: instead of No. you can print ABC or a form number. It also does variable data (I've only used a couple of times).Took a little while to learn but is now a piece of cake.
WordTips is your source for cost-effective Microsoft Word training. (Microsoft Word is the most popular word processing software in the world.) This tip (92) applies to Microsoft Word 97, 2000, 2002, and 2003. You can find a version of this tip for the ribbon interface of Word (Word 2007 and later) here: Sequentially Numbering Elements in Your Document.