after setting up a validation mask for tender types, our client cannot use the number 3 in any tender amount. yes, that's the amount, not the account.
anyone seen anything like this before?
- posted
16 years ago
odd tender behavior
Loading thread data ...
- Vote on answer
- posted
16 years ago
I took a backup of the client's database and restored it on our test platform. Tests show that even after disabling the 3* validation mask from the AX tender, pressing '3' in the tender amount (any tender) behaves like PgDn (it goes to the bottom of the tender screen to the last tender type. 3 never gets entered into the amount. Moreover, even when enabling the touchscreen keyboard and clicking the 3 button, the same thing happens.
when i restore to another database, the "bug" effect is gone. therefore it's not a virus; it's something corrupt in the database.
"J Shirk" wrote:
- Vote on answer
- posted
16 years ago
I took a backup of the client's database and restored it on our test platform. Tests show that even after disabling the 3* validation mask from the AX tender, pressing '3' in the tender amount (any tender) behaves like PgDn (it goes to the bottom of the tender screen to the last tender type. 3 never gets entered into the amount. Moreover, even when enabling the touchscreen keyboard and clicking the 3 button, the same thing happens.
when i restore to another database, the "bug" effect is gone. therefore it's not a virus; it's something corrupt in the database.
"J Shirk" wrote: