![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Anne Wainwright wrote: if printerSetOptions(prnOptions) then thisbuy.print(repInfo) else errorShow ("Could not set printer options.") endIf That is pretty much what I have, but I believe I only need to do both in one place. Been a while since I revisited this, though, so not certain. Long and short, it FEELS familiar and right. --------------- Tony McGuire |
#3
| |||
| |||
|
|
But that was version 5 and maybe it works better in later versions. |
#4
| |||
| |||
|
|
Hi all, (and best for 2009) I had to cure a problem of printing a report, the windows default printer driver would pop up each time and (on Pdox alone,and only late this past year) it decided to start with a postcard sized default paper size. No way to keep the default at A4 and clip-to-width set. Looking at the pdox examples I saw the PrinterOptionInfo type variable which allowed to set certain requirements, and the ReportPrintInfo type which allowed to set others, with some overlap. Neither would set all that I wanted. Yet the examples shown for each both concluded with print(varname). Thus I saw an either-or situation. I did quite easily get it to work, and my basic code structure is here var prnOptions PrinterOptionInfo repInfo ReportPrintInf0 ; other var items endVar ; set printer options showing overlap item and wanted item prnOptions.Orientation = prnPortrait prnOptions.PaperSize = prnA4 ; set report printing options showing overlap item and wanted item repInfo.orient = PrintPortrait repInfo.panelOptions = PrintClipToWidth ; lots of other code follows to generate report thisbuy.rsl if printerSetOptions(prnOptions) then thisbuy.print(repInfo) else errorShow ("Could not set printer options.") endIf ; more code thus I left the printerSetOptions as just set and 'printed' the repInfo ones. I didn't try it the other way around, but this seemed the 'right' thing to try. Well it works fine, but any comments welcome on this small matter. Is this the best approach, are the two variable each typically used under specific circumstances? regards Anne |
#5
| |||
| |||
|
|
Well it works fine, but any comments welcome on this small matter. Is this the best approach, are the two variable each typically used under specific circumstances? |
#6
| |||
| |||
|
|
Well it works fine, but any comments welcome on this small matter. Is this the best approach, are the two variable each typically used under specific circumstances? I think the version of Paradox is essential to the answer. In my experience there are som important differences how printing is handled in P7, P8 and P10 (the versions I have experience from). What works in one version might fail in another. I use P10 and the syntax with an array and it seems to work for me. |

|
Anders |
#7
| |||
| |||
|
Just to be awkward I am running version 9 ![]() |
![]() |
| Thread Tools | |
| Display Modes | |
| |