Create an index in a PDF file

Hi!!

I have a report that is exported to a PDF file... Is possible to get an index in the beginning of the file? I have the page number at the bottom of each page but i would need an index...

Thx in advance!!

Any idea? Isn′t possible to do it? At the moment, I havent found anything linked with this...|||

Hi Sergio,

Do you mean a document map? Check out this link: http://msdn2.microsoft.com/en-us/library/ms156383.aspx

|||

Hi Brad!!

not exactly... i would like to appear something similar but in a page in the beginning of the PDF document including the page number where each element is, i.e. the tables of the document... is there any option to do this? it′s very similar to the document map but with the page number...

I see two problems:

- I was thinking of using "=Globals.PageNumber" but i can′t, it says me that only can be placed in the header or the footer...

- and the other problem is setting the content of the document map in a page of the PDF... could I do this?

Perhaps, this is a bit difficult but I am always looking for challenges ... any suggestions? thx in advance!!

Sergio

|||I know of no way to accomplish exactly what you are looking for sorry to say. The document map links to items as repeated on pages. But I am not sure what you mean by "setting the content of the document map in a page of the PDF". If you mean as a page, there is no way to control this.|||

Hi Brad,

that was exactly i ment: i want to show it as a page, but if there is no way to do it... anyway, thank you for your help...

Sergio

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?
>
>