The data entry component to my app. It now includes a lookup where it locates the data they just entered in a reference DB and allows them to spot-verify that they're making changes to the right person, since illegible handwriting and/or people not knowing their ID number often leads to data being entered for the wrong person.
Of course, I also (finally) implemented "undo" 😛
My coding style involves lots of error messages being coded for conditions that should never, ever, ever, EVER be true. Things like "If you are reading this message, the apocalypse is upon us. RUN!". It keeps me sane. I call them "easter eggs." You'd call them a waste of time and binary.
But anyway, I went ahead and installed the new JARs. Within about 15 seconds... "TONY, WHY IS THIS ERROR MESSAGE POPPING UP?" I walk over and it says on the screen...
Of course, I also (finally) implemented "undo" 😛
My coding style involves lots of error messages being coded for conditions that should never, ever, ever, EVER be true. Things like "If you are reading this message, the apocalypse is upon us. RUN!". It keeps me sane. I call them "easter eggs." You'd call them a waste of time and binary.
But anyway, I went ahead and installed the new JARs. Within about 15 seconds... "TONY, WHY IS THIS ERROR MESSAGE POPPING UP?" I walk over and it says on the screen...
Uh-oh. Fortunately, that message isn't as fatal as it sounds. The program still functions as it did pre-update in that condition. All you have to do is ignore it. So instead of resting on my laurels, I busted out the code and started trying to figure out why it worked on the devbox, and not on the deployed boxen. Turns out, I FORGOT TO INSTALL THE DAMNED REFERENCE DATABASE. That error is a "File not found" for a required file.If you are reading this message, the apocalypse is upon us. RUN!