Thanks for the head start on this, it got me part the way through my problem but I found that when I had 3 figures in a row then a map, the next figure would jump back to #.1 again. Because I had figures, maps and tables that needed to be numbered I used the ‘levels’ to differentiate between them as you suggested, but found if you create a new number list for each entry ie. number list for maps, and number list for tables etc then they don’t conflict. thanks for the start off though. no where else pointed it out as clearly as this. Cheers
But we won’t be stopping at just using a field code to increment the numbers. I’m also going to show you how to save the text (“Interrogatory No.” etc.) that precedes each number as an AutoText entry. That means you’ll be able to type just four letters and hit the Enter key (those are the “5 keystrokes” promised above) and Word will finish the phrase for you, complete with the sequence code to increment the discovery request number for you.
I am attempting to write a query joining two linked tables in a query by payroll number (all numeric). When write the query and join by payroll number I get the "Data Type Mismatch in Expression" error. Both tables have the Data Type as "Number", but the only difference I can tell is one has "Field Size" as "Decimal" and the other has "Field Size" as "Double". I have even tried to join on the VAL() of each payroll number field with no luck. Any ideas? "Decimal" and "Double" are actually different dat...
In this scenario we are assuming that there will be no more than 999 documents attached to a case. In Scenario 2 we assumed no more than 9999 inquires during a year. So you need to adjust the number of zeros when formatting Sequence for the anticipated number of records. Of course this can always be changed later. You also don’t need to format the sequence with leading zeros as the Format function does. As shown the expression returns something like: DCASD/CI123-025 for the 25th document in case CI123 for client DCASD. Without leading zeros it would be: DCASD/CI123-25. The advantage to the latter is that you don’t have to anticipate the number of records you might have in the sequence, but I’ve found many users prefer a more uniform number with the leading zeros.

With this expression we check only for records that are in the same year as the Inquiry date to increment the sequence. Again, the NZ function will automatically restart the sequence with each year. Cleary, though, we cannot generate this number until the InquiryDate has been entered. Is this value is a user entry, then you may want to check that it’s filled in before generating the number. Something like:
The expression: Nz(DMax(“[PONum]”,”tblPO”),0)+1 will check if a PONum already exists. If it doesn’t it returns a 1, if it does it returns the number incremented by 1. If the number exists, but is 0 it will return a 1. In my blog I advise that number should NOT be generated until the user is ready to save the record. And to immediately commit the record after generating the number. Therefore, there should be no issue about giving them a new number if they go back to it.
I make the design with as many up as I need on the master page, linking the frames where the numbers will go. Then I make the list using Excel, copy paste to ID and apply a paragraph style with "start in next frame" option. Click the outbox on the pasted text to get a loaded cursor and delete the frame. Then just shift-click over the first textframe on a live page to have as many "tickets" added as needed automatically.
A variety of printing products use sequential numbering printing. Carbonless forms, invoices, receipts, business forms, contracts, purchase orders, office documents, event tickets, packaging and more all use sequential numbering.  The numbers can also be printed twice on the media if required. They can be printed in any color, but are often printed in black or red to make them stand out.
One other thought. It may not hurt to make option 1 a logical expresssion where it will update the number IF a number other than 0 already exists for it. This will prevent it from giving a new number if you go back, edit it and save it. I accomplished this by adding the following (roughly): If PONo=0 Then My.PONo…. (Expression and save command) Else (Save Command)

I have a problem with Outlook 2007 and the add-in Access Outlook Add-in for Data Collection and Publishing. This add-in worked when I first installed Outlook 2007 when installing Office 2007 Enterprise. The add-in created a sub-folder in my Inbox named Data Collection Replies and worked well until about 6 weeks ago. Now I can’t get the add-in to work at all even though it appears in the list of COM.adds in Outlook 2007. More perplexing is the error message I now receive EVERY time I click on any email message to read it. The message is titled ‘Custom UI Runtime Error in... sequential numbering
×