>the cursor should be selected. there are numerous fields in the report based off the cursor; however, dxdt is in the page header (it refers to a date), so it will be referenced first. I know I select the cursor before I do the report form command, but since it doesn't occur on my machine I can't be for certain that the clients machine is looking at the same cursor, especially since the error doesn't occur every time they run the report. I probably need to clarify what I said earlier too. Dxdt was a variable in the procedure that called the report. We had to capture that variable in the report cursor because we had to create another executable program that runs the reports (for flexibility from client to client, they want to see different results). Maybe this will shed some light.
>

Since you never see the problem, and your client only sees it sometimes, I'd say that the problem is data dependent. Is the dxdt field displayed on the report, or is it only used in expressions? If it's displayed, is there a print when condition that is always .F. for you, but sometimes .T. for them? If it's in an expression, is it in a part of the expression that you never run, but they do?