Programming with dBASE - Weird printing problem

Author

Weird printing problem

John Fried

2005-12-22, 8:23 pm

I've written a generic report printing previewer form designed (with Plus
2.6 b1899) to use pdfFactory (a nice printer driver replacement that will
produce PDF files, email them, etc) using the following code:

Line
====
1 r = new &cRepName.()
2 r.startPage := 1
3 r.endPage := -1
4 r.outPut := 1 // printer
5 r.printer.copies := 1
6 r.printer.printerSource := 2
7 r.printer.printerName := "pdfFactory"
8 //r.printer.choosePrinter()
9 r.render()
10 r.release()

I have recently installed this on a client's server as part of their
upgrade from dB2K to Plus 2.6. Of 14 terminals, printing works fine on 9 of
them. On the other five, as soon as line 7 is executed, the entire dBase
app immediately closes - no error messages or anything. Just 'poof' gone!
If I comment out lines 6 & 7 and uncomment line 8, then it works just fine
on all machines -- even when the user selects pdfFactory as the printer.
The client prefers not to have chooseprinter come up though.

FWIW, this same code structure has been used with another client for years
without any problems.

All computers are running the same version of Windows XP, the same install
of the dBase 2.6 b1899 runtime and the same install of pdfFactory (both
done by me during the upgrade process). I suspect there is _something_ in
the network setting or in the Windows setup that is different for these
five machines, but I can't find anything.

Does anyone have any ideas or clues for what is wrong or where to look? I'm
at my wits end trying to solve this one.

Thanks,
John

Rick Miller

2005-12-22, 8:23 pm

Hello John,

John Fried <john@dataknight.com> wrote in
news:8YJ83J0BGHA.1584@news- server:
> Line
> ====
> 1 r = new &cRepName.()
> 2 r.startPage := 1
> 3 r.endPage := -1
> 4 r.outPut := 1 // printer
> 5 r.printer.copies := 1
> 6 r.printer.printerSource := 2
> 7 r.printer.printerName := "pdfFactory"
> 8 //r.printer.choosePrinter()
> 9 r.render()
> 10 r.release()
>
----

Don't know exactly why the problem :-(
This is the sequence used here for
report printer property assignment.

1) Color
2) Copies
3) Duplex
4) Orientation
5) PaperSize
6) PrinterName
7) PrinterSource
8) Resolution
9) PaperSource

Good Luck and Merry Christmas,
Rick Miller

John Fried

2005-12-23, 11:23 am

Hello Rick!

Thanks for the tip. I'll try rearranging the order and see if that has any
effect on the problem. Keep your fingers crossed... ;-)

A Merry Christmas to you and may 2006 bring lots of good things - like Plus
2.61. ;-)

John

Rick Miller wrote:
> Hello John,
>
> John Fried <john@dataknight.com> wrote in
> news:8YJ83J0BGHA.1584@news-server:
>
>
> ----
>
> Don't know exactly why the problem :-(
> This is the sequence used here for
> report printer property assignment.
>
> 1) Color
> 2) Copies
> 3) Duplex
> 4) Orientation
> 5) PaperSize
> 6) PrinterName
> 7) PrinterSource
> 8) Resolution
> 9) PaperSource
>
> Good Luck and Merry Christmas,
> Rick Miller

John Fried

2005-12-23, 11:23 am

Rick,

The sequence change changed nothing. Nice try but no cigar.

See my 'more info' post for, guess what, more info. ;-)

John

David Kerber

2005-12-23, 1:23 pm

In article <8YJ83J0BGHA.1584@news-server>, john@dataknight.com says...

....

> All computers are running the same version of Windows XP, the same install
> of the dBase 2.6 b1899 runtime and the same install of pdfFactory (both
> done by me during the upgrade process). I suspect there is _something_ in
> the network setting or in the Windows setup that is different for these
> five machines, but I can't find anything.
>
> Does anyone have any ideas or clues for what is wrong or where to look? I'm
> at my wits end trying to solve this one.

Were the printers all installed by a user with the same (probably
administrative) privileges? It sounds to me like some kind of access
restriction or permissions issue.

--
Remove the ns_ from if replying by e-mail (but keep posts in the
newsgroups if possible).

John Fried

2005-12-27, 9:23 am

Hi David,

In this case, all computers are running the same program which
automatically tries to print to the pdfFactory printer driver and then runs
pdfFactory to display the report. pdfFactory was installed without any
special priveledge settings and is in fact usable by all computers when
called from the Select Printer dialog box. I tested this myself to make
sure the driver wasn't the cause of the crash. Good idea, though... thanks,

John

David Kerber wrote:
>
> Were the printers all installed by a user with the same (probably
> administrative) privileges? It sounds to me like some kind of access
> restriction or permissions issue.

Sponsored Links