Does anyone have a solution for the following.
We have an action-table in which rows “live” from anywhere from a couple of minutes to hours. These rows have buttons, one of the buttons is active when certain conditions are met - upon pushing the button a field in the row is updated and causes the button to be inactive. Until some other conditions are met, the button may not be used again.
There are anywhere from 2 to 10 people active in this doc and everyone is allowed to push this particular button. This works mostly fine, but sometimes the document does not update instantly or all users, and in those situations it happens after user 1 pushes the button and updates the row, user 2 is still seeing the original instance of that row with an active button and pushes it again.
One of the button actions is to write a record to another table and in the situation as described this happens twice and that is not very desirable. Since we work with time codes, it is not a simple matter of checking on duplicates in the secondary table.
Is there a quick fix to prevent this, or do I have to write routines to somehow double check in the secondary table if the action has already been taken. Since all the actions take place in the doc on the phone/tablet I can’t think of a way of checking if the user has the latest instance of the doc in his tablet before doing the write to the 2nd table.