Perfect solution Richard, except that, like today...0, zero, zip,
nada...errors reported and they run this report several times every day
as a way to look up info they need for their job. Yesterday there were 6
errors from three different computers in two different towns.
I can't get past the idea that if there is an error in the report's
content or structure, why would restarting the application fix the
printing problem?
Thanks for the input though!
Mike
Richard Kaye wrote:
Another brute force option is removing one object at a time from the FRX and
see when your error goes away.
--
rk
-----Original Message-----
From: ProfoxTech [mailto:[email protected]] On Behalf Of Mike
Copeland
Sent: Friday, June 12, 2015 5:49 AM
To: [email protected]
Subject: Re: Where would you sniff?
Thanks Richard.
I've cleaned the (appropriate) memo fields in the FRX of the report and it
continues happening. But I agree with you that this is a very common problem.
Mike
Richard Kaye wrote:
In the past, I've run into detail band too large issues when the printer
environment is saved in the FRX and the printer does not exist at the client
site. If you're using standard paper sizes then you should be able to clear out
the printer stuff from the FRX.
--
rk
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
