>This wouldn't have occurred during printing a report to an HP printer, would >it? If so, check MS KB article Q183522 for a fix.

There is an HP printer installed, but this program hasn't gotten as far as actually printing anything yet. Thanks for the KB article reference, it explained what is causing this error - and it might be a division error during a Select-SQL statement. (the harder management cracks the whip, the quicker the product is released, but also the more code 'oversights')