crashing excel when printing exported RS report

We are having a problem with some reports that get exported to excel and then
trying to print. we don't get this with all reports just some.
Here is what happens:
The report generates fine in RS. We then export to excel. We tell excel to
print and then get a 'Memory can't be read' error and excel crashes.
Whenever we want to just print a report as is, we export to PDF and print
that way. But many times the report is used in excel for further analisys
with other data. I have tried printing without touching the report in excel
and still get the error. So I know it is not something we added.
Because we are only getting this error with some reports and not all, I am
guessing that there must be something that was(n't) added to the report in RS
that would cause this.
Did I make enough sense to explain my issue?We are having the same problem with a couple of reports that were recently
modified. The modifications included adding a couple of additonal parameters
and then displaying the parameter values in the report footer. We already had
the report parameters displaying in the footer with no problems.
Our users are running Office 97 on WIndows NT worksatations. Our
deveoplment environment is running Windows XP with Office 2003 and the report
printing problem cannot be reproduced in the development environment.
Anyone had any luck with fixing this problem?
Ray
"David" wrote:
> We are having a problem with some reports that get exported to excel and then
> trying to print. we don't get this with all reports just some.
> Here is what happens:
> The report generates fine in RS. We then export to excel. We tell excel to
> print and then get a 'Memory can't be read' error and excel crashes.
> Whenever we want to just print a report as is, we export to PDF and print
> that way. But many times the report is used in excel for further analisys
> with other data. I have tried printing without touching the report in excel
> and still get the error. So I know it is not something we added.
> Because we are only getting this error with some reports and not all, I am
> guessing that there must be something that was(n't) added to the report in RS
> that would cause this.
> Did I make enough sense to explain my issue?
>
>|||We have finally solved this issue.
Our poblem was solved by reducing the amount of information in the report
footer. We display the users input parameter values in the footer to allow
them to print the parameters used when rendering the report. In our case we
had increased the number of parameters in the report and hence displayed in
the footer from 6 to 8. This caused Excel to crash when attempting to print
the export file. We have since reduced the parameters in the footer to 6
again and now the report prints in Excel.
Hope this may help you in finding the soucre of you printing problems.
"David" wrote:
> We are having a problem with some reports that get exported to excel and then
> trying to print. we don't get this with all reports just some.
> Here is what happens:
> The report generates fine in RS. We then export to excel. We tell excel to
> print and then get a 'Memory can't be read' error and excel crashes.
> Whenever we want to just print a report as is, we export to PDF and print
> that way. But many times the report is used in excel for further analisys
> with other data. I have tried printing without touching the report in excel
> and still get the error. So I know it is not something we added.
> Because we are only getting this error with some reports and not all, I am
> guessing that there must be something that was(n't) added to the report in RS
> that would cause this.
> Did I make enough sense to explain my issue?
>
>

CR XI Report printing in Landscape instead of Portrait

CR XI Report printing in Landscape instead of Portrait

Even though we specify the orientation of report in Crystal reports XI as Portrait during design time from report designer (i.e. File -> Page Setup), while printing it uses the default printer options i.e. orientation set to Landscape and prints the report in Landscape.

But the same report in Crystal report 7.0, when set to Portrait at design time from report designer, it print as set in the report designer i.e. Portrait and does not take default printer settings.

In Crystal Reports 7.0 have File -> Page Set up and File -> Printer set up options, using which the report orientation can be set, where as in Crystal Report XI has File -> set up options only.

Why is this wierd behaviour using CR XI ? Any idea.

We are using VB 6.0, Could the printer settings be supplied from VB 6.0 programmatically.

I would appreciate if anybody could help in this regard.

Thanks,try this found in crystal report samples.

Thanks

CR 8.5, dual monitor printing issues, delphi

Hi Guys,

We develop software in Delphi and Crystal Report 8.5 is used as reporting tool. Delphi's crystal component is used for coding.

I have a situation with a potential client. They have toshiba tecra m2 laptop which has GEForce FX 5200 video card which is dual monitor card. The OS is XP with SP2. When I click preview it is fetching data from the database and after that it hangs for ever neither displays view window or print. If the Harware accelaration is changed to 0 and Enable write combining is checked for this hardware properties the reports can be viewed and printed. But the client said these hardware properties are required for other applications on the machine.

Could any one help me resolving the issue? Is there any one have similar kind of problem?

Thanks in advance.

-KtuserThis behaviors can occur because of the 'Hardware acceleration' setting in Microsoft Windows. Reducing hardware acceleration on your computer will resolve these behaviors.

To access the 'Hardware acceleration' setting in Microsoft Windows, click Start > Settings > Control Panel > System > Display > Settings > Advanced > Troubleshooting.

There are typically six possible settings for 'Hardware acceleration': from 'None' to 'Full'. Reduce this value one setting at a time until the above behaviors are resolved.

The behavior of 'Enable write combining' has not been tested so not sure about it. Try the following along with the 'Enable write combining' checked and unchecked.