>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.

Randy,

Do you have this variable defined in your report (Report/Variables)? Try to delete it from there on your copy.

Also how do you invoke this report? Is it on a form with a grid? I had the similar problem, which is still unresolved. If I invoke report form from a form with a grid, which has focus, even if I put select myCursor just before report form command, it could not find variables. I guess, it reselects Grid.Alias.