It might also be that the browse can’t locate the added record because the primary key is a MSSQL IDENTITY, and you haven’t retrieved the record by the primary key. If you know the primary key value you could try an …
…after the TakeCompleted embed of the update form. This will reget the Clarion file buffer for the new record.
Last night we got an ABC error returning a FILEERROR() from another window which was far more meaningful. It was SQL 22001 naming the table and indicating a column that was too small. So it was then easy to locate that in the new database. A column that should be 15 characters was set at only 5. Once that was put right we haven’t seen the problem again yet.
The column though was just data, not involved in any key. The effect though was that records were not saved at all, so that might account for the Record Retrieval Error message. Obviously we will need to keep an eye out and if another cause turns up I will report it back to this thread.