title: Missing Schemas in Crystal Reports
body: <p>A little bit of an odd issue here.</p>
  
  <p>I have a database, hosted on SQL Server 2008 R2 (SP2), that has 10 different schemas that could be used for reporting purposes:</p>
  
  <p><a href="https://i.stack.imgur.com/v4Awl.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/v4Awl.png" alt="SQL Server Schema List"></a></p>
  
  <p>Please note, for company compliance reasons, I did redact this image to the bare essentials.</p>
  
  <p>Now, when I go to create a report, and connect to the database in question, the only schemas that are presented to me are those starting with lm_:</p>
  
  <p><a href="https://i.stack.imgur.com/H9Kad.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/H9Kad.png" alt="Crystal Schema List"></a></p>
  
  <p>Again, redacted...</p>
  
  <p>Now, for the purpose of the report I need to build, I need to be able to select against tables that are in one of the ls_ schemas.</p>
  
  <p>My question is, in Crystal Reports 2013, <strong>how do I make all available schemas visible for use in a report?</strong></p>
  
  <p>Other important things to note:</p>
  
  <ol>
  <li>I am able to log into SSMS as the same account I am using to connect to the database in Crystal Reports, and am able to successfully run queries against the schemas in question.</li>
  <li>The account I am connecting to the database as, in both SSMS and CR, has full administrative access/capabilities against all schemas in the database in question</li>
  <li>Points 1 and 2 would suggest that this is not a security related issue</li>
  <li>I am connecting to the database in CR through an ODBC connection created on my system through ODBC Data Source Administration (32-bit) - as a System DSN</li>
  <li>The ODBC Data Source uses the same administrative account being used directly in CR and SSMS</li>
  </ol>
  
  <p>Thank you in advance for your help. Please let me know if there is any additional information that I can provide to help solve this issue.</p>