It may not be OOP correct, but I rarely use the DE for reports. I typically create one cursor to report on with all the fields I need for the report. If I need a relationship for the detail section, I create two cursors, index them using random index names then programatically create the relationship in the BEFORE OPEN TABLES event. It works great, and when you get rid of your cursor it automatically deletes the indexes. I must admit I still get a little confused when programatically creating relationships. It always seems backwards to me, but I eventually get it all in the right order.

Marcus.

>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