Append Query adds to table, but assigns random autonumber instead of next consecutive number in "append to" table
I am working in an existing Access 2013 database which is designed to copy the budget items from a budget table and append them back in with the next fiscal year. Once the append query is run, the data fields append ok accept for the auto-number key field. Is there any code to add to the SQL to have the records append and begin the next consecutive number available in the "append to" table.
The SQL Viewer reads:
The SQL Viewer reads:
INSERT INTO tblBudget ( [Sub Acct Numer], Description, [Module], Task, [Qty Req], [Unit Cost], [Cost Center], [Account Number], Fund, Project, DateEntered, [Budg Year] )
SELECT tblBudget.[Sub Acct Numer], tblBudget.Description, tblBudget.Module, tblBudget.Task, tblBudget.[Qty Req], tblBudget.[Unit Cost], tblBudget.[Cost Center], tblBudget.[Account Number], tblBudget.Fund, tblBudget.Project, Date() AS DateEntered, [Budg Year]+1 AS [New Budget Year]
FROM tblBudget
WHERE (((tblBudget.[Budg Year])=16))
ORDER BY tblBudget.[Account Number], tblBudget.Fund, tblBudget.Project;ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
No one recommended a GUID. They cause other issues and so I would not recommend them unless you actually need them and those cases are extremely rare. This isn't one of them.
ASKER
The creator of the database used auto numbers to identify individual line items in a budget. The gap resulted from deleted records. compiling cleaned up the database and accepting a gap due to deleted records will be acceptable. Thank you team!
Many developers in this situation will create another column as a 'business key' that will be the unique identifier exposed to users, and the app can contain whatever funky logic is used to create that number. Especially for situations where there are mixed letters and numbers 2016A1, or if part of the value has an exact meaning like 2016=the year.