>>>> ...
>>>>We have an application, called BldMstr Editor. This application has a form with three pages. First page has a grid with several fields from the table (only essential fields, so no codes) and two other pages show record detail info. The last step of the job is a report, which will show, how many coded fields we have in a file, and if there is incorrect code value, it shows ******** in description. So, converter will see, that he (she) has 70 records with incorrect value in, say, amenities, and now he(she) wants to look up those records.
>>>>
>>>>So, here is the question: how can we filter incorrect codes? Usually these lookups tables contain only few records (less than 15), so we may create arrays for each of them.
>>>
>>>Do you want to filter the records that show "*****"? How do you obtain these? Division by zero? If yes, you might filter for ... = 1/0.
>>>
>>>Hilmar.
>>
>
>So, what is the problem of issuing:
>
>SET FILTER TO MyField = "*******", after running the above program? Or do you want to make the above program more efficient?
>
>
>For the other question (only accepting valid codes), I assume Sergey's answer is faster than mine, because it doesn't involve a UDF.
>
>Hilmar.

Because it's a completely separate step in the Parcel Conversion job and it creates a cursor... The report is useful, but it doesn't tell us, where the records with invalid codes. So, I'm thinking about creating a filter in the BldMstr Editor application (insert this filter in our FilterDef table). I think, Sergey's idea about chrtran would work with one simple modification of using &cValidAmenityCodes and making cValidAmenityCodes as a global variable. For other fields, I think, I would use my original idea of not indexseek (or lookup function, whichever is more efficient).