1) I can't reproduce the issue with my simple survey (survey structure is attached) ==> can you reproduce the issue with my sample survey?
2) Can you provide a sample survey structure, where I can reproduce the issue?

Well when I tried to import the csv file, creating a new survey I get:
Warning: Invalid argument supplied for foreach() in /home/<USERDIR>/public_html/surveys/admin/importsurvey.php on line 1184
Couldn't insert quota
insert INTO lime_quota_members (,sid,qid,quota_id) VALUES ('#','66545','','')
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'sid,qid,quota_id) VALUES ('#','66545','','')' at line 1

If you send me an e-mail to wrduncan at wsos dot org I can set you up with an account so you can see it first hand if that would help.

@ wrduncan:
1) email is sent
2) please upgrade to the latest version ==> an important bug for you (03590: Quotas and Multilingual Surveys) is fixed

I can reproduce the issue with a labelset by wrduncan ==> I attached my test survey ===> limesurvey_survey_62239.csv

I am currently in the process of updating the code to the latest build. I am going to see what the easiest way to do this since it was originally a cpanel install.
I will post back when this has been completed and see if issue goes away.
Thanks.

I updated to the latest build (7523) and it appears that issue with duplicate entries in the dropdown (in our case County names) did not go away.

In the interim, I have removed the option for Spanish to facilitate the data entry for our staff. The survey results are now coming in rather rapidly and I wanted to try and make it as easy for the data entry folks as possible.

BTW - the updated code also broke my template I think - the CAPTCHA wasn't showing the question, only the answer box. Since I felt this was a tad too difficult to expect from our survey takers, I just removed the CAPTCHA requirement for the time being. I will have to look at my template again and see what I left out. (It was just based off the limespired template, and made blue to match our organizational colours.

Sorry, I didn't mention that I could reproduce the issue on the latest version - but the upgrade was a good idea anyway!

I am not sure why this issue got closed, I am still having the issue. The upgrade didn't fix the problem.

I think the bug got fixed in a build that you currently don't use. The easiest way is to wait till the next package is available for download (normally next monday).
Or you get the actual branch via SVN.

jelo is right
Resolved=Bug is fixed in the development version
Closed=Fix is released.