There’s an old Steve Martin joke about how to make a million dollars which starts, “First, get a million dollars…” That’s the key to this trick, too: First, get a bunch of numbers. Here’s a file with 1,197 numbers in it. Now import or paste those numbers into a thread so that the numbers appear in the right place. If you need two matching numbers, just import it twice.
i have gone through the intersting discussions on this site. I am having a problem with foot notes in Adobe in design cs 4. when i pasted a fresh set of pages in a doc in- in design, the fn numbering starts from 1 all over again in the fresh set of pages. i am not able to insert foot notes manually, as it does not creat the space below the text. I am stuck for help
Hello! I already have automatic numbering set up (to change paragraph numbers automatically when paragraphs are moved within a document) but I would also like to have automatic lettering within the same document that is independent from the numbering. Example, paragraph 1 references Exhibit A, paragraph 2 references Exhibit B, so on and so forth. Currently using the above referenced method, the auto numbering lettering then follows as if the letters are a representation of the corresponding number (if that makes sense), ex: 1 B 3 C 5 D. How do I have the number sequencing independent from the letter sequence? Thank you in advance!
To include numbering prefixes from higher levels, enter text or click at the start of the Number box and choose Insert Number Placeholder and then select a Level option (for example, Level 1), or enter ^ and then the list level (for example, enter ^1). In a list with first levels numbered 1, 2, 3, and so on, and second levels numbered a, b, c, and so on, including the first-level prefix in the second level renders second-level numbers as 1a, 1b, 1c; 2a, 2b, 2c; 3a, 3b, 3c.
Does anybody have a way of formatting the phone numbers in Outlook 2003 so that they appear as xxx yyy zzzz that is no dashes, no parentheses? If I am going to synch to my PDA I want the numbers as short as possible and, to me, as readable as possible. Steve No. Masking of phone numbers is hard coded and based on your default dialing location. -- Russ Valentine [MVP-Outlook] "Steve E." wrote in message news:2dd601c48eb8$3ff4a1e0$a601280a@phx.gbl... > Does anybody have a way of formatting the phone numbers in > Outlook 2003 so that they appear as x...
"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.
Version numbers are used in practical terms by the consumer, or client, to identify or compare their copy of the software product against another copy, such as the newest version released by the developer. For the programmer or company, versioning is often used on a revision-by-revision basis, where individual parts of the software are compared and contrasted with newer or older revisions of those same parts, often in a collaborative version control system.
Basically, the only difference is that we now maintain a VBA.Collection, and this time we do make use of the UniqueKeyVariant parameter, using it as a key to locate the previously assigned number. If we don’t find it, we add to the VBA.Collection. The SQL to use those 2 functions remains identical. The downside is that if the query generates millions worth of rows, the memory may run out due to a large VBA.Collection. However, if a form is bound to that large dataset, it will likely have several other problems anyway so VBA.Collection should not be a problem for forms that loads a few hundred rows. The other downside is that VBA.Collection will persist indefinitely even long after the query has “finished.” Back to form example, you might need to remember to call the ResetRowNumber() function on a form’s close to ensure that you dispose of the VBA.Collection and free up the memory.

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='' sec='7']
An invoice number is simply a way to uniquely mark an invoice to help keep track of your business transactions. Consecutive or sequential invoice numbers help to ensure that each invoice is unique and each business transaction can be clearly and comprehensively organized and referenced – for accounting reasons as well as customer support. While a receipt is generally used as proof of payment and therefore documents a finalized sale, an invoice is a request for payment that includes more detailed payment or contact information in addition to pricing information for the goods or services rendered. Having a proper invoice numbering system helps you avoid duplicate payments that can amount to large losses for your company.
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.
Determine what kind of numbering you want to use for your document or book. For long documents, you can assign chapter numbers. Each document can be assigned only one chapter number. If you want to use different numbering within a document, you can define ranges of pages as sections; these sections can be numbered differently. For example, the first ten pages of a document (the front matter) might use Roman numerals, and the rest of the document might use Arabic numerals.
Numbering and Section options are available in the Pages Panel menu. These options allow you to define what page starts a section and how it should be numbered. A Current Page Number marker must be set on pages in order to use this feature. The Current Page Number is a special character inserted in a text frame on a page or master page (recommended) where the page number will appear, by selecting Type>Insert Special Character>Markers>Current Page Number.
The first number in this identifier is the date, followed by the customer number, and the unique sequence number. The last number is important if you have multiple invoices for the same customer on the same date – in that case, the next invoice would be numbered 05232017-4602-01. The date format can be selected from a variety of options as well. The example above uses the DDMMYYYY format, but alternate options include MMDDYYYY, DDMMYY, YYYYDDMM, or YYDDMM, among others.
To enter specific sequential number codes, such as purchase order numbers, you can use the ROW function together with the TEXT function. For example, to start a numbered list by using 000-001, you enter the formula =TEXT(ROW(A1),"000-000") in the first cell of the range that you want to number, and then drag the fill handle to the end of the range.
You would need to use Photoshop scripting actions can not do what you want to do. You could print them on roll paper with a script like my paste image roll or build that process into your script. Create large documents with many sequenced tickets laided out in them. The steps are the same steps yod would use in an action however you can use locic to update the sequence number in the setial text layer and position the tickets location.  You need to code in one of three supported scripting language. Javascript is the best choice. you fo not meed to have a dialog like pasteimagerollm Rou most likely want to have a ticket template file that your scrip opens and loop update its serial and paste mintp pace into your print document.  You can look at my pastimageroll script to see how to tile you ticket image into a document.
All I want to know is, how do you link fields, like {SEQ}, to a style – so that if I select/apply style “Figure Caption” (my style, I also have “Table Caption”), I get not just the attributes of the style (what it looks like, where it is on the page etc.) but I get a chapter (or section) number + a sequence number added, (e.g. “2-3”). I know about STYLEREF and SEQ Figure # and/or calling a section number (if required) – but I can’t find out how to take the simple and to me obvious step to have sequential numbering (prefixed with either “Figure” or “Table”) attached to my Figure Caption style. It all seems to be a two-step process: (i) select the style, (ii) select the numbering. I want to do both at style level. I want to see/get (e.g.) “Figure 2-3: Linking figure numbering to styles” just by applying my “Figure Caption” style to my figure caption text “Linking figure numbering to styles”. Please, only tell me how to do that, how to link chapter/sequence numbering via a style – i.e. in just one step – applying the style.
An InDesign document can only have one chapter, and these chapters are typically combined in an InDesign book. To insert a chapter number, create a text frame where you want the chapter number to appear on either a document or master page. Click on the "Type" menu, then "Text Variables," "Insert Text Variable" and then "Chapter Number." Update the chapter number if necessary to keep your chapter numbers consecutive by clicking on "Numbering & Section Options" in the Layout menu.
To make the endnote numbering sequential page by page, here’s what to do: Find the first page that has a break-out box with an endnote. On that page only, cut-and-paste each text frame into a new or different document. Then cut-and-paste each text frame back onto the page in the order they will be read. That will get the endnote numbers in the right order. Do this for every page that has a break-out box, but leave all the other pages as they are. That’s the workaround!
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.
Having said that, it’s easy to convert footnotes to endnotes and vice versa in Word. Simply select a footnote or endnote, right-click, and choose Convert to Footnote/Endnote. To change ALL your footnotes to endnotes (or vice versa), select the References Tab at the top, click the bottom right corner of the footnotes section to open the Footnote and Endnote Dialog Box, click Convert, then click OK or Apply. Easy, right? And you can switch them back and forth as many times as you want.
An overwhelming majority of companies use designation-based part-numbering systems. A Design Management Procedure, for example, may be numbered as SOP 4.4-1. With the previous revision of the ISO 9001 standard, it meant that this document related to the element 4.4, design management. Well, it does not mean the same with the new ISO 9001 revision, simply because design management clause now has a different number: 7.3. What is the solution? The solution is simple: no part numbers, and no designators!
If you are still reading this then perhaps you are looking for a simple and reliable way to number a couple of lists in a Word document. If you read John's article then you have already been informed that field numbering is simple and robust. If you are like 9 out of 10 Word users in my office then anything more than 1. space space Blah, blah "enter" 2. space space Blah, blah ... defies simple! If that applies to you, then the "SeqField Numbering" Add-In presented later in this page is for you.
I am curently working on a larger projekt, where we have aprox. 4500 pcs.of furnituer designed in 4 different kind of families, generic, furnituer, furnituer systems and specialty equipment. We need to be able to asign every  pcs.of funituer a seqventual serial number, we have tried to do this using an extension with a funktion called element positionerning, but we have had no success with this tool, apparently it is taking up to much memory.

Next we will look at scenario 2. The variation here is that Apex wants to start each year with anew sequence of numbers. Also, they want to include the year when displaying this number. We still use a DMax, but we need to add criteria to determine the year. So Apex needs to have a field in their table that indicates the date. Generally, such inquiries will have a date/time stamp to indicate when received or the user will input the date and time. So we will assume there is a field in record called InquiryDate. We will also add an Integer field named Sequence. On the form we will add a control bound to Sequence, but set its Visible property to No. The line of code will look like this:
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:
I have done this twice now, getting flustered. The ticket part the person keeps has the correct sequential number on it, but the side that we keep has the same number on it for the whole page. What part am I missing, at first I did not uncheck the box, but this time I did but have the same number on the stub side that we keep with the person’s name, etc

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)
If the list you want is as simple as "1", "2", "3", you'll appreciate how easy it is to apply this type of numbering in legal documents. Simple numbered lists are different in Word 2000 than they were in Word 97. In Word 2000, the default for even the most basic list is multi-level. For example, if you number an item and press Enter and then press the TAB key, Word automatically formats this number as the second level in an outline numbered list format. Single and multi-level numbering are explained later in this chapter.
I have done this twice now, getting flustered. The ticket part the person keeps has the correct sequential number on it, but the side that we keep has the same number on it for the whole page. What part am I missing, at first I did not uncheck the box, but this time I did but have the same number on the stub side that we keep with the person’s name, etc
When you are ready to restart numbering, you can use the technique above, or you can place your cursor inside a numbered paragraph above, click the Format Painter (the paintbrush icon on the Home tab under Clipboard), then click on the line where you want to restart numbering. Using Format Painter this way solves several paragraph numbering problems (the number sequence, indents, and inter-paragraph spacing) simultaneously.

A multi-level list is a list that describes hierarchical relationships between the list paragraphs. These lists are also called outline lists because they resemble outlines. The list’s numbering scheme (as well as indentations) show rank as well as how items are subordinate to one another. You can tell where each paragraph fits in the list with respect to the paragraphs before and after it. You can include up to nine levels in a multi-level list.

2. Yes, The code should be entered using CodeBuilder. Where you enter it depends on how and when you want to trigger the generation of the next number. If you want to use a button, that works. And no, you don’t use 000 in the NZ() function. If you want to DISPLAY at least 3 digits with leading zeros, then you do that in the Format function. Note, though, you will need to change that when you hit 1000 POs. sequentially numbering in publisher