Hi Liam,

Did you test this report alone, without any form open? Create cursor in command window, than modify report YourReport. If the problem still exists, it's definitely a report problem itself and you should carefully examine each aggregation function, if you use them, for example, in page footer. Check report variables also. There could be reserved names, etc.

If the problem doesn't appear, then you call it from command window, the problem is in the Form...

>Hi Barbara,
>
>>I second's Nadya's opinion that you're probably calling a function that changes work areas. Make sure you check the OnEntry and OnExit fields for each band, and grouping expressions, and expressions for storing values to variables, as well as any function calls you might have in any bands.
>
>Thanks for your input. However, that's not the problem. It's a very simple report that has no UDF's contained in it. There are also no references to tables in the report (eg table.field). Even if I were to have called a function call that changed tables, the result should not be affected by browsing the table prior to issuing REPORT FORM.
>
>It's a strange one. Thanks for your input.
>
>Liam