>>>>>Don,
>>>>>
>>>>>I'm sorry, but did you add NOFILTER to your select command? I bet it's creating a filtered view and thus you're getting the problem.
>>>>
>>>>I did. Yes. It did not change the result.
>>>
>>>Does this report use default DS? Did you verify there is no interfering timer?
>>>
>>>If you add browse right before report form command, what data would you see?
>>
>>There is no timer.
>>Browse immediately before the report form shows the correct cursor.
>>What do you mean by DS?
>
>Report may have private DS if the check for DS is clicked.
>
>>I created a new report from scratch (no wizard) with just the details band. I was hoping to find something in the report that was messing things up. But it had the same behaviour.
>
>Well, I'm puzzled as well at the moment. I'll think at night on the problem to see if I can come up with more ideas to check.

What is really strange is this: If the cursor is located on any of the controls directly on the form when the report is run it will error. But if it is located in an editbox on the first page tab it will work OK. However setting the cursor to the editbox programmatically does not solve the problem. Looking for something unique about the editbox I find nothing. I also tried Chris's suggestion with the DE but it did not solve it either.

I'll be out until Monday. Have a great weekend.