Thanks George,

I'll try your suggestions and I'll let you know.

Paul


>
>It may be. If it is the division by zero, one potential solution, is to check for that possibility and simply not allow it. I know it sounds like a lot of work, and, perhaps it is. However, a long time ago, I made it a practice to enforce this in every summary report. Personally, I think it's a good practice, since division by zero is meaningless (infinite, if you want to be technical < g>). I've never encountered this problem despite the fact that nearly all the printers my applications print reports to are HPs (some old, true, but many are new).
>
>The other possibilities I mentioned would be: 1. To add a brief (10 millisecond or less) wait period after issuing the initial call. While I have no idea whether or not it would help, it certainly couldn't hurt. 2. Use a driver supplied with Windows rather than the manufacturer.
>
>Other than that, I don't have any ideas.
>
>hth,