Auto Numbering Issue

[Buzz619]

Hi members,

I'm having some difficulties on a task related to Auto Numbering.

For Example:- Whenever i get to the new line, a new number should be populated. But the number can be repeated as per requirement till i put next number. then all previous sequence number can not be used.

like:
S.No.
A-001
A-002


A-003
A-003
A-003
A-004
A-005
A-005
A-006


Is there any way to make this happen?

[Minty]

What you have described is not and as far as I can tell cannot be an Autonumber.
Autonumbers are identity fields and by definition they are unique.

Surely a Serial number (as that's what it appears to be) should also be unique?

If it's a batch number then that is a different thing, but still not easy to automate, as what determines when it changes?
From your description is seem completely arbitrary?

[Buzz619]

What you have described is not and as far as I can tell cannot be an Autonumber.
Autonumbers are identity fields and by definition they are unique.

Surely a Serial number (as that's what it appears to be) should also be unique?

If it's a batch number then that is a different thing, but still not easy to automate, as what determines when it changes?
From your description is seem completely arbitrary?

Ok,

so please tell me the way for this situation:

I need to enter a purchase invoice data. the purchase invoice have multiple unique items. so all items need to be entered into separate rows.
so how can i give this invoice a unique & auto generated batch number?

[Minty]

Ah ha - now we have more of the picture. This is a very common data structure, typically an Order and Order lines. In your case a Purchase order and Purchase order lines.
So you have two tables one is your Purchase Order Header, and the other is your PO Line Data

POHeader will contain who the order is placed against , when, perhaps who raised it etc, and contains your PO Number - This can be an Autonumber for simplicity, as long as you don't mind that it might have gaps in the sequence. But it will be unique.

POLineData will have the PO Number as a Foreign Key, and a POLineID as the autonumber.
This line contains your Part No, the qty ordered, and the item and or line price, as well as the two important numbering fields above.

This is just the basics - you might need other fields for your business requirements.

[Buzz619]

Ah ha - now we have more of the picture. This is a very common data structure, typically an Order and Order lines. In your case a Purchase order and Purchase order lines.
So you have two tables one is your Purchase Order Header, and the other is your PO Line Data

POHeader will contain who the order is placed against , when, perhaps who raised it etc, and contains your PO Number - This can be an Autonumber for simplicity, as long as you don't mind that it might have gaps in the sequence. But it will be unique.

POLineData will have the PO Number as a Foreign Key, and a POLineID as the autonumber.
This line contains your Part No, the qty ordered, and the item and or line price, as well as the two important numbering fields above.

This is just the basics - you might need other fields for your business requirements.

Thanks for help!!