A number of clients have reported this over the years. If they don't catch it in time, they have to reversed the check run, reboot their computer (which somehow fixes the problem), and reprint all checks.

Has anyone else experienced this? Is there a real solution?

The latest client to complain is using 8.1F (140409)

Thanks

Steve