Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Set printer options

4 views
Skip to first unread message

Jack E. Wasserstein, DDS, Inc.

unread,
Oct 20, 2004, 8:35:13 PM10/20/04
to corel.wpoffice.paradox-dev

I have been experimenting with setPrinterOptions and getPrinterOptions to
simply print a form which is an envelope, without having to manually change
the settings in the printer dialog box. I may be spinning my wheels here but
when I view PrinterOptionInfo I can see that it accepts the changes I made
with setPrinterOption. However when the printer dialog box comes up
thereafter, the only parameter that is changed is the orientation. The
paperSource and size revert back to the default settings.

Any help or comments about this behavior is greatly appreciated.

Jack

Anders Jonsson

unread,
Oct 20, 2004, 8:54:18 PM10/20/04
to corel.wpoffice.paradox-dev

Jack,

Which version of Paradox are you using?

> I have been experimenting with setPrinterOptions and getPrinterOptions to
> simply print a form which is an envelope,

Are you really printing a paradox-form or do you mean a paradox report that
has the papersize as an envelope?

Anders Jonsson

Jack E. Wasserstein, DDS, Inc.

unread,
Oct 20, 2004, 11:59:40 PM10/20/04
to corel.wpoffice.paradox-dev

Paradox 10,

It is a form, not a report. but has the papersize of a 9.5 x 4.125.


"Anders Jonsson" <g...@takethisawaybredband.net> wrote in message
news:417702b0$1_3@cnews...

Bertil Isberg

unread,
Oct 21, 2004, 2:59:21 AM10/21/04
to corel.wpoffice.paradox-dev

Jack

Which of the three syntaxes for printerSetOptions() are you using?

1. printerSetOptions ( PrintOptions PrinterOptionInfo ) Logical
2. printerSetOptions ( var printerInfo DynArray[] AnyType [const
overRide Logical] ) Logical
3. printerSetOptions ( var printerInfo dynarray [] Anytype ) Logical


I would recommend syntax 2 or 3.

--
Bertil Isberg
CTECH
FAQ newsgroup: corel.wpoffice.paradox-faq
Paradox Buglist: http://w1.826.comhem.se/~u82608896/

remove spamfilter (reversed) to reply


Anders Jonsson

unread,
Oct 21, 2004, 3:09:37 AM10/21/04
to corel.wpoffice.paradox-dev

> Paradox 10,

Good.

>
> It is a form, not a report. but has the papersize of a 9.5 x 4.125.

What happens if you design a Report with that paperszie and use the new
syntax for print with the dynamic array reportPrintInfo? I haven't used the
diffferent papersize options myself but accordning to the help files it
should allow yo to set even a custom paper size.

Anders Jonsson

Jack E. Wasserstein, DDS, Inc.

unread,
Oct 21, 2004, 11:49:34 AM10/21/04
to corel.wpoffice.paradox-dev

Hi Bertil,

I tried both 2 & 3. I got it to work by creating a report from the form and
then printing the report. That took the settings from set printer options.
However, I was unable to get it to work just using the form. I will work
around it by creating the report. On that note, is there an easy way to
restrict the report to only one record? Is there a way i can operate on the
table supporting the report to restrict it to one record only using
something like SetRange(). This is simple on a form since i can work on a ui
object but that is not possible with a report. I know I can do a query and
base the report on that it would be simple enough but there must be a more
elegant solution.

Thanks,

Jack

"Bertil Isberg" <bertil...@retlifmapsSCB.se> wrote in message
news:4177583f$1_3@cnews...

Bertil Isberg

unread,
Oct 21, 2004, 3:55:47 PM10/21/04
to corel.wpoffice.paradox-dev

Jack

<<
On that note, is there an easy way to
restrict the report to only one record?
>>

You can run a query that selects that record, and open the report with the
answer table. Look at the report.open(reportopeninfo) and
report.print(reportprintinfo)

--
Bertil Isberg - CTECH
Paradox buglist:
online: http://w1.826.comhem.se/~u82608896/
FAQ newsgroup: corel.wpoffice.paradox-faq

Bertil Isberg

unread,
Oct 21, 2004, 4:18:34 PM10/21/04
to corel.wpoffice.paradox-dev

Jack

<<
I know I can do a query and
base the report on that it would be simple enough but there must be a more
elegant solution.
>>

I didn't see this before I replied.

IMO, running a query is an elegant solution. An alternate solution is to use
a dummy master table for the report. This master table, containing only the
keys for rows to be included, is linked to your real table(s). By inserting
and removing rows in the dummy table, you can control which records are to
be included in your report. And as it is possible to replace the master
table for report, you can open the report with the dummy table in :PRIV: so
every user gets a unique table to control the contents of the report.

0 new messages