I understand, but I don't think limiting vehicle years to the actual years the vehicle is available is too rigid. You all did a great job of making this site easy for a user to add a vehicle, but having the year drop-down be limited is not adding any more steps to the user, [u]they have to use the drop-down anyway, why not just limit the years.\[\/u]
Actually that brings up another point, in the FAQ for "what if my car/motorcycle year isn't listed"
it's stated that an administrator "might" need to approve the new year, do you all actually do that? It doesn't look like it. That seems that might be more work on your end then what's necessary.
I'm sure the 2004 Prius V is an honest mistake (and I did send them an email about 1 month ago...no response yet), but that person actually used more mouse clicks just to enter the incorrect 2004 model than if they were just limited to the correct years.
Anyway, I'm not a coder (except for some SQL for report writing) but I do manage a database (which I inherited) and I'm always asking the coders to build in QA/QC controls in the front-end so that it's less work on my part and then there's the knowledge that the data isn't garbage. Granted my DB is for environmental monitoring where correct data is critical, but if you have the tools why not use them?