I need a way for the priority level to automatically adjust when I add or change an item with a new priority level. I might have 6 tasks, each will have a different priority. If I add one and set it to 1, the others need to increment + by one digit. Adding one to the above the highest would see no change in the others. Adding one in the middle would spread the rest apart (e.g. I have a 3, I put a new record and put it at 3, the old 3 becomes 4, and so on (everything below it would increment one digit).
Please guide me that i have Purchase order in one excel sheet i.e 200 pages i want to know any formula for footer page number which should be permanent Means i have 1st purchase order of 3 pages, 2nd purchase order for 4 pages and 3rd purchase order for 2 pages. each purchase order has different Serial number but all in one excel sheet i.e sheet1. i inserted footer page no of ? which generate 1 of 9, 2 of 9 etc. Please guide i want to segerate the footer page number for 1st page order 1 of 3, 2 of 3 and 3 of 3. 2nd purchase order should have footer page number 1 of 4, 2 of 4 etc and hence for 3rd purchase order. looking forward for your guidance
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.

Hello, can anyone help me with making serial numbers in this way: When I purchase 10 chairs, I want to monitor all of it by having serial numbers each of those 10 and those 10 numbers should have the prefix “CHR-” if they are chairs. “TBL” if tables, the codes are associated with the item category. BTW, items have categories predefined by beforehand on the items by relationships. So when I will want to monitor these 10 chairs, I will only have to click the “generate control numbers” button and each of those purchased items get their own control numbers.
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.

The blog is pretty much step by step. Where it may not be that specific is, because, these are decisions the developer needs to make. For example, where to put the DMax expression is a matter of your workflow so I can’t tell you where to put it. I’ve given tips in the blog to help you decide. If you are having issues, then please give me more info about your application and I can suggest things.


What I actually want to do, is say I go out and shoot 100 images, and I want to number them 1 to 100 so I can send them to the client and they can respond back with the number of the images they like, for instance, "Give me 21, 45, 68, and 77" as an example.  Is there a way to batch process a folder of images to sequentially number them individually, or do I have to painstakingly number them one at a time?
Ah, that’s the con – this works beautifully when you are in fact exporting data but when you are viewing the query’s output in a datasheet or a form, as you scroll around, Access will be re-evaluating the rows, including a call to the RowNumber(). But when it repeatedly calls RowNumber(), of course it keeps incrementing blindly, without any regards to whether a number was already generated for that row.
If you use the Form Wizard, controls will be named with the field name the control is bound to. But that name can be changed. This trips up a lot of people because my code samples use a naming convention that is not what is automatically generated. So you just need to make sure you use the correct name for the object. The name is shown in the Name property on the Other tab (Not the Caption property). To determine what field in your table the control is bound to check the ControlSource property. It should be bound to the PONum field.
English Spanish Dictionary | English Italian Dictionary | English German Dictionary | English Portuguese Dictionary | English Russian Dictionary | Medical dictionary English French | Computer dictionary English French | Computer dictionary English Spanish | Business dictionary English French | English Arabic Dictionary | English Hebrew Dictionary | English Dutch Dictionary | English Polish Dictionary
Search sequential numbering and thousands of other words in English Cobuild dictionary from Reverso. You can complete the definition of sequential numbering given by the English Cobuild dictionary with other English dictionaries : Wikipedia, Lexilogos, Oxford, Cambridge, Chambers Harrap, Wordreference, Collins Lexibase dictionaries, Merriam Webster ...

Thanks for the quick reply, I think I’m a little confused by the Display aspect of this. Artifact ID is a primary key to the table I am working in and I need it to have a unique identifier that other people can search for. The previously adopted naming convention for this ID is that which I mentioned before, Collection Point ID plus a period and then a sequential number restarting at each new Collection Point ID i.e 2-1050.1, 2-1050.2, 2-1060.1 and so on. So I think I actually need to save this in the Artifact ID field. I realize this might be slightly redundant but I’m not sure how the display would work as far as searching for specific Artifact IDs in the future.
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.
OK I found the ControlSource property but it is on the Job No text box, do I enter the code there or am I entering my code on the button I created to save and get new number? If I put it behind the button, when I open the form it goes to the first record so I go to the last record and hit save get new number button and it gives me the number 1……Is it because when I open the form it goes to the first record and not a new record????
Ah, that’s the con – this works beautifully when you are in fact exporting data but when you are viewing the query’s output in a datasheet or a form, as you scroll around, Access will be re-evaluating the rows, including a call to the RowNumber(). But when it repeatedly calls RowNumber(), of course it keeps incrementing blindly, without any regards to whether a number was already generated for that row.
Thanks for the quick reply, I think I’m a little confused by the Display aspect of this. Artifact ID is a primary key to the table I am working in and I need it to have a unique identifier that other people can search for. The previously adopted naming convention for this ID is that which I mentioned before, Collection Point ID plus a period and then a sequential number restarting at each new Collection Point ID i.e 2-1050.1, 2-1050.2, 2-1060.1 and so on. So I think I actually need to save this in the Artifact ID field. I realize this might be slightly redundant but I’m not sure how the display would work as far as searching for specific Artifact IDs in the future.
To recap, you use a DMax function to return the highest number in the Sequence and increment it by 1. You assign the incremented number to a control on your form and then immediately save the record. If your identifier includes additional information from the record, you use an expression that concatenates that information with the sequence number to display the full identifier.
This is how I see it. A person (passenger) makes a reservation. If the person has never made a reservation before, then they are added to the passenger table, But it really makes no sense to assign a sequential number to the passenger. Otherwise, an entry, just needs to be made in the reservations table. The Reservation needs to include the specific train (number and date so there should be a table for train schedules so all you need is a foreign key), the passenger and date of travel. Here I can understand wanting a sequential number to show passengers booked in a day.
What I actually want to do, is say I go out and shoot 100 images, and I want to number them 1 to 100 so I can send them to the client and they can respond back with the number of the images they like, for instance, "Give me 21, 45, 68, and 77" as an example.  Is there a way to batch process a folder of images to sequentially number them individually, or do I have to painstakingly number them one at a time?
This actually has nothing to do with linking or unlinking of headers or footers but with restarting numbering (which can be done without unlinking). In any section where there is a jump in the numbering, go to Insert | Header & Footer | Page Number | Format Page Numbers.... In the Page Number Format dialog, change the "Page numbering" setting from "Start at" to "Continue from previous section."
Ah, that’s the con – this works beautifully when you are in fact exporting data but when you are viewing the query’s output in a datasheet or a form, as you scroll around, Access will be re-evaluating the rows, including a call to the RowNumber(). But when it repeatedly calls RowNumber(), of course it keeps incrementing blindly, without any regards to whether a number was already generated for that row.
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.
Let’s look at why we have this setup. It seems strange to put a ResetRowNumber() call in a WHERE clause, doesn’t it? However, the WHERE clause is actually resolved prior to the SELECT clause. (For those who wants to geek out on SQL internals, Itzik Ben-Gan, a SQL Server MVP has a great post that outlines the logical query processing. Though this is specific to SQL Server, the Access database engine as well the majority of RBMS engines generally follow the same outline). This gives us a convenient point to ensure that the module level variable lngRowNumber is always correctly reset at the right time (e.g. before we start returning records from a query).

So if you encountered this problem, then you didn’t follow the instructions completely (which is OK) and appear to be automatically generating the number whenever the record is accessed. If that’s the case, then you are risking duplication because you are not saving the generated number immediately. Rather then try to test if a number already exists as you seem to be doing, you should not automatically generate the number, but trigger the generation from some action in the form.
OK I found the ControlSource property but it is on the Job No text box, do I enter the code there or am I entering my code on the button I created to save and get new number? If I put it behind the button, when I open the form it goes to the first record so I go to the last record and hit save get new number button and it gives me the number 1……Is it because when I open the form it goes to the first record and not a new record????

This requires no pre-knowledge of a primary key and only assumes that when you load the form initially, it is already sorted. Any records newly inserted will get the next bigger number. However, if you requery and it causes the newly inserted rows to be re-sorted, they will be now given a new number that relates to their actual position within the set, which can be either good or bad, depending on your specific requirements.


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.
I've read a few posts which I thought would cover this but haven't been able to make anything work. Basically I have a piling layout with 350 piles on it which have to be numbered. I have done this by block and attribute and can edit the number to each one individually. However, If one pile gets added I have to renumber the subsequent ones to have a logical sequence for the builder. Not too much of a problem if is near the end of the numbers, but a real pain if it is near the top. The piles are not on  a regular grid either so I can't just select and move the numbers en bloc. Is there any way to speed this up in Acad LT 2013? It would save me hours of editing time.
×