Cannot update data: While you were editing, another user may

Problem

You see this error when attempting to save data in your application:

Cannot update data: While you were editing, another user may have deleted the same record(s) you were modifying.

This message is normally displayed when a user attempts to update a record that was edited and saved by another user. This is a normal outcome of the concurrency handling mechanism in your applications. No solution is required in this case because this is a normal outcome of the concurrency handling mechanism in applications.

However, this error message can also occur when your database schema has changed and your application has not been updated to reflect the schema changes. Iron Speed Designer doesn’t know you changed the database schema, so it continues updating your application based on the old schema.

Another user updated the record

No solution is required in this case because this is a normal outcome of the concurrency handling mechanism in your applications.

Database schema has changed and does not match your application

Step 1: In Iron Speed Designer, scan your database for changes (Databases, Scan All Tables for Changes).

Step 2: If changes are identified, then accept the changes to synchronize Iron Speed Designer and your application with the database schema (Databases, Accept All Changes).

Step 3: Rebuild your entire application (Build, Rebuild All). This will update your application to match the database schema changes.

Recursive relationships exist in your database schema, triggers or stored procedures

This error may be caused by a recursive relationship in your database schema. Database triggers and stored procedures may make recursive calls that cause this problem. For example, a trigger may be updating a row that has already been updated.

Remove the recursive relationships in your database and possibly (re)define them in Iron Speed Designer (in the Databases tab).