And what do you do when you get an interpreter that speaks 11 or more languages? Think of the changes you'd have to make to support that change.
Instead of 10 different fields for recording the languages each interpreter speaks, create a related "languages" table where you have one related record for each language spoken by a given interpreter. Not only will this make searching for an interpreter that speaks a specific language simple (you now have just one field to search for all languages), it will make many other reporting tasks easier to set up should you need to do so with your database.
That worked great. I inserted a portal linking to the languages table and it works great! Thanks.