Hi! I have FE and BE structure under Access 2003. Just want to know under this environment, can I use 3 separated PC front end stored at each to input data to the same BE table at the same time. Provided that, for each new input, it involved 2 tables with one new Master and one or more than one transactions relationship between the 2 tables. If not, is there any suggestion for that?? Thanks a lot!!
Multi users access the same table
- Thread starter rickyfong
- Start date
- Local time
- Today, 10:58
- Joined
- Sep 12, 2006
- Messages
- 16,001
yes. there is no problem with multiple users accessing the data at the same time. that is the way access is designed.
rarely you might find that 2 users try to change the same data at the same time. there are two basic strategies for this.
1. record locking. the first user "locks" the record so no other user can read it - so he can make his update safely.
2. no record locking. Let both users see the record at the same time. At the time of saving the change any user checks to see if the record changed since he started to edit the reocrd. if it has, he is warned, and needs to start over. This is based on the fact that any number of users just looking at a record is never an issue. the only issue is two users trying to change the same record.
this second method is caused "optimistic locking", and is the default in access. the vast majority of the time, this form of locking is adequate. you might need to implement a real locking strategy in very few circumstances. Assume you do not need to change the default.
rarely you might find that 2 users try to change the same data at the same time. there are two basic strategies for this.
1. record locking. the first user "locks" the record so no other user can read it - so he can make his update safely.
2. no record locking. Let both users see the record at the same time. At the time of saving the change any user checks to see if the record changed since he started to edit the reocrd. if it has, he is warned, and needs to start over. This is based on the fact that any number of users just looking at a record is never an issue. the only issue is two users trying to change the same record.
this second method is caused "optimistic locking", and is the default in access. the vast majority of the time, this form of locking is adequate. you might need to implement a real locking strategy in very few circumstances. Assume you do not need to change the default.
In case, 2 users are goint to input 2 different new records to the same table. Should the table locked mechanism worked as point 1, or they are freely to insert new records without any constaint!!. In case not, is that the first locked user can insert a new record, and the second would get a warning message and only can insert new record until the first one lock out from the table!!?? Thanks!
DavidAtWork
Registered User.
- Local time
- Today, 10:58
- Joined
- Oct 25, 2011
- Messages
- 699
inserting new records should not be a problem if the PK is an autonumber, if the PK is some sort of calculated value, then this may cause an issue if multiple users are trying to add new records that might result in the same PK being generated.
David
David
- Local time
- Today, 10:58
- Joined
- Sep 12, 2006
- Messages
- 16,001
leave the default setting unchanged, until you find a specific reason to do something different.
as david just said - a problem may occur depending on how you generate a record id. (or a sequential reference, say) but that is still more of a design/implementation issue/problem, rather than a record locking problem.
as david just said - a problem may occur depending on how you generate a record id. (or a sequential reference, say) but that is still more of a design/implementation issue/problem, rather than a record locking problem.
