title: Completely standalone RDLC reports
body: <p>Is it possible to design a completely standalone RDLC report?</p>
  
  <p>By that, I mean that the host application driving the ReportViewer control might pass in a connection string, but every other aspect (in particular, including the SQL queries) must be defined inside the RDLC file, with no predefined DataSets etc in the code.</p>
  
  <p>Essentially, what I'm looking for is something where the code knows how to connect to the database, but the report file is in complete control of which tables to fetch data from and how to join them.  So that you can drop a new RDLC file in without touching any of the code and it can report on completely different tables than any previous reports.</p>
  
  <p>Everything I can find about RDLC talks about making typed datasets or populating DataTables in code, which is not what I want.</p>
  
  <p>I did notice that there appears to be a <code>CommandText</code> value in the file, which seems promising, but I can't find any way to set this in the RDLC designer, nor does it appear to actually do anything.</p>
  
  <p>I'm sure I must be missing something fundamental here (for background, I'm most familiar with Crystal Reports, which behaves as I am wanting above).  I can't imagine how writing additional code could be a requirement to write additional reports.</p>