We have a web application developed using ASP that calls a Crystal report and attempts to print it to a printer selected by the user.
The printer is defined by name and the code used is as follows (this was done using VB but the code is in an ASP application and follows the same logic):
crxApp = CreateObject("CrystalRuntime.Application")
crxReport = crxApp.OpenReport(reportName)
crxReport.MorePrintEngineErrorMessages = False
crxReport.EnableParameterPrompting = False
crxReport.DisplayProgressDialog = False
crxReport.SelectPrinter(driverName, printerName, portName)
crxReport.PaperOrientation = 0
crxReport.PrintOut(False)
We have tried this against RDC v8/8.5/9 and have noticed the following problems:
1) If the printer is a local printer, the report will only print if the printer name and model name are the same as found the in the Windows Printer applet. If we change the name of the printer to something else, then nothing happens and there are no error messages.
2) If the printer is a network printer, nothing happens. No printing or error messages.
All this works if we use a VB application to call the report and print.
Any ideas or suggestions would be welcome.
The printer is defined by name and the code used is as follows (this was done using VB but the code is in an ASP application and follows the same logic):
crxApp = CreateObject("CrystalRuntime.Application")
crxReport = crxApp.OpenReport(reportName)
crxReport.MorePrintEngineErrorMessages = False
crxReport.EnableParameterPrompting = False
crxReport.DisplayProgressDialog = False
crxReport.SelectPrinter(driverName, printerName, portName)
crxReport.PaperOrientation = 0
crxReport.PrintOut(False)
We have tried this against RDC v8/8.5/9 and have noticed the following problems:
1) If the printer is a local printer, the report will only print if the printer name and model name are the same as found the in the Windows Printer applet. If we change the name of the printer to something else, then nothing happens and there are no error messages.
2) If the printer is a network printer, nothing happens. No printing or error messages.
All this works if we use a VB application to call the report and print.
Any ideas or suggestions would be welcome.