>You can also do this using SET RELATION (which saves making the cursor), but unless the report is based on a very large table, I reckon the simplicity of the SQL Join outweighs the possible performance implications.

IMO, SET RELATION is still far superior in many aspects than SQL assuming that the table is a native VFP. In our case, we rarely use SQL commands in desktop applications because it does not recognize whatever current updates in the table when it is buffered (not until TABLEUPDATE() is issued.)

>
>Cheers,
>
>Andrew
>
>>I am doing a SELECT - SQL command that gathers all of my data for my report. But is there a way within the SQL command that I can translate some of the data that has codes to represent data which is really strings of text?
>>
>>For example my report shows a column of codes as in 1, 3, 6, 4, 6
>>1 = Ford
>>2 = Chevy
>>3 = Buick
>>4 = Pontiac
>>5 = Cadillac
>>6 = Chrysler
>>
>>Is there an easy way during the SELECT to translate the codes on the fly so I don't have to play games in the report or before the report to translate the codes? So the word Ford prints instead of the code 1 and so on.
>>
>>I am simply looking for a shortcut or better way. Thanks for your able-bodied assistance ahead of time.