Concurrent Data Entry in Forms
We created a form using for staff to register for daily available slots. Unfortunately, when we tested the form, we did not test it for concurrent data entry. And lo and behold, when we opened the reg...
Forum Discussion
Well, the root of the problem is the difference between table states when the form is loaded and when it's saved, I think? Basically more than one user opening a registration form and sitting on that page, after which there is no subsequent check against availability.
So you could narrow your problem window quite a bit by performing another check after the registration form is filled out. To avoid too much UI aggravation, maybe do something similar to a multi-stage online payment - at the bottom of the registration form, rather than a SUBMIT or REGISTER button, implement a PROCEED button (or even call it CHECK AVAILABILITY) that goes to another form page displaying/confirming the information they've entered, with the REGISTER button on that page - or instead of the REGISTER button, display a 'no more availability' message if someone else has already registered that slot.
So you could narrow your problem window quite a bit by performing another check after the registration form is filled out. To avoid too much UI aggravation, maybe do something similar to a multi-stage online payment - at the bottom of the registration form, rather than a SUBMIT or REGISTER button, implement a PROCEED button (or even call it CHECK AVAILABILITY) that goes to another form page displaying/confirming the information they've entered, with the REGISTER button on that page - or instead of the REGISTER button, display a 'no more availability' message if someone else has already registered that slot.
- Thank you. This I think would be the doable solution for the future unless I can figure out Dan's solution above. I will try and let you know.