Yes you are.

Post #92,031 by tseliot 3/26/03 9:08:02 PM Reply	Yes you are. Just kidding. But I would put those values in a table for fear that I would need to change them someday. Much quicker to change table entries than a soon-to-be-massive switch statement. Many fears are born of stupidity and ignorance - Which you should be feeding with rumour and generalisation. BOfH, 2002 "Episode" 10
Post #92,048 by jbrabeck 3/26/03 9:21:29 PM Reply	Agree, but... The way I understood the problem is that there are multiple fields that needed to be converted. Would have had to load the with many aliases to get the proper linking. I have a table of individuals. In the positions table I have, currently only, 10 different positions. To list the "Who's responsible" list, I have to link the positions table to the names table 10 times. Can't have multiple links to the same table. And if I understood correctly, field1, field2, ... fieldn all have values to be converted to Y/N/U. [link\|mailto:jbrabeck@attbi.com\|Joe]
Post #92,556 by tseliot 3/28/03 4:34:34 PM Reply	Then you have one of four choices If there are multiple fields per query, you have four choices: 1) Use Switch. This works until you get too many fields, or too many values, or change values often. Any one of those conditions makes maintenance a bear. 2) Use subqueries in the field list. This works if the number of fields stays small; the number of values can be huge and change often. 3) Store the value as text instead of a number. This increases DB size but lowers query processing time. Why have a lookup table if it's not normalizing anything? 4) Write a VBA function and call it within the SQL. Not portable. Pick one based on your environment. Many fears are born of stupidity and ignorance - Which you should be feeding with rumour and generalisation. BOfH, 2002 "Episode" 10

Welcome to IWETHEY!