I am getting the above error in my multi-user database when someone tries to add a new record to the database.
My database is set up as a split database with 2 tables in the backend, one for the file/project and another with the action currently taking place with that file. Data is entered through a form with a subform on the front end. The problem occurs when trying to enter a new record on the subform:
Record/Account: (info on form, from table 1)
George Jones at 1234 Anywhere St Nowhere Id
Action: (info on subform, from table 2)
1: Set up time for lawn mowing.
2: Wants garden weeded on Saturday
Both tables have autonumbers as the primary key. Table 2 has a field that is referenced to table 1 using the unique autonumber.
I believe it is a problem with the autonumber field in the second table, such as when a number is held in "limbo" because a record hasnt been really entered, but it locks everyone else from getting the next autonumber.
What can I do to correct this?
Please and thank you!
Aim for the moon, for even if we miss, we are still among the stars.
My database is set up as a split database with 2 tables in the backend, one for the file/project and another with the action currently taking place with that file. Data is entered through a form with a subform on the front end. The problem occurs when trying to enter a new record on the subform:
Record/Account: (info on form, from table 1)
George Jones at 1234 Anywhere St Nowhere Id
Action: (info on subform, from table 2)
1: Set up time for lawn mowing.
2: Wants garden weeded on Saturday
Both tables have autonumbers as the primary key. Table 2 has a field that is referenced to table 1 using the unique autonumber.
I believe it is a problem with the autonumber field in the second table, such as when a number is held in "limbo" because a record hasnt been really entered, but it locks everyone else from getting the next autonumber.
What can I do to correct this?
Please and thank you!
Aim for the moon, for even if we miss, we are still among the stars.