Auto-Numbering

What error message are you getting?
What code are you using to add a record to the database?

Remember you should not include the name of the Identity field in you code when adding the new record.

Cheers,
Andrew

Firstly, you don't need to open a recordset if you're not going to be displaying it on the page.

Secondly, if you're Identity column is [Test1], then you shouldn't be addding anything to that column as the database will do it for you. It therefore, should not be in your code.

So, code to create a new record:

dim strSQL as string
strSQL = "INSERT INTO [MyTable] ([Field1],[Field2],[Field3]) VALUES ('Value1','Value2','Value3')
myConn.execute(strSQL)

Note, field1, field2 and field3 are not identity fields.  The identity field is called something else, that you don't need to mention in your code. Value1, value2 and value3 are surrounded by quotes when strings, otherwise they should be left off for numerical fields.

myConn is a connection that you have already established in your code.

Cheers,
Andrew

There will (and should) be gaps in the autonumber if that happens.

Try to think of Autonumber (primary key) fields' purpose, purely to uniquely identify records and to be used in relationships between tables. 

They should rarely (if ever) be seen by anyone except the database developer.

For simplicity, take for example a table of customers and a table of Purchases. 

Customer (Ralph) with an ID (Autonumber) of 10 has been part of a dozen or so purchases.  Therefore Ralph's Customer ID (10) is in the Purchases table 10 times, alongside the relevant product.

Now Ralph leaves. His record gets deleted from the customers table.  A new customer (Bill) comes along and gets Ralphs old ID of 10, which is now free... Whoops! Ralph has automatically made 10 puchases since he is linked to those 10 puchases in the Purchases table.

This is why the autonumber or identity field numbers are not recycled.

And if everyone understands that they should not be used or shown publicly for identifcation then there wouldn't be any problems.

Hope this helps,
Andrew

That goes without saying. 

Was the easiest way to provide an example.

In the above situation, the customers record shouldn't be deleted in the first place.