Re: Missing VFP9.0 print jobs

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hi Nico:

No, I don't have any suggestions. However, I do have a question. Does the
report print if you exit Visual FoxPro?

By the way, have youtried opening the report with a SE command cna clearing
the Expr, Tag and Tag2 fields?
138396 How to use the default Windows printer in Visual FoxPro
http://support.microsoft.com/default.aspx?scid=kb;EN-US;138396

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/info/product.aspx?view=22&pcid=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


>Hi Lee,

>We have now tested with a SET PRINTER TO immediately afer the REPORT FORM
>command.
>The exact code is:

>SET PRINTER TO DEFAULT
>SET PRINTER TO
>REPORT FORM ("&lcReport") &tcCommand
>SET PRINTER TO && release print job

>This doesn't work, no physical print.

>I decided to do another test, using a 3th party print engine (latest
>evulation version of xfrx). For test purposes I replaced the code above
>with:

> LOCAL lcPrinter, loObj, loXFF
> loObj = EVALUATE("xfrx('XFRX#LISTENER')")

>* Output to a temporary file
> loObj.targetType = "XFF"
> loObj.targetFileName = ""
> REPORT FORM &lcReport OBJECT loObj
> loXFF = loObj.oxfDocument

>* Send the document to a printer
> lcPrinter = SET("Printer", 3) && get default printer
> loXFF.printDocument(lcPrinter,"Mod4U", 1, 10000)

>We now observed that the document prints if using xfrx as external print
>engine. However, in that situation the layout differs too much from the
>original (wordwrap is different), so, using xfrx for printing would mean
>that a lot of .frx files needs to be modified.

>It looks like there is a problem in either the .frx or the VFP printing
>engine.

>Lee; do you have any suggestions based on this information ?

>Nico>

.

Relevant Pages

  • RE: Missing VFP Printjobs
    ... Keep an eye on the product lifecycle for Visual FoxPro here: ... >Is there any way, within VFP, to see if a print job actually was printed? ... >I would try adding the following command immediately after the REPORT FORM ... >>After the report has been run, a SET PRINTER TO DEFAULT is issued. ...
    (microsoft.public.fox.vfp.reports.printing)
  • Re: Pictures on Reports or Labels
    ... By using the MEMO BINARY field type and a UDF, we can store .JPG files in ... a table field yet when the report runs have them read from DISK. ... ENDPROC ... Keep an eye on the product lifecycle for Visual FoxPro here: ...
    (microsoft.public.fox.programmer.exchange)
  • RE: general fields
    ... Visual FoxPro 8.0 supports TIF files. ... Here is some code for displaying image files in a form and report without ... LOCAL lcTemp as String ... Keep an eye on the product lifecycle for Visual FoxPro here: ...
    (microsoft.public.fox.vfp.reports.printing)
  • Re: Printing Saved Files
    ... Here is some code to create a PDF file using Visual FoxPro: ... Demo showing how to print a Fox report to a PDF ... DECLARE INTEGER FindWindow IN WIN32API STRING, ...
    (microsoft.public.fox.vfp.reports.printing)
  • Re: Printing labels?
    ... SET PRINTER TO NAME Gen_Label ... REPORT FORM labels\address.lbx TO PRINTER NODIALOG ... Report command. ... Often one single SQL result cursor is enough to display parent table ...
    (microsoft.public.fox.programmer.exchange)