Groups > dBase > dBase whish list > Re: Disabling print dialog box




Disabling print dialog box

Disabling print dialog box
Mon, 14 Apr 2008 12:15:37 -040
it would be nice if the print dialog box that shows when you render a report to
the printer can be suppresed. if you just want to produce a report to an html
file it would be nice if you could suppress the print dialog box.

Post Reply
Re: Disabling print dialog box
Mon, 14 Apr 2008 18:30:10 -040
Me Too.

"Agbeniga David" <agbenigadavid@yahoo.com> wrote in message 
news:KoYeGrknIHA.1516@news-server...
> it would be nice if the print dialog box that shows when you render a 
> report to the printer can be suppresed. if you just want to produce a 
> report to an html file it would be nice if you could suppress the print 
> dialog box.
>
> there are some procedure that i run that uses the classes that are also 
> exposed by a report object, sometimes you do not want the report but you 
> only want this process that are embedded into the report class to run. it 
> becomes absurd when this pprocess runs and the user see "printing
report", 
> in such an instance i will like to suppress the print dialog box 

Post Reply
Re: Disabling print dialog box
Mon, 14 Apr 2008 23:06:40 -040
In article <KoYeGrknIHA.1516@news-server>, agbenigadavid@yahoo.com 
says...
> it would be nice if the print dialog box that shows when you render a
report to the printer can be suppresed. if you just want to produce a report to
an html file it would be nice if you could suppress the print dialog box.
> 
> there are some procedure that i run that uses the classes that are also
exposed by a report object, sometimes you do not want the report but you only
want this process that are embedded into the report class to run. it becomes 
absurd when this pprocess runs and the user see "printing report", in
such an instance i will like to suppress the print dialog box
 

Agbeniga,

Put those "other processes" in their own .cc which can be called in
the 
report and elsewhere. When called from elsewhere, the "printing
report" 
will not be an issue.

-- 
Geoff Wass [dBVIPS]
Montréal, Québec, Canada

.|.|.|        dBASE info at http://geocities.com/geoff_wass       |.|.|.
.|.|.| ---------------------------------------------------------- |.|.|.
Post Reply
Re: Disabling print dialog box
Tue, 15 Apr 2008 12:40:05 -040
this is not the matter of a function or a procedure, im talking about you using
the pagetemplate's, detailsband's, headerband's or footerband's canrender of
onrender for example to generate a parallel text file to a report. in this case
you are using the iteration provided by these classes to achieve your objective,
i know you can acheive same using for endfor and do while, but why will i want
to write a process whose structure is already exposed by a report which i have
already written.

in this type of case i will want to run the report, use the iteration exposed by
its classes and the text in its classes to generate my text file. this is
extreamly useful in exporting reports to other formats.

Post Reply
Re: Disabling print dialog box
Tue, 15 Apr 2008 23:12:43 -040
In article <gKhEcdxnIHA.1096@news-server>, agbenigadavid@yahoo.com 
says...
> this is not the matter of a function or a procedure, im talking about you
using the pagetemplate's, detailsband's, headerband's or footerband's canrender
of onrender for example to generate a parallel text file to a report. in 
this case you are using the iteration provided by these classes to achieve your
objective, i know you can acheive same using for endfor and do while, but why
will i want to write a process whose structure is already exposed by a 
report which i have already written.
> 
> in this type of case i will want to run the report, use the iteration
exposed by its classes and the text in its classes to generate my text file.
this is extreamly useful in exporting reports to other formats.
> 
> this is the kind of case i mean not what you are refering to.
 

Agbeniga,

In that case, you will have to wait for the report to "finish" before

your application or the user can do the next task. Even if you don't 
want it, having the "printing" message is at least a bit useful in
that 
it shows something is going on.

If you really don't want it, you could experiment with the 
lockWindowUpdate to freeze the Window display while the report runs.

if type('LockWindowUpdate') # 'FP'
	extern clogical LockWindowUpdate(chandle) user32
endif

LockWindowUpdate(form.hwndClient)

// do your report
		
LockWindowUpdate(0)

-- 
Geoff Wass [dBVIPS]
Montréal, Québec, Canada

.|.|.|        dBASE info at http://geocities.com/geoff_wass       |.|.|.
.|.|.| ---------------------------------------------------------- |.|.|.
Post Reply
<< Previous 1 2 Next >>
( Page 1 of 2 )
about | contact