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)
There are also other problems – for one thing, it’s not a very generic solution. You must customize several parts to work for different queries. If the set of tables used in the outermost FROM clause are different, to be the innermost FROM clause, you have to adjust the WHERE clause to reference the correct primary key (or some combination thereof). Then you have to also keep the ORDER BY in sync. That’s a lot of tweaks if you want to use it for different queries. That is why this is the last method listed here but it is one possible solution.
Both the Collection Point ID and Artifact ID fields are bound properly and display those exact names in the property sheet under both control source and name. On the save button I have on the form, when I click on the event tab and the on click option I have event procedure and I click the […] option to open up the code builder and this is what I currently have:
Sequential numbers can be printed almost anywhere on a sheet or form and can be positioned horizontally or vertically. Numbers can also be repeated in another position on the form. When developing your artwork, consider putting a box for numbering, making it easier for your customers or employees to find and reference a specific job or transaction. You may also differentiate your number by color. Most printers allow a choice of colors, typically black or red, to make your number stand out. Start your sequencing at any point you like, to pick up where you left off on your last print order.