>Hi Nadya,
> that is so funny. We put a browse command in after the client notified us about the error. With the browse, everything worked fine. We commented the browse out and everything worked fine for the rest of the day. The report only runs on Friday. So the next Friday, the first time the report ran, they got the error, but it worked everytime after that. So I am waiting for this Friday to see if the error occurs again. Thanks again for your help.
>
>Randy

Randy,

Does your report run in separate DS? In our case we have Main application and Special application. If I make special to use its own DS (create a Session object), it doesn't produce an error. If Special runs in Main application DS and I don't put Browse command, it produces an error. In our case it's a form with a grid and there are several grid.SetFocus() command in the form's code.

Since you don't have a grid, but just combobox, it's probably a case, which was not found before. (Grid problem is well known, I think). Let's see, if somebody else has the similar problem or could reproduce your problem.