We use the auto page numbering trick here, the trick is to do it as spreads. You just make your pages the same size as the ticket with crops and bleeds. Then set up the shell on the master page and place your auto page number where you want your numbers. Each pages is the next number. You can also have two sets of numbers for perforated ticket. You then can use the page start options to add to the numbers and keep the same number of total numbers. For example you would do a new page start after number 99. 0001 to 0099 so it doesn't add two "0's" to the front of 100 and you get 00100 when you want 0100. Works great for small quantities, we have done up to 1000+ tickets and once you do it once or twice it is a snap to set up. To avoid having to do 1000 pages just send the tickets in groups. Usually between 25 to 100 at a time works good depending on artwork file size. Just save each time before sending to printer and name the file with what the tickets are. Like "MyTickets-0001-0100.Indd". Makes it easier to go back if you have a problem. You can even do two rolls of tickets if your using 12 x 18 sheets by flipping the sheet and doing one row along the top and one along the bottom on reverse side. That is if your ticket is single Sided. Two sided tickets are a bit trickier. :-)

Select the Text Tool (T) and start dragging a text box that will wrap around the whole ticket including the crop marks. This is very important since the Data Merge will automatically calculate the duplication. Then open up the Text Frame Option (Command + B) and set the Inset spacing to 1p4 for the top and 1p8 for the left. Of course, you can place the text for the numbers anywhere you like. I set the numbers to a small text.


The Artifact ID should NOT be your PK. There is no reason for it to be and to try and use it as such will be a headache. A primary key is simply a unique identifier for a record. Many purists will tell you that users should never see the PK and in your case, I would recommend that. Use an Autonumber as you PK and you can use that as your corresponding Foreign Key in related records. To prevent duplication you can make the combination of Collection Point ID and Artifact ID a unique, multi-field index. Then display the combination as I indicated where you need to show the user a record ID. This is all explained int he blog.
Is it acceptable to have long and difficult-to-read and remember numbers? Yes, of course! Is it practical? I do not believe so! In the example above, the procedure numbers, without the tab, contained seven digits. This meant that the system was prepared to handle almost 10 million part numbers (PN). The company had approximately 250 documents and probably would never go beyond 300. If nothing else, just reading these numbers with five sequential zeros may give one a headache. Those folks figured it out too - that is why they called document 0000057-001 “fifty seven.” Surprisingly, this is not the worst case I have experienced! The company that won my “The Worst Part Number” Grand Prize assigned 12 (!) digits to their part numbers in alphanumeric format.
Number Pro does not create your raffle ticket or document it just allows an easy way to  number them. Check out Number Pro, take a look at the demo videos and even try the demo of Number Pro to see how it works. Number Pro is a cloud based application meaning there is no download of the application. We access the application online in the members area. They offer a three year membership with unlimited use.
I am using your instructions to create a page of tickets - the design has been created as a picture so I added a text box to "hold" the mail merge instructions but I keep getting the error message "You cannot include DATA, NEXT, NEXTIF, or SKIPIF fields in comments, headers, footers, footnotes or endnotes." I have not included any of these but I'm wondering if it's because I've attempted to insert it in a text box. Is there an easy way to do this? TIA
I am having trouble with this procedure. My situation is almost identical to example #2. I want to populate RecordNumber on my form with a date number like “130001, 130002, etc.” where “13” is the year based on a date automatically generated in the OpenDate field in tblLogRecords. OpenDate is a date/time type field that has a default value of the date the record is created and is not editable. I have added a field called Sequence to tblLogRecords and it is a Number, Long Integer type. I also created a bound control for Sequence on my form. I have a completely separate autonumber field as the PK.
In an early planning meeting, someone on a project we’re working on requested a 65 digit number for a document! This code wasn’t just numbers, it included letters and symbols as well. There’s no doubt that this system was super-organized, but is it practical? It’s worth remembering that the doc number has to be understood by everyone, including external suppliers and subcontractors. Plus the longer the number, the greater the risk of human error.
Normally, the term infinite sequence refers to a sequence that is infinite in one direction, and finite in the other—the sequence has a first element, but no final element. Such a sequence is called a singly infinite sequence or a one-sided infinite sequence when disambiguation is necessary. In contrast, a sequence that is infinite in both directions—i.e. that has neither a first nor a final element—is called a bi-infinite sequence, two-way infinite sequence, or doubly infinite sequence. A function from the set Z of all integers into a set, such as for instance the sequence of all even integers ( …, −4, −2, 0, 2, 4, 6, 8… ), is bi-infinite. This sequence could be denoted {\displaystyle (2n)_{n=-\infty }^{\infty }} .
Ok, generating a random 3 digit number is a whole different thing, so I’m not going to go into that. If you want your numbers to start at 100 (to insure three digits) then change the 0 to 99. The Nz function will return the value listed if the field is Null. So the first time you execute that code, the DMax should return a Null since no numbers have been generated for the PONum field. The Nz will then substitute 99 and then increment that by 1. You can accomplish something similar by just entering 100 as the PONum for one record. .
Remember that you must update the values in the sheet if you want to continue the numbering series with the next batch of tickets. For instance, if you want your next batch of tickets to start with 112, you'd open the workbook and change the value 100 to 112, and update the remaining values accordingly. Don't forget to save the workbook after updating the values.
Document control number Fields are created and modified in the Library Administration section of FileHold therefore the creators must have at least Library administration rights. Once a document control number schema is created users can create new document and a new and unique document control number will be automatically allocated. Once a document number field is assigned to a schema and documents are created using this schema parameters cannot be modified.
Scott, I had posted on Microsoft and you sent me to your blog to have the numbering system (similar to APEX example) explained. I am not a programmer and I don’t understand where these codes and expressions are even suppose to go in access. When I do try to implement the little I do know I continue to get errors. I am not sure if I am putting the information in the wrong place or if I am way off. Do you know of any youtube videos that could walk me through it step by step? Or if you have the time could you help walk me through the steps.

Though the seems simple, when the try and do the things using spreadsheets - frequent mistakes happen. It is not uncommon to see two different document with the same document number in the EPC industry. To ensure that the document numbering system is useful for the project - the document control center has to ensure that there is a uniqueness check built upon the document numbering method for the project.
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)
×