This can happen when there are multiple records that start with the same key values. I would look to see if you have multiple instances of the same check number, same bank code during the period you are working on.

This can happen when there are multiple records that start with the same key values. I would look to see if you have multiple instances of the same check number, same bank code during the period you are working on.

Thank you, turned out to be a blank record in the GL_Bank table.

We've seen that cause problems with BR too (most especially with rebuild sort files for BR). 

Sage really needs to add a check for blank rows in that table, to prevent errors / data corruption.  It would be nice if the blank rows could be prevented (AFAIK the cause is unknown), but when it happens, the program should still work properly.

Thanks!