To me, this is a document control db, where the successive document identifier that is created in a series gets the next number in that series. IMO, you do this on the final stage, assuming there are stages. In other words, if you allow partial saves, you don't save the document identifier data until all required info is provided. If stages are not applicable, you create the identifier when the record is committed (i.e during the form BeforeUpdate event) so that when the document record is created, that's when you reveal the document identifier. IMO this is the required methodology in a multi user document/record db.
In any event, the next identifier number is the DMax (or Max) of the number field WHERE the other parts match the rest of the document identifier parts. So the document identifier should not be a single field, but a compilation of however many fields would make up the document identifier string.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.