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.

Dynamics GP Payables Apply malfunction

We had a payables payment in GP go bad on us.  When it was put in as a Manual Payment some documents were applied.  This was a partial application and amounts were still outstanding.

However some of these applied documents got disconnected and were left behind.  They showed on the Apply Payables Documents window as being selected with the manual payment, but we could not make any further selections.  When we tried GP kicked the following error:

"This invoice already is partially applied to this credit document.  You cannot apply this document until the other apply amount is posted."

hmmmm....

Found some references to the GP apply tables.  Specifically PM10201, the Payment Apply To Work File, and PM20100, the Apply To OPEN OPEN Temporary File.

For some reason these tables have a LOT of junk in them.  I'm not ever sure how to start cleaning them out.

But for purposes of resolving the current problem I found a bad payment referenced in PM10201 for the invoices that were showing as applied.  I deleted those records and removed the related records from PM20100.  When I ran CheckLinks the apply documents moved to history and all appears back to normal.

Some day there will be a reckoning with those two tables.  It's just a mess.