When entering an account number in the Banking > Spend Money or Banking > Receive Money forms, the second character typed can appear at a further point in the account number string if typed too quickly.
This problem occurs regardless of the state of the "Use Easy-Fill When Selecting From a List" option.
I've verified this to be the case by using a keylogger on the machine to ensure keystrokes were being entered in the correct order. I've also confirmed that if an account code is copied and pasted from another source that it always appears correctly, so it seems to be exclusively a problem with manually entering a partial or full account number.
What appears to be happening is that after the first keystroke is entered, the account numbers load and lock the interface during loading. If the user is still entering the account number while the list is loading, the second character seems to be stored and kept whilst subsequent characters are entered as normal into the field. Once the list has loaded, the second character entered is then inserted into the string at whichever position is now last in the string.
The result of this is that a user entering "12345" quickly in this field can end up with an account number looking like any of: "12345", "13245", "13425", or "13452". The "1", "3", "4", and "5" are always in the correct order, it's just that the "2" is changing location in the string.
My users most commonly just enter three digits, e.g. "124" in order to have the account number list display all the "1-24xx" numbers, but this bug causes that to appear in the field as "1-42" and as we have no account numbers beginning with "1-42xx", the list of available account numbers is empty.
So far the solution we've been given from MYOB support is "have your users work slower", but that's a very non-ideal solution. It means my users have to not only slow down but also double check every account number they enter in case the digits have been swapped in such a way that the incorrect account number exists and items get coded to the wrong account.
"Bug - entering digits too quickly in the "Acct No." field causes the second character to be misplaced in the string"
... View more