Custom Crystal Reports for LBI that use Commands(sql)

 5 Replies
 0 Subscribed to this topic
 22 Subscribed to this forum
Sort:
Author
Messages
gsusnme
Basic Member
Posts: 5
Basic Member
    In publishing a custom report that has a command (sql) and parameters, in LBI, the parameter screen displays, and after choosing parameters it goes to a screen to put in default user id and default password, (which has been populated in the setup), and when you enter it again it goes back to the parameter screen, it's looping.  It's as if the custom crystal and the command(sql) are treated separate, but never mesh back together.  Any one have any ideas of how to handle this?  Or can LBI truly handle custom reports with this type of scenario?
    Chris Martin
    Veteran Member
    Posts: 277
    Veteran Member
      LBI functionality is not the issue. However, you may have an issue with your data source. Does the report run successfully from Crystal Reports on the LBI server?
      gsusnme
      Basic Member
      Posts: 5
      Basic Member
        Thank you for your response.  I am not the LBI administrator, author of the crystal. The administrator says it runs correctly on his pc. I will ask if he's ran it on the LBI server.   Also have another report, no command, use 2 tables, runs on the pc, produce a report, but the administrator can't get it to publish at all, just churns.  We are new to LBI so we don't know the do's and don'ts, if any limitations of custom crystals reports on LBI.
        Chris Martin
        Veteran Member
        Posts: 277
        Veteran Member
          What happens when you try to publish the other report?
          gsusnme
          Basic Member
          Posts: 5
          Basic Member
            We have been able to publish other reports and some with similar logic.  And they run ok. 
            jrbledsoe001
            Veteran Member
            Posts: 91
            Veteran Member
              I've seen this too with Crystal command reports.
              Check that RAS is running (when it doubt I bounce RAS). Make sure RAS has enough memory to process the report request.

              Depending on your version and hardware you may need to look at your server ODBC configuration (see RS User Guide p 114 small print about 32 bit ODBC driver for RAS).

              I've seen LBI loop back to the log on screen when a report contains complex Crystal selection formulas. Sometimes reports with complex select formulas won't refresh to screen in LBI with the view with data refresh command. For this reason I always move as much of the select formula as possible to the SQL command.

              Hope this help you eliminate what might be causing your issue!