You don't need to do this with an array - that's the more complicated way of doing this!

Here's what I would do:

Formula 1 - put this in the report header section of the subreport:

WhilePrintingRecords;
Shared StringVar hazards := "";

Formula 2 - put this in the details section of the subreport:

WhilePrintingRecords;
Shared StringVar hazards;
if hazards = "" then
hazards := {HazardList.Name}
else
hazards := ", " + {HazardList.Name}

Formula 3 - Put this where you want the data to appear on the report:

WhilePrintingRecords;
Shared StringVar hazards

Note that there's no semi-colon at the end of this. If you put the semi-colon there, the value will not appear on the report.

I also do a couple of things in the main report when I work with subreports like this that only return a value for use in a report:

1. The subreport goes into its own section above where the data will be needed. I turn off the borders and turn off "Can Grow" under "Format Subreport..."

2. Make the height of the subreport as small as you can get it - I'll go to "Size and Position" on the right-click menu and set the height to something like .055 and the Y position to 0 so that the subreport is at the very top of the section.

3. Make the height of the section the subreport is in as small as you can. This way it won't really take up any space between the details sections on the report.

By doing it this way, you're not trying to fit a subreport into your data itself - you're just using a value generated by one.

Having said all of that, do you really need to use a subreport? If your report will only ever pull a very small number of rows, it's probably ok. However, every time a subreport is called in your report (in your case, for every row in the data) Crystal has to connect to and query the database for the data for that instance of the subreport. If you have a LOT of data, this will significantly slow the report down.

If you have the ability to create a stored function in the database (or have your DBAs do so) then I would create a function that takes whatever field you're currently using for the link to the subreport as an input parameter, queries the table for the values, and walks through the rows in the query to concatenate the values, which it will then return. You can then call this function in a SQL Expression in your report. The concatenated string from the SQL Expression can then be used in the same way that any field or formula in the report is used. SQL Expressions are evaluated by the database as part of the Select statement that pulls the data for the report. The database is more efficient at handling this sort of thing than Crystal is, so this will be MUCH faster than trying to do this in Crystal.

-Dell

What type of a section are you putting this formula in? If it's a details section, that's your problem. It won't display correctly unless it's in a group or report footer section.

Acutally... looking at this more closely, you need to put a semi-colon on the end of the formula. That way it will process in the details section but not display any values. You then put the third formula I gave you in a footer section to display the full value of the concatenated string.

-Dell

Edited by hilfy - 29 Sep 2014 at 8:44am