What is against a query with the following field?
[Suppose your number is in field part]
X: Format(Now();"yy") & "/" & Format([part];"000000")
Say you have 25 in part; X would give 02/000025
However, next year this would read as 03/000025. If you really want to have the text string added, make a new field, say Y. Use an update query where all empty Y would get the value Format(Now();"yy") & "/" & Format([part];"000000")
I have the feeling that something as this would be your solution. Although, I would only add to my table a field with the date [i.e. now()] in it and a string in the query to combine the year and the number, if that is what you want on paper. It is very simple to add a date field e.g. INPDAT with default value =now()
This is anyhow a wise decision as it will always show when the number was added to the database. The field INPDAT you can protect or hide in a form.
The query would contain:
Z: format([INPDAT];?yy?) & ?/? & format([part];?000000?)
This can also be a (calculated) field on your form or in your report.
It you require more or fewer digits amend the six zeros.
It may be possible that you have to replace ; [semi colon] with , [comma]
Good luck.