Problems using reportbuilder in Terminal Server 2003 with Powerfuse
Hi,
we use Reportbuilder under a Terminal server 2003 environment,
and as the standard windows shell we use Powerfuse. As soon
as reportbuilder wants to show the defaul printdialog, after a print
comand, we get an exception. It seems that reportbuilder can not get the
selected printer settings, because the PrinterName, PrinterType
and PrinterWhere values are all empty. PrinterType and
PrinterWhere show only the label component names,
lblPrinterTypeDesc and lblPrinterWhereDesc.
I can however select one of the printers using the PrinterName listbox
and print to this printer succesfully.
This only happens using the powerfuse shell. Any suggestions ?
OS : Windows Terminal Server 2003
SHELL : Powerfuse 6.03 editon 2003
greetings,
Rob Segerink
Novo-Wallco
we use Reportbuilder under a Terminal server 2003 environment,
and as the standard windows shell we use Powerfuse. As soon
as reportbuilder wants to show the defaul printdialog, after a print
comand, we get an exception. It seems that reportbuilder can not get the
selected printer settings, because the PrinterName, PrinterType
and PrinterWhere values are all empty. PrinterType and
PrinterWhere show only the label component names,
lblPrinterTypeDesc and lblPrinterWhereDesc.
I can however select one of the printers using the PrinterName listbox
and print to this printer succesfully.
This only happens using the powerfuse shell. Any suggestions ?
OS : Windows Terminal Server 2003
SHELL : Powerfuse 6.03 editon 2003
greetings,
Rob Segerink
Novo-Wallco
This discussion has been closed.
Comments
Have not heard of this before.Sounds like an initialization problem
somewhere. Make sure that the user account under which the application is
executing has full access rights to all of the printers.
Try modifying your Delphi library path from RBuilder\Lib to RBuilder\Source
and tracing the source code. The print dialog is created is ppProd.pas. The
printer code resides in ppPrintr.pas. The printer related code calls the
Windows API to get printer information. Much of this code is demand driven -
it is triggered by a request for printer information.
You may be able to programmatically access some of the Report.PrinterSetup
properties such as PrinterNames[], PaperNames[], etc. to get RB to
initialize the printer.
--
Nard Moseley
Digital Metaphors
http://www.digital-metaphors.com
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com