>>I'd suggest putting an
>>
OTHERWISE
>> RETURN SPACE(12)
>>
>>in that CASE statement, just in case....
>Ed R. Suggested that, too. It worked, which showed me that the SQL was IIIFing
>records that didn't match my WHERE clause. Theoretically, there never should
>have been an otherwise case.
Yeah, I noticed that after I posted. :-( My experience has been that you should
always put the OTHERWISE clause in, because sooner or later, something will slip through....
