Issue with Running a Crystal Report -- Error Message

SUGGESTED

I am having an issue with a Crystal Report that I have pulling the data from the SQL replicated data.  The data pulls when I run the report in both Crystal Reports and also when I run from within Sage from any of our companies.  Upon having a user try and run the report, it works under 1 of the companies but they are receiving an error upon trying to run in any of the other companies. 

I would think if it was a parameter issue, it wouldn't work in any of the companies for any of the users, which is what is throwing me for a loop.

  • 0
    SUGGESTED

    Have you tried removing the quotation marks in your SQL statement? My understanding is that quotation marks are used to identify a string, so by putting quotation marks around your data field reference, I would assume that your formula is evaluating whether the exact string within the quotations on the left of the equals sign matches the string in quotation marks to the right of the equal sign, and those two quoted strings will never evaluate to true. By removing the quotation marks, your formula may actually compare the two data fields in your tables.

  • 0 in reply to Art Minds

    Art,

    The quotation marks were being entered just in the instance of the error message.  I've since went through and removed anything that had a formula within the Crystal and included the formula within the SQL query.  The user is now receiving the attached message.  It is very odd the fact that the user can run the report for one company but not others.  I've also had 2 other users with the same permissions try and run the report and they are able to run it for all companies.  It seems to be an issue with the one particular user.

  • 0

    I guess I hadn't read your original message as thoroughly as I should have. I would look at your security settings. Perhaps certain users lack security permissions for the companies where the report doesn't function. I would look at both company permission assignments as well as file level security settings for those users.

  • 0 in reply to Art Minds

    I think I may have figured out part of the issue.  Upon looking at her user on the SQL database side, the database role memberships were assigned matching Sage for the one company that was working.  For some reason within the other companies it was not.  The owned schema checkbox on the other companies is checked tying back to her user for some reason unlike the other users.

  • 0 in reply to Curtis Morrow

    Art, upon deleting these user schemas that were tied to the user and marking the correct database role memberships the report is now working for the user.  I'm not quite sure why it decided to create the schema for this particular reason when it hasn't been for other users.