Rahul- this is not a bug, I'm afraid, but a rather stupid side effect that came with the advent of the Data Environment. It is not new to VFP 6, it was around in 5, (and 3 I'm pretty sure, but I can't verify). Since reports now have DEs, they only show fields from tables in the DE, not all open tables. If you absolutely need this feature, add the tables to the DE.


>Bob:
>
>Thanks for your reply. But I'm afraid, I have already checked out all the conditions you mentioned. The simplest way you can duplicate this problem is as follows:
>
>1. Open VFP 6.0
>
>2. In the command window open a dbf by USE . Note that this dbf is in default data session.
>
>3. In the command window type in MODIFY REPORT test. Note that, by default the report will have Default datasession. You are welcome to change and try it differently.
>
>4. Try to add a field from the table while in Report Designer. Remember to use the Expression Builder's Fields Listbox. However, if you see what I am seeing, it will be an empty Listbox.
>
>Let me know, if you're finding anything different.
>
>Rahul
>
>
>>>I am trying to use the following code in an EXE
>>>
>>>USE abc
>>>MODIFY REPORT test
>>>
>>>Now, I expected that when I add a textbox to the report, I could use the expression builder and select the fields from the abc table from within the Expression Builder (there is a listbox for "Fields"). It used to work in Previous Foxpro versions. Now it does not work anymore. The users are having to remember(guess) the field names in the abc table. This particularly becomes a problem when abc is a cursor generated by a SQL select.
>>>
>>>Can anybody help me?
>>>
>>>Thanks in advance.
>>>
>>>Rahul C.
>>
>>Either your report, or your form, or both are using a private data session. But, basically, the report is not looking in the same data session that your table is open in.
>>
>>You could either open the table in the reports data environment, or make sure that your form is using Default Data Session and so is the Report... or, if your form is using Private Data Session and the report is using Default Data Session, this should work too.
>>
>>BOb

Erik Moore
Clientelligence