Wednesday, November 20, 2019

Dexterity change next requires action

Once again doing battle with Dex ranges.

Kept getting the dreaded "error get/change table...a record was already locked" during a loop on a table with a range where clause.  After the change next on the second record in the range I got the error when attempting to read the third record with a subsequent change next in the loop.

The problem was I did nothing with the second record (by design).  Apparently in every change statement the table record must be saved or removed.

When I added a save command for every record in the loop the error went away.

No comments:

Post a Comment