5. Working with QBF Operations : QBF Update Operation : How Updates Are Saved : Transaction Deadlock in Update Mode
 
Share this page                  
Transaction Deadlock in Update Mode
Deadlocks can occur at two times during the QBF Update function. First, a deadlock can occur while you are editing rows of retrieved data. QBF displays the following error message:
Deadlock detected, your transaction has been aborted.
This means that you cannot update any more rows retrieved by your last query. However, any changes you have made before this point are still stored in the buffer. In this situation, QBF displays the following message:
Do you wish to save the changes made thus far?
Answering y (yes) is equivalent to selecting the Save operation. As QBF writes your changes into the database, it displays the message:
Saving Changes
The second type of deadlock can occur during the Save operation while your changes are being written from the temporary storage buffer to the database. In this case, QBF displays the message:
Deadlock detected, your transaction has been aborted.
In this situation, all changes made since the last Save operation are lost and you must begin again with a clear form.