FoxPro Help and Support - preview / print differences

Author

preview / print differences

Villi Bernaroli

2005-12-20, 11:24 am

A customer reports that one of our print reports gives him a
problem: in preview it shows all the records it should, while on
the print it just prints the emopty page (borders and grid for
the records data, but no records data in it).
I have never seen this happen before, there maybe something wrong
with his PC ().
The report is a classic VFP report who cycles on a single table
created for the print job, and the 2 REPORT FORM commands differ
only for the PREVIEW clause.
Any clues about this issue?
--
The answer to the ethernal question is:
put a read events after the launch of the form

Stefan Wuebbe

2005-12-20, 11:24 am

"Villi Bernaroli" <a@b.c> schrieb im Newsbeitrag
news:OwQTCSYBGHA.740@TK2MSFTNGP12.phx.gbl...
>A customer reports that one of our print reports gives him a problem: in preview it shows
>all the records it should, while on the print it just prints the emopty page (borders and
>grid for the records data, but no records data in it).
> I have never seen this happen before, there maybe something wrong with his PC ().
> The report is a classic VFP report who cycles on a single table created for the print
> job, and the 2 REPORT FORM commands differ only for the PREVIEW clause.
> Any clues about this issue?

Hi Villi,

One possible cause might be that the current workarea changes
unexpectedly, e.g. when a grid object gets focus right before the report
starts printing.

hth
-Stefan

--
|\_/| ------ ProLib - programmers liberty -----------------
(.. ) Our MVPs and MCPs make the Fox run....
- / See us at www.prolib.de or www.AFPages.de
-----------------------------------------------------------

Dan Freeman

2005-12-20, 1:24 pm

I agree with Stefan's suggestion but one more thing to check....

Does your report command contain a scope clause? If the preview leaves you
at EOF(), you might not get any records printed without a proper scope.

Dan

Villi Bernaroli wrote:
> A customer reports that one of our print reports gives him a
> problem: in preview it shows all the records it should, while on
> the print it just prints the emopty page (borders and grid for
> the records data, but no records data in it).
> I have never seen this happen before, there maybe something wrong
> with his PC ().
> The report is a classic VFP report who cycles on a single table
> created for the print job, and the 2 REPORT FORM commands differ
> only for the PREVIEW clause.
> Any clues about this issue?

Lee Mitchell

2005-12-20, 8:26 pm

Hi Villi:

Take a look at this article and see if it describes the behavior you are
seeing:

185628 Printing or previewing Report Form results in incorrect data
http://support.microsoft.com/defaul...kb;EN-US;185628

I hope this helps.

This posting is provided "AS IS" with no warranties, and confers no rights.

Sincerely,
Microsoft FoxPro Technical Support
Lee Mitchell

*-- VFP9 HAS ARRIVED!! --*
Read about all the new features of VFP9 here:
http://msdn.microsoft.com/vfoxpro/

*--Purchase VFP 9.0 here:
http://www.microsoft.com/PRODUCTS/i...cid=54787e64-52
69-4500-8bf2-3f06689f4ab3&type=ovr

Keep an eye on the product lifecycle for Visual FoxPro here:
http://support.microsoft.com/gp/lifeselectindex
- VFP5 Mainstream Support retired June 30th, 2003
- VFP6 Mainstream Support retired Sept. 30th, 2003

>I agree with Stefan's suggestion but one more thing to check....

>Does your report command contain a scope clause? If the preview leaves you
>at EOF(), you might not get any records printed without a proper scope.

>Dan

>Villi Bernaroli wrote:
> A customer reports that one of our print reports gives him a
> problem: in preview it shows all the records it should, while on
> the print it just prints the emopty page (borders and grid for
> the records data, but no records data in it).
> I have never seen this happen before, there maybe something wrong
> with his PC ().
> The report is a classic VFP report who cycles on a single table
> created for the print job, and the 2 REPORT FORM commands differ
> only for the PREVIEW clause.
> Any clues about this issue?

OE Fan

2005-12-20, 8:26 pm

Lee Mitchell wrote

> Hi Villi:
>
> Take a look at this article and see if it describes the behavior you
> are seeing:
>
> 185628 Printing or previewing Report Form results in incorrect data
> http://support.microsoft.com/defaul...kb;EN-US;185628

Thanks, but it looks like this isn't the cause of the issue: it
applies to both printing and previewing. Tomorrow (now it's just
midnigth here) I'm gonna tell this guy to print using the button with
the printer icon in the preview toolbar: if the previee works he
should be able to print from there, I guess.
It could be just a temporaneous solution, better than nothing.
--
Vilco
Think pink, drink rose'

Sponsored Links