autonumbering of a field with several categories

hi guys, im new in microsoft access and i got stuck with some problems.
i created a table called inventory transaction and the fields are 'transaction No (PK)' "transaction reason', 'transaction date','items', etc.
Here's my areas of concern.
1. transaction code consist of several categories such as 'production' and 'purchases', if i select "production" as my transaction reason, transaction No will start with 1. and if i select "purchases", transaction no. should also starts with 1. in short Transaction No sequence should be separate for the 2 categories

tnx a lot

re: autonumbering of a field with several categories

In these circumstances it is not AutoNumbering you need. It's explicit, controlled setting of the number instead.

We can help with this but could you first explain where Transaction Code fits in? You gave a list of fields, then proceeded to explain your problem with reference to a field you hadn't included. This muddies the waters rather and I don't want to proceed with a fuzzy understanding of your problem as that way leads to problems and confusions.

This will work much better if you can post the meta-data (info about the layout / structure) of the table in the same way as I use in my example. Click on the Reply button and you will have access to all the codes I've used. PK & FK stand for Primary Key & Foreign Key respectively. Please don't use any TABs in your formatted layout as this will not display correctly - Spaces only for layout.
Table Name=[tblStudent]

re: autonumbering of a field with several categories

tnx neo, these are some info abt my proj.
Table=[Inventory Transaction]
I have 2 transaction reasons which are "production" and "puchases". i want each of them to have separate transaction code numbering/sort

tnx

re: autonumbering of a field with several categories

So. [Transaction No] doesn't exist at all. Please be more careful in future.

As for your question, the [Transaction Code] field needs to be changed to a Number / Long Integer field and something else added into your PK. A PK MUST be unique. You would probably want to add the [Transaction Reason] into the PK such as :
The new setting for each record would be determined in the code of your form as (assuming TextBox controls of txtTranCode & txtTranCode) :
I hope this clarifies things a bit for you.