Navigation problem

I have one report that uses "navigate" to another report through the data
region field. This works fine in the development environment (i.e. visual
studio), but when I deploy the reports and try it online on the live
environment, the 2nd report does not even open - i.e. goes to 2nd report
screen, but no report being generated and just blank report window. Nothing
happens.
I have SP2 on developer side, but not on server yet. Could this be the
issue? Other reports that use navigation (but created in SP1 development
environment) work.
Ideas?Does your production server has all the latest versions of your custom dlls.
--
Message posted via http://www.sqlmonster.com|||I found out that the problem is that the 2nd report must be runnable right
away, (i.e. cannot prompt user to enter any parameter values). Thus, I had
to give some parameters default values. This is not good. I am guessing,
using jump to URL would solve this problem, but is not a satisfactory
solution.
"Patrick P via SQLMonster.com" wrote:
> Does your production server has all the latest versions of your custom dlls.
> --
> Message posted via http://www.sqlmonster.com
>|||The intent of jump to report is to allow for drill through. You can map the
parameters of the second report to fields or parameters or really any
expression. You are right, you can use jump to URL if you are wanting the
user to fill in additional parameters. Not sure why that is not a
satisfactory solution. A little more work but after you have one jump to url
working the second time you do it is easier.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"bamboo" <bamboo@.discussions.microsoft.com> wrote in message
news:15945379-C022-4084-BF9C-15FF90133663@.microsoft.com...
>I found out that the problem is that the 2nd report must be runnable right
> away, (i.e. cannot prompt user to enter any parameter values). Thus, I
> had
> to give some parameters default values. This is not good. I am guessing,
> using jump to URL would solve this problem, but is not a satisfactory
> solution.
> "Patrick P via SQLMonster.com" wrote:
>> Does your production server has all the latest versions of your custom
>> dlls.
>> --
>> Message posted via http://www.sqlmonster.com