LBI/Crystal cascading parameters

 6 Replies
 0 Subscribed to this topic
 22 Subscribed to this forum
Sort:
Author
Messages
drhoades44
Advanced Member
Posts: 46
Advanced Member

    I have a report that has several parameters; two of them are Boolean. I set them up with descriptions so they don't just say True or False. If you use it for a while (in testing), when you click the drop-down, you don't just see my 2 descriptions, you see a list of True, False, True, False, etc. Screenshot attached.

    Has anyone else had this issue and did they find a resolution? Thank you.

    Matthew Nye
    Veteran Member
    Posts: 514
    Veteran Member
      first off, any particular reason your using Business Objects parameters and not LBI?

      second, your saying the the more you run the report hese values duplicate?

      can we get a screen shot of the properties of the parameters from the crystal designer?
      If any of my answers were helpful an endorsement on LinkedIn would be much appriciated! www.linkedin.com/pub/matthew-nye/1a/886/760/
      drhoades44
      Advanced Member
      Posts: 46
      Advanced Member

        I was told that removing the LBI parameters made it more attractive and that numeric input such as 9280, if using LBI parameters was 9,280 and if using Crystal parameters was 9280. The properties are attached in the zip file. And yes, the more I run it, the longer the drop-down lists get.

        Attachments
        Matthew Nye
        Veteran Member
        Posts: 514
        Veteran Member
          i would strongly suggest not using the @ in the parameter names. Special characters tend to mess things up.
          If any of my answers were helpful an endorsement on LinkedIn would be much appriciated! www.linkedin.com/pub/matthew-nye/1a/886/760/
          drhoades44
          Advanced Member
          Posts: 46
          Advanced Member
            I looked at this on Friday. SQL Server requires the @ symbol in their parameters but I take it that Crystal does not require the parameter names to match--from my somewhat brief testing. I didn't know how to reset the parameters or report to get rid of the cascading effect already there. Any thoughts??
            Matthew Nye
            Veteran Member
            Posts: 514
            Veteran Member
              No you dont need to conform to the database standards in the Crystal Report except in a Command or Database Expert.

              Try setting "Prompt with Description Only" to False.
              If any of my answers were helpful an endorsement on LinkedIn would be much appriciated! www.linkedin.com/pub/matthew-nye/1a/886/760/
              drhoades44
              Advanced Member
              Posts: 46
              Advanced Member
                It appears to be working. I set "Prompt with Description Only" to False and then back to True to reset it. The parameters don't appear to be accumulating any more. Thank you very much!!!