>Hi Dragan
>>
>>When the third type is introduced, get back to Borislav's message :).
>
>I'll bear it in mind, but it is essentially the same solution, just my code is in the report and Borislav's suggestion would use essentially the same type of code when building the cursor.

The idea is roughly the same, but while iif() returns only two possible values, with a cursor you can have an unlimited number. Speaking from experience, in any situation where you have a check for a particular value of a string, it usually starts with "this value or the other, so it's an iif()", then becomes a case statement with a number of values, and ends up as a foreign key into a lookup table :).

In your case, it can't go over 254 values, as the number of fields in a table is limited, so you may be lucky. I've just learned to spot the places which can grow more complicated.