Guest
Rank: Apprentice
Rating: 0%, 0 votes
It appears this is something to do with the way the network printer driver works, and only appears to be a problem when using a networked\shared printer. The problem occurs when the Windows API .EndDoc procedure is called, apparantly if you configure the compiler to ignore floating point overflows this seems to work OK, but thats sounds like a horrible solution.
I am unsure of the context of your problem but judging by the website you're probably printing, rather than writing code, so my advice would be to contact the vendor to see if they have updated software. We had this problem with our software, and had to change it as above.
I'm sorry thats not the best of help, the only other work around is to connect to the printer locally\directly.
Ross