Spelthorne1
Registered User.
- Local time
- Today, 01:54
- Joined
- Feb 17, 2004
- Messages
- 20
After searching high and low i have still come to no answer - certain threads look promising but none have the exact solutions.
I have a db set up with a table WC16Feb that holds the core of the data inputted.
At the moment there are only 2 users, but this is soon to increase. There is record locking on the edited record but database locks at a minimum 5 times a day when one user tries to add a new record. -this only happens with this user!
The only way to allow them back in is for the other user to close their form and then go back in again.
We have tried -
[1]
In the table the [ID Val] increments by one using the autonumber.
-db locks
[2]
The oncurrent() method of :
If newrecord then
[ID Val] = DMax("[ID val]", "WC16FEb") + 1
end if
(after disableing the autonumber in the WC16Feb table)
This last method worked but the users kept on adding several new records by leaving the mouse pressed for too long on the new record button.
There doesnt seem to be a happy medium - either db locking or eronerous data being inputted.
Does any one have any other suggestions which may solve this problem?
I have a db set up with a table WC16Feb that holds the core of the data inputted.
At the moment there are only 2 users, but this is soon to increase. There is record locking on the edited record but database locks at a minimum 5 times a day when one user tries to add a new record. -this only happens with this user!
The only way to allow them back in is for the other user to close their form and then go back in again.
We have tried -
[1]
In the table the [ID Val] increments by one using the autonumber.
-db locks
[2]
The oncurrent() method of :
If newrecord then
[ID Val] = DMax("[ID val]", "WC16FEb") + 1
end if
(after disableing the autonumber in the WC16Feb table)
This last method worked but the users kept on adding several new records by leaving the mouse pressed for too long on the new record button.
There doesnt seem to be a happy medium - either db locking or eronerous data being inputted.
Does any one have any other suggestions which may solve this problem?
