>Thanks a lot. I will try that.
>
>Why in the past? It doesn't make a difference whether you are using 2.6 or 5.0, right?
Just hedging my bets incase something had changed - I'm a newbie to 3 (have to cater for 16bit os) and haven't written any reports yet. - Sarah
>
>ShihChau
>
>>I can't remember the exact code I used in a situation like this in the past (2.6 land) but it used the field() command, something like evaluate(field(1)).
>>
>>This might be an appropriate fix in this case.
>>
>>Good luck
>>Sarah
>>
>>>>>>If you have seen this in another section, I am sorry. I posted into the wrong category.
>>>>>>
>>>>>>I have generated crosstab cursor, ready for reporting. But since the fields are created by VFPXTAB, I won't know exactly what fields are created. Without knowing exactly what fields I have, how do I write the report?
>>>>>>
>>>>>>Is there a good way or do I have to make a fix column table and insert data into it?
>>>>>
>>>>>You have two options:
>>>>>1. Open resulting cursor and see what field names inside.
>>>>>2. Run one more step to rename all fields into nicer ones, using e.g. Select..Into Array and Insert into ... from array...
>>>>
>>>>Sorry, I don't understand the first option. After my program sees the field name, how do I write it into the reports? What do I put in my report during design time?
>>>>
>>>>Thx
>>>
>>>First option is applied if you have static situation, i.e. column identifier is always the same (e.g. jan,feb,etc.). In this case, you always have the same field names, and just check them once from command window. If it's not the case, then use option two.