Thanx David, but I need the prompt. What I ended up doing was trapping the error with my error handler and then ignored it. I can live with that for now, but I won't totally comfortable until I get it resolved.

Got an email yesterday from someone else experiencing the same problem. Since it does the same thing in VB, maybe it is a bug. If so, is there a way to get MS involved? I'm going to be relying more heavily on the web browser control as I have stopped using the Report Writer in favor of generating HTML instead.

Charlie