LBI/Crystal XI Failure to Process Prompt Error with Cascading Parameters

 2 Replies
 0 Subscribed to this topic
 22 Subscribed to this forum
Sort:
Author
Messages
Charlotte Chase
Basic Member
Posts: 8
Basic Member
    I have a Crystal XI report with a cascading parameter. The report  uses a SQL command rather than a stored procedure. Runs fine in Crystal, but when published in LBI the first prompt works, but I get a "Fail to process prompting" error on the second parameter.  If I get rid of the SQL command and pull in the tables directly, both parameters work  in LBI, but that just kills performance.  Has anyone had experience with this? Thx!
    Char
    Veteran Member
    Posts: 62
    Veteran Member
      Charlotte:
      Strangely enough, Charlotte here too. I have a client where I use XIR2 but one of the folks in accounting had this issue running one of my reports from Crystal Reports on a Crystal XI R1 machine that had no patches, I had him upgrade to XIR2 and he stopped getting the error. While it didn't happen on LBI, I know for a fact that LBI is R2 suggesting that a patch might be in order (or upgrade to R2 which is probably just as good if not better). Hope that helps!

      Char
      Charlotte Chase
      Basic Member
      Posts: 8
      Basic Member
        A belated thanks, Char. I will run it by my client. That is the only recommendation I've heard.