It looks like this bug is what we refer to, in technical terms, as a "glitch." Normally that means that the programmer has no clue, and that is half true in this case. The root of the problem is that the message number for http://dripinvesting.org/Boards/Read.asp?MID=97092 is "123," which is incorrect. If that was the last message read, then I calculate the number of messages to be read as the current message number (around 19,000) minus the message number of the last message read, so obviously this creates great confusion. What I actually do when saving your message is to initially store the message number as "123," then when I read the message back, I replace the "123" with the proper message number. In this particular case, for some reason, the message was written to the database, but could not be immediately retrieved. Amusingly, I left a message to myself in the code that the way I was doing things was awkward and needed to be rethought at a later time, so if I get a chance, I'll revisit this portion of the code.