OnDemand linked subreport in Crystal question

Does your subreport return more than 1 record for each record in the main report?

yes - it can return several records.

What version of LBI are you running?

we're running Reportin Services Version: (200905) 9-0-3-2-102 05 - is that what you mean?

Yes, that is what I was asking. Are your main report and subreport pointing to different datasources?

no - they have the same datasource

I thought most of the subreport bugs were resolved by version 9.0.2. Does it prompt you for the login credentials when it's not an ondemand subreport?

no - subreports that are not on-demand work ok. I partially put this out here to see if the issue was on my side or with the system. From your comments, it sounds like it may be a system problem. I've created a ticket for my local help desk on this.

Do you recall that prior to 9.0.2, subreports had issues including this type of log-on issue? Does my issue sound similar to those earlier issues?

I'm not 100% sure it's a bug, but it sounds like it.

Here's one thing you can try as a possible workaround: If you are using Override Datasources, try selecting "Use Report Data Source" and hardcoding the db credentials at the report level.

Honestly, I don't recall if I ever tested on-demand subreports on the pre-9.0.2 versions. I do recall, however, that there were significant subreport issues.

I don't have the option of hardcoding db credentials at the report level. I use an override data source set up for me by I.T. but the userid/password are then hidden from me. I need to use the override datasource so that the report will run when scheduled - since it won't run on the server under my own userid.

You could have IT hardcode db credentials for testing purposes. Hardcoding the credentials should not affect the scheduling results.

Just as an FYI follow-up on this, after working on this issue with I.T. for a while, we've found out that everyone can see this subreport ok without the login screen popping up - except for me - the report owner.  We're not sure what the issue is - perhaps it has something to do with the url, or maybe there's an LBI bug that only kicks in when the owner views the report.  Don't know at this point.