I am working on an existing (and large) report. It gets launched from a web app. I added a Stored Procedure in the database fields. The report runs fine with that addition. However, once I actually place one of the SP fields onto the report and try to launch it from the web app, the report dies without showing anything (no data, no headers, no labels... nothing).

Any ideas where I should be looking for the problem?






** Additional Info **

The Stored Procedure only has one parameter (that accepts a NULL), and I've tried every conceivable input for it.

We have many reports that were put together very similarly. They each have several CR Commands that bring the data in. Those Commands have links set up that bind the data between them. Most of the reports are also calling a Stored Procedure, which fills some report text fields. But the it is not repeated record data. These text fields are basically column headers for the data records.

In the reports that have this Stored Procedure, there are no links between the SP and any other data source. And there are no problems running those reports.

The report I'm working on does not have this SP. I would like to add it in order to maintain conformity across all our reports.

Currently, this particular report is bringing in those "column headers" via another CR Command.

Edited by PaulyWally - 20 Aug 2013 at 6:53am

OK. That would make sense if that's what's going on.

So since I have some other reports where this is working, do you have an idea of where I can look to find out where my report is not setup like the others?

Thanks!

It is not. Sorry. That is what I was trying (or failing) to explain in my first post. That SP has no links or joins in Database Expert, in any of the reports (working or not).

Edited by PaulyWally - 20 Aug 2013 at 8:10am

The web app is a database. And it has a customization feature that allows the user to rename GUI field labels in order to resemble their own verbage. For example:

Let's take the "Customer" form. There are 3 fields -
"First Name"
"Middle Name"
"Last Name"

Most users will leave it that way, and be happy. But some users might come along and would prefer:

"First Name"
"Middle Name"
"Surname"

The application allows them to change the "Last Name" field label to "Surname" (or whatever else they want). It doesn't change anything in the backend. Just what the user sees.

The Stored Procedure is used by the programmers so the field labels are reflected across every piece of the application. So when we put together a report (for example), we pull the label information from the SP, and the user will get their custom labels on the report.


In the report I'm having issues with, the field labels were hard-coded. So if a user makes those changes, they won't be reflected on the report. But there are other reports that are pulling and displaying data from the SP just fine.

Edited by PaulyWally - 20 Aug 2013 at 8:34am

It is only returning one record.