Hi Mike & Jan,
xcelsius is also a good suggestion.
@Mike, using the webelements library allows crystal reports developers to create launchpads, embedded control sections, etc. with crystal custom functions. i.e. one can create a new report that acts as a launchpad to one or many other crystal reports. the end output of all of the controls is an opendocument url. with the webelements functions, there is a builder function that takes all of the values from all of the controls referenced from the report and creates the url from that. so similar to your xc launchpad suggestion but with cr instead.
@Jan, reasons to use webelements vs. xcelsius may come down to things like licensing...webelements are custom functions in crystal and hence there's no additional licenses required. they are rendered in html so the file size served up by your cr server or bobj enterprise server are small. you can also view cr with webelements in ipad via ios browser...recommendation would be to design the report size for the device screen though as the dhtml viewer on ios browser doesn't auto size etc. with xc though a nicer looking launchpad can be created as the flash controls are more eye-catching.
if you do go the cr & webelements route my suggestion would be to do Mike's recommendation of a separate launchpad that hits your target report. if you do want to embed controls on the same report i would recommend having your controls on a main report and have your target fields etc. in a separate report which is an iframe on the main report. the iframe is a separate webelements control. there are examples of this in the "submit" sample in the main download.
cheers,
jamie