And then it gets a little weirder. . .so, I tried a number of things to work around the error message. I tried changing my email address in my profile (didn't work). I tried clearing browser (didn't work). Then I invited my husband (who is on our hotel reservation) to help "plan" through MDX (as if!). I used his email address and our reservation number to log into Be Our Guest. It worked--I got in! But, once again, the four people who popped up on our reservation were NOT the people we are traveling with, but rather four men! I figured I'd give it a shot anyway, since the reservation was under my husband's name and we needa ressie for 5 people, anyway, and tried to book a table, but when I went to the available dates, all I got was May 1-7, which I figure are those other people's travel dates. Those aren't the dates I need. I hit May 7, anyway, just to see if it was available (it wasn't), but when I tried to go back and check a different date, I got the error message again. Has anything like this happened to anyone else?
Sort of. When I first logged on, I used the wrong reservation # from our luggage tags (which the site allowed!) and made a FP reservation. I realized my error today and tried to change the reservation # associated with my account. I didn't want to not have a valid FP or interfere with someone else's FP. I couldn't figure it out, called technical support, and got nowhere. Luckily the # I used is not affiliated with a reservation yet, but it could be---or the restaurant might cancel the FP after it sees I don't have a valid reservation #. Luckily I was able to create a new account with husbands email and correct reservation #. So we cancelled the first FP and scheduled a new one with his acct. Sounds to me as though you could easily fiddle with the #s or enter one incorrectly and cause the problem you've encountered. It's crazy that their computer system doesn't have safeguards for this sort of thing.