Adam,

Thanks for sending me your report. I could finally see things that you wouldn't have known to mention to me.

Here's the most foolproof way to do reports. Make ONE CURSOR with all of your data, including the results of your special functions. (SELECT MyFunc(MyField) AS MyInterpretedField...). Make sure that this CURSOR is SELECTed right before you run your report. (It will be if it was just SELECTed.)

The report cursor will be very non-normalized. Do not attempt to use related tables unless you want a debugging nightmare. After you've done this, setting a couple of variables in the command window is easy and debugging the rest of the problems in your report will be much simpler.

In the report, refer to the fields as MyField and not MyTable.MyField.



>Sorry I didn't get back to you sooner, but I was traveling last week. Below is the code in a procedure which prepares all the data for the Report. I now notice that when the number of records in the detail band exceeds one page (12 records per page), that the next page repeats the last record on page 1 and then prints no further records. The 'gnTotalRooms' also then reflects the erroneous amount [13] instead of the true amount of records [20].