Primary key auto populate in form

[kets0985]

Hello,

I have a form which I use to record the daily activities. To track each activity time, I have used timer in the form. However, when I open a form, the record_ID which is the primary key, always autopopulate. Even when I click cancel or submit, the field takes the autonumber without been given a command for new record.

In the form load event, I have a code as "DoCmd.GoToRecord , , acNewRec".

What should I do, so the record_ID field should not take autonumber untill I give new record command.

The main issue is, due to the record_ID error, the record which are there in the datasheet table does not reflect in the form when clicked on them. These records are kept on hold and when needed they can be reworked on once clicked.

[ranman256]

If you start a new record , you get a new autonum. (blame microsoft)
BUT, if you start entry in an 'entry table' (not connected to the main data)
then click save, that will fire an append query to add the record. No wasted autonum.
and not subform errors due to new autonum.

[Missinglinq]

...Even when I click cancel or submit, the field takes the autonumber without been given a command for new record....

...In the form load event, I have a code as "DoCmd.GoToRecord , , acNewRec"...

But you have given the command for a New Record! That's what the above, in red, is telling Access to do!

That aside, it shouldn't matter if the Autonumber is wasted! Autonumbers should not be used for anything other than the Primary Keys! Things like serial numbers, account numbers, employee numbers should be something other than Autonumbers.

Linq ;0)>

[June7]

The acNewRec parameter sets focus to new record row, however, AFAIK new record is not actually initiated until some data is input to a field, either by user or by code. This initiation of record will trigger generation of autonumber. If record is then canceled and not committed to table, the autonumber is still 'used up' but no record is associated. This is the nature of autonumber field in Access.

It is possible to programmatically 'recover' lost autonumbers but this is tricky and seldom justified.