Crystal Reports Crystal Reports Formulas Ripplestone Tips

Delimited Crystal Reports Parameter Values

We have a Ripplestone client that has a report with a string value parameter that had values that were delimited so it could be any of the listed values.  This was then used within the Selection with a IN clause.

The values were surrounded with double quotes and then had brackets around the quoted values.  Below is an example:




The problem was that the double quotes would not work within Ripplestone since the double quotes would not work with the HTML Dropdown Box.  All that would be returned in the HTML would be the bracket (“[“) and nothing else.

We found with some testing that we could remove the Brackets AND the double quotes and the report would still work.  Below is the delimited list without the brackets and the double quotes.

40, 41, 42, 43, 44, 45


This worked in both the Crystal Reports designer and also when published to Ripplestone.

.csharpcode, .csharpcode pre
font-size: small;
color: black;
font-family: consolas, “Courier New”, courier, monospace;
background-color: #ffffff;
/*white-space: pre;*/
.csharpcode pre { margin: 0em; }
.csharpcode .rem { color: #008000; }
.csharpcode .kwrd { color: #0000ff; }
.csharpcode .str { color: #006080; }
.csharpcode .op { color: #0000c0; }
.csharpcode .preproc { color: #cc6633; }
.csharpcode .asp { background-color: #ffff00; }
.csharpcode .html { color: #800000; }
.csharpcode .attr { color: #ff0000; }
.csharpcode .alt
background-color: #f4f4f4;
width: 100%;
margin: 0em;
.csharpcode .lnum { color: #606060; }

General IIS Ripplestone Ripplestone Tips

How to Change the File Upload Size in Ripplestone

When you publish a Crystal Report file or document to Ripplestone you are moving the physical file from the local storage to the web server. Ripplestone has a default file size of 10 MB, so report files that are larger than 10 MB will not upload.

This size can be changed in the web.config file located in C:SitesRipplestone. The web.config file is an XML file that can be edited with any text editor or XML reader. Look for the httpRuntime section and change the maxRequestLength to whatever value you would like (1024 = 1MB).

Below is an example of the httpRuntime section with the default values that come with Ripplestone.

<!—Sets the max size for file uploads: 102400 = 10MB and 3600 = 1 hour –>

<httpRuntime maxRequestLength="10240" executionTimeout="900" requestValidationMode="2.0"/>

IIS Ripplestone Ripplestone Tips

Changing the Timeout Within Ripplestone

Ripplestone has a default timeout period of 20 minutes. If the application has not been used for 20 minutes, the session will end and the user will need to login again to continue. The default value can be changed by editing the web.config file located in C:SitesRipplestone. The web.config file is an XML file that can be edited with any text editor or XML reader. Look for the authentication section and change the timeout to whatever value (in minutes) you would like.

Below is an example of the authentication section with the default value of 20 minutes.

<authentication mode=”Forms”>

<forms name=”RSAuth” loginUrl=”SignOn.aspx” protection=”All” timeout=”20″/>


Crystal Reports Printers Ripplestone Ripplestone Tips Web Viewer

Printer Setting for Crystal Reports and Ripplestone

When publishing a Crystal report to Ripplestone, it helps to change the printer settings for the report to use the No Printer option.

When you create a new Crystal Report you normally set the report to print on a local printer.  While the report will run great for this printer it might not run when you publish it to Ripplestone and run the report using the web viewer.

A common message would be:

The page size was not large enough to format the contents of an object in the report.

Failed to export the report.

The reason for this error is that the web viewer has different margin and sizes that the printer that was selected and when the report is run it’s not able to fit in the new web viewer size.

To fix this problem open the Page Setup dialog box from within Crystal Reports and select the “No Printer (optimize for screen display)” option at the top of the box.  Save the report and make sure that it can be run without an errors.  If you get display errors then you can either change the margins on the Page Setup dialog box and/or change the layout of the report to fit within the new report dimensions.  After you get everything working in the report you can re-publish the report to Ripplestone and it should be able to be displayed in the web viewer and the pdf viewer.


Crystal Reports Ripplestone Ripplestone Tips

Truncating Fields in the Crystal Reports Web Viewer

The Problem

There are times when building a Crystal Report that you want a field to be short and if the data is too long for the field for it to be truncated.  This works fine when developing the report in the Crystal Reports Designer, but when you publish the report to Ripplestone and run the report the data in the field will overlap with the field(s) to the right. 

The screenshot below is from the Crystal Reports Web Viewer and the HTML that is generates allows the data to “spill-over” to the two fields to the right of the Title field.


What you want it to look like is this.  The screen shot below is the same report, but the viewer in Ripplestone was changed to pdf.  When exporting to pdf Crystal Reports does the proper thing and truncates the data in the Title field to the length that was set at design time.



The Solution

To fix the problem we need to head back to the Crystal Reports Designer and make a change to the field that is overflowing (the Title field in the example).  Open the Format Editor by right clicking on the field and selecting the Format Field option.  On the Common tab we want to check the Can Grow option and set the Maximum number of lines to 1.


After making the change to the report you can re-publish the report to Ripplestone and the field should be truncated and will fit the set width.  Below is the report in the Crystal Reports web viewer after the Can Grow option has been checked.




If you have a field in a Crystal Report that needs to be a specified width and cannot flow over to other fields and you need to view the report in the Crystal Reports Web Viewer you will need to set the Can Grow option along with the Maximum number of lines option.  Setting these two options in the Crystal Reports designer and then publishing that report to Ripplestone will cause the field to be truncated when displayed with the Crystal Reports Web Viewer.

Thanks to Patrick Kansa for help with this solution.

Crystal Reports Ripplestone Ripplestone Tips

Using Wildcard Parameters with Crystal Reports and Ripplestone

I have been working on the next version of Ripplestone and a client had asked about if and how Ripplestone will handle wildcard parameters in a Crystal Report.  I had not used wildcard parameters for awhile so I decided to dig in and build some reports with wildcard parameters and see how they worked when published to Ripplestone.

Creating the Crystal Report

For the report, I made a simple report that would have a parameter for a last name.  The report would use this parameter in the record selection and allow the user to enter wildcard in the format of “LY*” or “LY??” and have the report retrieve records for all the last names that either begin with LY or have four characters in the last name and they begin with LY.

To begin, I created the parameter with the settings to Allow custom values and Allow discrete values set to True.



Next I created the selection using the Select Expert and using the field called BillingLastName set the selection type to be “is like” and used the parameter called LastName as the value.



Running the report within Crystal Reports the user will get a parameter prompt and I entered the value of “LY*”.



The results from this simple report display all the records from the table where the last name begins with “LY”



Publish and Run the Report in Ripplestone

After creating the report in Crystal Reports, it is time to publish the report in Ripplestone and see how the wildcard parameters work.

Publishing the report was the same as any other report, select the report and give it a title click the Publish button.  Once the report was I clicked the Run Report link and got the parameter page.  The page prompts for  the last name and once again I entered “LY*” for the value.  Clicking the Run Report button will then pass the value to the report and the report will refresh the data for the report (in this case the data source was SQL Server) and display the report to the user within their web browser.


The report is returned as a pdf in the web browser.  The Crystal Report uses the wildcard parameter the same when running from Ripplestone as it does when running directly from the Crystal Report designer.


Crystal Reports Crystal Reports Formulas Ripplestone Ripplestone Tips

Converting Numbers to Dates in Crystal Reports

While working with a Ripplestone client today that had a Crystal Reports report that had data that was a date but the database stored the date as a number in the format YYYYMMDD (20090924 for example).  They wanted the date to be displayed in Ripplestone as MM/DD/YYYY (09/24/2009).

In their copy of Crystal Reports Designer they had changed the default number format to only display the number with no formatting.  They then used the following formula to convert the number into a date format:

Mid (ToText ({Database Field}), 5,2) + “/” + Right ( ToText({Database Field}),2) + “/” + Left (ToText ({Database Field}), 4)

This worked great when the number was 20090924, the formula split the number into the following 3 numbers 09, 24 and 2009 and then created the date by adding the “/” between the numbers.

The problem started once the report was published to Ripplestone and run.  The dates on the report were displaying as 90/00/20,0

After a lot of looking at the formula we discovered that the default number for the Crystal Reports Runtime Engine is to add commas and 2 decimals to the number, so that it was displaying as 20,090,924.00

When this was run with the formula, the 3 number were 90, 00 and 20,0.

To fix this problem we needed to remove the formatting from the number before the Mid, Right and Left functions were applied.  To remove the formatting of the number I added extra attributes to the ToText function.  The first attribute was the “#” as the second value.  This removes the commas from the number.  The next attribute was a zero (0) as the third value.  This will set the decimals to be zero and remove the “.00” from the end of the number.  The revised formula is below, with the changes highlighted in red.

Mid (ToText ({Database Field}, “#”, 0), 5,2) + “/” + Right ( ToText({Database Field}, “#”, 0),2) + “/” + Left (ToText ({Database Field}, “#”, 0), 4)

This allowed the number to be formatted correct and when the report was run or scheduled from Ripplestone the dates are displayed in the correct format.