For those who tried to access the forecasts (or to "Login"/"Register") this AM but were rejected, the problem has been fixed as verified by all who have emailed me subsequently. If you want the long story, and to show how things like this can happen, the original "Registration" page contained a generic "example" in the email field, namely "your_email_address@your_email_account". One registrant must have been in quite a hurry as he changed nothing on the form except for the UserID field, leaving the example email (I'm not sure I'd want this guy to help me with a positive control check - he flies from the same field as I). Last night I scanned over all the entries looking for something that might be "wrong" so that I could alter either the program or the instructions to prevent "unwanted" things from occurring, since users are notorious for finding ways to break software (this is how improvements occur). Among other things I ran across that email line and realized what had happened, so I first removed that "example address" from the Registration template, so that no one else would do the same thing, and then also removed that entry from his account listing, since I knew it was an invalid address. The last was a big mistake - apparently the software _needs_ an email field for its processing (and indeed it will not let you complete a registration without one). So upon trying to read the user database the program would bomb if it had to read past that user's UserID, which was "db...". Since the list is alphabetized by UserID, everyone with UserID beginning with lower case d and beyond was therefore locked out (all IDs with an upper-case first letter or number were ok). After making my changes last night I had actually made some tests just to make sure everything was still working ok - but my "administration" login name begins with an "a" so no difficulties were encountered. I went to bed glad to have everything running so well but awoke to find 30+ emails in my box all complaining about lack of access! That certainly produced a shot of adrenaline, since I take considerable care to try to make things go as smoothly as I can (within the constraint of being only one person). I did find and correct the error fairly quickly, thank goodness, and did send emails to all who had reported difficulties to let them know that the problem was solved. There might be some who also failed to get in but made no report, to whom I also apologize for the difficulty since I know from (too much) personal experience how frustrating it can be when a computer fails to respond as it should.