>>>Before I generate my report, I do some queries using SQL SELECT, and I save the results into Cursors. How do I use these cursors in my report? I couldn't just "add" a cursor to the Data Environment of the report. I tried to go around this by Writing my queries to tables, adding those tables to the DE, and then rewriting code so the query results are going into CURSORS again. However, the added table in the DE must have an INDEX to be able to set a relation between it and the other report table, and I cann't have an index with a CURSOR. Does this mean I should use tables instead of CURSORS?
>>>
>>>Mon
>
>>You can use the cursors directly in the report as others have said. The curse is that they no longer show in the field selection dialog of the report designer (I design my report "live"). In FPW you could "see" all the active tables in the dialog, in VFP that is no longer true, but they're still there.
>>HTH
>
>found this old answer and your reply. Wondering if you could shed a little more light and experience. Moving my app from VFP 2.6 to VFP 5.0. My clients are complaining that while they are building a report in query maker (third party product), that the fields of their query are no longer shown in the Fields listbox. query maker uses the regular report designer. Is there any way to get the query fields to show in the Expression Builder's, Fields listbox?
>
>thanks - brenda

Hi Brenda,
I don't think the others understand your problem. The problem, as you know, is that the data tables that exist in the current data session don't appear to be available to the report designer, even though they are! You can type them into the report and they work fine. I haven't solved this problem, but I know that only data files that appear in the dataenvironment actually appear in the list. Perhaps you can play with the dataenvironment by putting a "trick" dbf in the DE and somehow replacing it with a table with the same alias/dbf name when the report is to be designed/printed.
HTH a little :-)