PDF Export

Hi,
Currently the PDF Export Feature only exports the data that is shown in the
screen.
For Ex. I have a textbox and made its property "Can increase to accomdate
contents " to be false. When the report is renderd it shows 10 characters and
when exported to excel it shows all the 20 characters. but when exported to
PDF it shows only those 10 characters.
How can we make the PDF to show all the 20 characters
Thanks
EOn Jul 12, 2:02 pm, ERS Developer
<ERSDevelo...@.discussions.microsoft.com> wrote:
> Hi,
> Currently the PDF Export Feature only exports the data that is shown in the
> screen.
> For Ex. I have a textbox and made its property "Can increase to accomdate
> contents " to be false. When the report is renderd it shows 10 characters and
> when exported to excel it shows all the 20 characters. but when exported to
> PDF it shows only those 10 characters.
> How can we make the PDF to show all the 20 characters
> Thanks
Are you sure that the remaining 10 characters are not wrapping onto
another page? If they are, you can put the textbox control into a
rectangle control. If this doesn't help, you can either try setting
Increase to accommodate contents to true -or- I would suggest checking
for product updates for Adobe Reader and if you are using SQL Server
2005, make sure that you have SP2 installed as well. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant

Pathing Error: Subreport(s) could not be shown

Hi Folks
I have a working report with 5 additional subreports on my PC. Also, works
fine on the development server.
The issue is with PRODUCTION.
Our networking folks are disabling 127.0.0.1 and localhost in PRODUCTION.
Can anyone tell me if suppling the 'path' in the main report .rdl for all of
the subreports will fix the issue. Tried several permuations and have not
been able to have a subreport shown.
robjust doublechecked:
1. CAN deploy from VB.NET into the 'Home' directory in PRODUCTION and the
report/subreports work just fine :)
2. However, our 'normal' mode of operations is to copy the .RDLs from
DEVELOPMENT and upload them.
3. Attempting to deploy to any of the subdirectories/folders throws up an
authentication dialog.
4. My TargetServerURL: http://myproductionserver.here.mycompany.com/Reports
This needs to be something like:
http://myproductionserver.here.mycompany.com/Reports/thisapplicationreportsdir/reportnumber123
thanks
rob
"RobKaratzas" wrote:
> Hi Folks
> I have a working report with 5 additional subreports on my PC. Also, works
> fine on the development server.
> The issue is with PRODUCTION.
> Our networking folks are disabling 127.0.0.1 and localhost in PRODUCTION.
> Can anyone tell me if suppling the 'path' in the main report .rdl for all of
> the subreports will fix the issue. Tried several permuations and have not
> been able to have a subreport shown.
> rob|||sorry...
Finally, when deployed by hand (uploaded from .RDLs into where the reports
need to be) the subreports INDIVIDUALLY work just fine (so I'm pretty sure
it's a simply pathing related issue in the MAIN report).
Now, just how to modify the main report with the specific paths needed for
each subreport.
rob
"RobKaratzas" wrote:
> just doublechecked:
> 1. CAN deploy from VB.NET into the 'Home' directory in PRODUCTION and the
> report/subreports work just fine :)
> 2. However, our 'normal' mode of operations is to copy the .RDLs from
> DEVELOPMENT and upload them.
> 3. Attempting to deploy to any of the subdirectories/folders throws up an
> authentication dialog.
> 4. My TargetServerURL: http://myproductionserver.here.mycompany.com/Reports
> This needs to be something like:
> http://myproductionserver.here.mycompany.com/Reports/thisapplicationreportsdir/reportnumber123
> thanks
> rob
> "RobKaratzas" wrote:
> > Hi Folks
> >
> > I have a working report with 5 additional subreports on my PC. Also, works
> > fine on the development server.
> >
> > The issue is with PRODUCTION.
> >
> > Our networking folks are disabling 127.0.0.1 and localhost in PRODUCTION.
> >
> > Can anyone tell me if suppling the 'path' in the main report .rdl for all of
> > the subreports will fix the issue. Tried several permuations and have not
> > been able to have a subreport shown.
> >
> > rob|||Used the 'move' option to move all the reports to the proper location in the
SSRS tree.
The reports run just fine, however, this isn't the optimal way we want to
have to deploy our reports (preference is to upload the .rdls by hand).
rob
"RobKaratzas" wrote:
> sorry...
> Finally, when deployed by hand (uploaded from .RDLs into where the reports
> need to be) the subreports INDIVIDUALLY work just fine (so I'm pretty sure
> it's a simply pathing related issue in the MAIN report).
> Now, just how to modify the main report with the specific paths needed for
> each subreport.
> rob
> "RobKaratzas" wrote:
> > just doublechecked:
> >
> > 1. CAN deploy from VB.NET into the 'Home' directory in PRODUCTION and the
> > report/subreports work just fine :)
> >
> > 2. However, our 'normal' mode of operations is to copy the .RDLs from
> > DEVELOPMENT and upload them.
> >
> > 3. Attempting to deploy to any of the subdirectories/folders throws up an
> > authentication dialog.
> >
> > 4. My TargetServerURL: http://myproductionserver.here.mycompany.com/Reports
> > This needs to be something like:
> > http://myproductionserver.here.mycompany.com/Reports/thisapplicationreportsdir/reportnumber123
> >
> > thanks
> > rob
> >
> > "RobKaratzas" wrote:
> >
> > > Hi Folks
> > >
> > > I have a working report with 5 additional subreports on my PC. Also, works
> > > fine on the development server.
> > >
> > > The issue is with PRODUCTION.
> > >
> > > Our networking folks are disabling 127.0.0.1 and localhost in PRODUCTION.
> > >
> > > Can anyone tell me if suppling the 'path' in the main report .rdl for all of
> > > the subreports will fix the issue. Tried several permuations and have not
> > > been able to have a subreport shown.
> > >
> > > rob|||Rob,
Can I ask why you're not developing and deploying all your rdl's at
once, inside a single report project? It seems logical to keep
associated reports in the same "container", especially when you have 6
reports to keep track of.|||hi toolman
this is just how this company operates...
operations folks don't have access to/use any IDEs to deploy
in this case, I ended deploying this for them into production (Home
directory) and then had to use the 'MOVE' to move all reports.
not an ideal situation, but since I was the person who initially setup the
system(s), I still have access to them still. but typically, this would have
caused issues in this environment.
thanks rob
"toolman" wrote:
> Rob,
> Can I ask why you're not developing and deploying all your rdl's at
> once, inside a single report project? It seems logical to keep
> associated reports in the same "container", especially when you have 6
> reports to keep track of.
>