Is this a known bug? 2

[Olaf Doschke]

A customer has a report problem. Preview looks ok, but the printed report has lines partly cut off, as if there is some opaque element hiding most of one line. The same result on different printers of our customer, so empty toner is out of question.

How it looks (as far as I am able to show via ASCII):

_     .

Second Line

How it should look:

First Line
Second Line

So you only see a small part of the firs Line, say the upper line of the big F and a dot of the big L.

The detail report control in question is having a table.field as it's expression, printing a multi line Memo field with a monospaced font. So it's a single report control (in the header band, if that matters, printed once on page 1) displaying one to several lines (via "stretch with overflow").

The Font is unusual - Arial monospaced for SAP - but it's not missing and printed OK in preview. I also already tried Courier New. I also removed any printer info from Expr besides PAPERSIZE and ORIENTATION.

I can't reproduce with my printer, so I wonder if anyone knows a report bug, that could cause this. My thought was, the memo field may contain control characters, but nothing unusual in some recorded saample data, only CHR(10) and CHR(13) besides the text, not even TABs.

The customer is pinned to the official VFP9 SP2 without the latest Hotfix, which is indeed report related, but address other bugs, AFAIK.

Comparing a scan of the print with a screenshot of the preview zoomed to the same size, the spacing is correct. It's as if there is an opaque rectangle hiding most of line1, but there is no such thing in the report, and no special handling and changing the FRX previous to printing.

Bye, Olaf.

 

[DSummZZZ]

It sounds like a printer (driver) issue, but does changing SET REPORTBEHAVIOR make a difference?


-Dave Summers-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm

 

[Dan Freeman]

It does ring a bell, but not loudly enough to tell me anything.

Is the object shoved a little too tightly against the top of the band? What happens if you lower it by a pixel?

 

[Nigel Gomm]

Olaf,

how does it compare to this issue i had with a specific Canon printer last year?

http://www.tek-tips.com/viewthread.cfm?qid=1713150

i never found an answer to that - the customer worked around it.



n

 

[Olaf Doschke]

The workaround used right now is to print as PDF File and then print that. That works, so there is no hurry anymore.

It happens with most but a few printers, so I don't think it's a driver problem.
Many printers are HP, which rings a bell, I think. But I don't know if all printers not working are HP.

I'll test Reportbehavior and making the control a little larger actually is a good idea, even though stretch with overflow should do that

(The preview looks a little washed because it was embedded in Word)

In this case there is only one line of text, but even then it's not fully printing, the scan might be of another formula, otherwise the upper part of the 0.00 would have moved right, which could indicate an unwanted zoom effect and then clipping. If I enlarge the original size of the control we might really see a zoomed text printed.

OK, thanks so far, I'll report back (no pun intended)

Bye, Olaf.

 

[GriffMG]

I have seen a similar problem with a report - it turned out to be a slightly corrupted .frx file, where some of the
elements had 'something' in the Print When condition - not visible in the GUI, but easily cleared if the .frx was opened
directly.

You might have something similar?

Regards

Griff
Keep [Smile]ing

There are 10 kinds of people in the world, those who understand binary and those who don't.

I'm trying to cut down on the use of shrieks (exclamation marks), I'm told they are not good for you. ​

 

[Olaf Doschke]

Thanks Dan and Griff,

turns out enlarging the report control to three lines instead of one is helping, so automatic stretching may not work good enough.
It's Reportbehavior 90 and I didn't test legacy mode, I know there is a slight size change, if VFP prints in 90 mode with GDI+ and the reports are legacy, no report listeners, no advanced features used.

Bye, Olaf.

 

[dbMark]

Do you have ActiveX control boxes side by side with text boxes and stretching enabled? I found an issue with that years ago, never solved, so I had to disable the stretch option and use multiple single line boxes. Fortunately I knew what the maximum number of lines would be.
thread184-984387