3 ms·
Our health database was being used in many states but one hospital reported error messages of "Invalid patient postcode" to our Client Support. C.L. couldn't du
by helph67 2y ago
Our health database was being used in many states but one hospital reported error messages of "Invalid patient postcode" to our Client Support. C.L. couldn't duplicate the problem so I was sent to investigate, after checking that our same version was not giving the same errors. Long story --> Short; the operator inputting the postcode data was had been using `l' instead of '1'. The font in use made it difficult to detect the differences.
- martinbaun 2y agoThese are annoying. Reminds of two bugs I had as well. 1. One guy used tabs instead of spaces for fun and we couldn't find the records. 2. One.... "person" decided to put some values as null, for fun. :D Didn't break the system, but the client thought it was a bug.
- mcswell 2y agoI had an 'l' for '1' error half a century ago in FORTRAN code, keyed in by me on punch cards. The line printer printout of my code distinguished the two symbols, but the ribbon was old and the distinction was nearly--not entirely--obliterated in print.