Does anyone else get a wrong birthday when checking their registration at voteforchange.com?

[backscatter712]

It just happened to me. My birthday is correct when I checked my voter registration on my state's web site.

Who knows? I'm gonna doublecheck my registration, AGAIN, tomorrow. In person. At my county's election office.

Because I know that if my birthday in my voter registration is wrong, I'm vulnerable to purging - they'll claim my information's bad, thus they need to remove my name from the rolls. I wonder if somebody's doing this on purpose?

[applexcore]

1. Mine is wrong

The day is right, but the month is wrong.

[ingac70]

2. Given the state you are in...

I would definitely straighten that out... and get the word out to all you come in contact with to check on their registration!

CO is a major battleground, and this crap could well be on purpose.

[eleny]

3. I'm also in CO and got that message at first...

I had forgotten to put the / as they indicated in their example. Could that have been the problem or is it the date itself that's wrong?

[Seen the light]

4. Voteforchange.com isn't always right

According to them, my birthdate is November 30th. According to the NC Board of Elections, my birthdate is listed as correct.

[XOKCowboy]

10. I got Nov 30th also...

I went to the county offices and checked my registration info and it's correct. Methinks VFC's software is buggy.

[liberalmuse]

5. Some people were saying their birthdate was showing as November 30th.

I don't think they're right on this info. If your state has online registration, check your status there.

[applexcore]

9. Thats what mine was

[uppityperson]

6. It was doing this yesterday also, try this site also.

http://www.canivote.org/

It is good to check in person, but that website was having issues last night, something about Oct 30th I think. I found mine later, was fine.

[elkston]

7. Its obvious there is problem in their software somewhere ...

The origin database contains the correct information, but somehow their display routine is not using this value. (I suspect a typo in the code -- referencing the wrong variable or an incorrect integer constant)

[backscatter712]

8. That sounds likely.

Probably grabbing a date from the wrong column in a database table.