...only my dog knows for sure. :~)
Mike
Kurt @ VR-FX wrote:
Like rk - I've had similar issue on past w/label printing!
But - as 4 Where 2 sniff - I'm not sure my response would B appropriate in this
public forum!
:-)
-K-
Sent from my iPhone
On Jun 11, 2015, at 5:44 PM, Richard Kaye <[email protected]> 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
-----Original Message-----
From: ProfoxTech [mailto:[email protected]] On Behalf Of Mike
Copeland
Sent: Thursday, June 11, 2015 5:18 PM
To: [email protected]
Subject: Where would you sniff?
I have a VFP9 app that has developed a new and intermittent printing error
problem.
When printing a report, I randomly get a
"Detail 1 band is too large to fit on page"
error when running one particular report. Thinking it was just a problem with the
report spreading out into the left/right margins as the error suggests, I reworked
the report and now have 3/4" blank space on each side, using nothing but Arial
typeface. No change in the problem, the error keeps coming up randomly. When the
error happens, there is no output, no paper, nothing sent to the printer.
This application and report just recently developed this problem and it happens
on different computers...all running Win 7 or WinXP.
I have changed printer drivers from Postscript to XL. Still random errors. I installed
the printer drivers from Microsoft's auto-download and install routine in the printer
setup. NO change. Downloaded and installed the printer drivers from the manufacturer
(Lexmark)...no change. I have also checked and cleared the "printer residue"
settings in the FRX file memo fields before compiling the application to an EXE (the
report file is included.)
Finally, one "fix" that always seems to work is to close the application and
reopen it, and the report prints fine. Every time.
Obviously there is something being changed by something as the application is being used
for various tasks...some setting or value is being left in a state that causes this
printing error to happen, even though the report is good, the data is the same, and the
printer(s) are okay. The "other" tasks that this application does are pretty
standard:
obtain and store data from DBF and MySQL files, display forms on screen, etc.
Nothing fancy or edgy. Also, this gremlin has been giving me grief now for
over a month, and it is consistently random. 20+ computers use this application
every day and there will be 4 or 5 error reports each day from different
systems at different locations.
Question: Where would you look or suspect as being the cause of the problem?
Thanks for any WAGs or war stories!
Mike Copeland
[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.
