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.

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.

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.

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.