You do make a good point, but the reason I am doing that is because I am using the table to update another table, and I need the LangSymbol field and *not* the Language field. I could do the update query looking this up, but it would be more complicated.
But actually, you have solved my problem. I think your line of code assumes that I have a (possibly hidden) txtLangSymbol field on my form bound to the LangSymbol field in the table. I guess that would work.
However, your line of code made me realize something else. Why do I need the Language field bound at all? Why not make the language name visible, but make the hidden ctlLanguage.column(1) bound to the LangSymbol field in the table. That way when the user selects the language, it will be the *symbol* that gets into the table. I don't need a language field in the table at all! I redesigned the form that way (and changed the "required field" properties in the table) and it works! Thanks a bunch.