RE: Missing VFP Printjobs

Hi ***:

I would try adding the following command immediately after the REPORT FORM
command:

SET PRINTER TO

This command forces VFP to close and release the print job.

Visual FoxPro 6.0 is no longer supported. I don't think this is a VFP
issue, but I feel I need to tell you that anyway.


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

>Lee, thanks for the reply.

>They are using REPORT FORM. At the beginning of the code, there is a SET
>PRINTER TO NAME XXXX statement that sets the printer to this network
printer.
>After the report has been run, a SET PRINTER TO DEFAULT is issued.

>The hardware people say they have downloaded the latest driver from HP.
This
>is a random occurance, so previewing the document would be tough to do.

>I believe they are running TS. The printer is about 6 months old and was
>installed new when the software was put in place. They are trying to get
>their hardware people to give them a loaner to try to see if that fixes the
>problem. Their hardware people will try some of the things you have
>suggested.
>
>This app was written and compiled in 6.0 SP5.

>Their network, at least to me, has intermittent latency issues (a nice way
of
>saying it's dog-slow). They do have a utility running called Norman, which
>appears to be an AV and Firewall.

>If you can think of any thing else to try, I sure appreciate hearing them
:)

>***


>Lee Mitchell wrote:
>Hi ***:
>
>I am not sure what the problem is, but I have some questions.
>
>Are they printing using the REPORT FORM command or @...SAY commands? Do
you
>have the most recent printer driver? Can they preview the report instead
>of printing it? Are you running Terminal Services or Citrix on any of the
>machines? Does this occur if you install a different printer on the
>Windows 2003 Server? Do you have the most recent printer driver for the HP
>1320 print device? Are you using VFP 6.0 with SP5?
>
>Here are some ideas to try as well:
>
>Try raster mode
>Try low resolution for printer.
>Try standard VGA
>Deactivate any Mathematics processor on the machine.
>
>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-5
2
>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 have a client who has an HP 1320 laser connected directly to a Win2003
>>server.
>>Occasionally print jobs will be sent to it from VFP 6.0 but they never
>>print. They switched from USB to parallel but that didn't help. This
happens
>>to all users on the network (W2k on all workstations). Just this morning
>>they saw the following appear on one of the documents that printed...
>
>>CL XL error
>>subsystem: IMAGE
>>Error: ExtraData
>>Operator: ReadImage
>>Positon: 112
>
>>Any suggestions?
>
>>TIA
>
>>*** Day

--
Message posted via DBMonster.com
http://www.dbmonster.com/Uwe/Forums.aspx/foxpro-reports-printing/200512/1


.