1 of 1 people found this helpful
The issue I had quite some time ago only affected one of our many clients (thats my secondary post you linked to)
I initially posted on the old 'techtalk' and received quite a few suggestions to try and rectify the problem, unfortunately since the transfer to this community platform the original technet posts are now in pieces..
Have you tried the steps which I thought solved it on the fm forums?
Our client has never had the issue since (same hardware too) and we have not set the solution to run in compatibility mode either. I know they may not be 100% accurate, after all I typed " I think..." , but at the time I was trying all sorts to fix it.
Lyndsay Howarth's post linked below was part of the overall fix which I seem to have missed on the "fm forums post"
Related posts are showing in the "More like this" box on the right but its a mess
Edit: I should add, the initial issue for us was with FM10, the clients moved over to FM11 about a year later. We have not moved over to FM12 yet.
Thank you Steve!
Sorry its sketchy, but I hope something helps
Chalk up another use still having this issue in Win 7 - FM 11. I was hoping some part of this was resolved in 12 but apparently not. Le sigh...
I'm considering putting an error catch in the print scripts to just save as PDF when this problem happens so the users can print from the PDF which seems to work.