Note that there are some explanatory texts on larger screens.

plurals
  1. POCrystal Report Not Showing Changes to Report
    primarykey
    data
    text
    <p>I've <em>inherited</em> an ASP.NET web application which displays reports using Crystal Reports. I wanted to add some new fields to one .rpt, but noticed that my changes were not being displayed when the report was called.</p> <p>Thinking that maybe my changes were to blame, I merely changed some label text on the original; yet my changes were still not reflected in the report displayed by the site.</p> <p><strong>I have tried:</strong></p> <ul> <li><p>Resetting IIS</p> <p>Moving/Renaming the .RPT file (<em>and the site is still able to load the old report</em>) This is mainly what leads me to think I'm confused here.</p> <p>Starting/Stopping the site</p> <p>Recycling the App Pool</p> <p>Deleting ASP.net temp files</p> <p>Setting Content Expiry on the rpt in IIS</p></li> </ul> <p><strong>I've only found one (unanswered) similar question <a href="https://stackoverflow.com/questions/337713/crystal-reports-in-asp-net-2-0-app-report-changes-not-showing">here</a>.</strong></p> <p>I don't know if maybe I'm just not understanding how the report is called, so here is the relevent portion of the code calling BookstoreReport.rpt.</p> <pre><code> else if (print=="bookstorereport") { BookstoreReport Report = new BookstoreReport(); foreach (CrystalDecisions.CrystalReports.Engine.Table myTable in Report.Database.Tables) { //connect to local db myLogin = myTable.LogOnInfo; myLogin.ConnectionInfo.DatabaseName="abc"; myLogin.ConnectionInfo.UserID="def"; myLogin.ConnectionInfo.Password="ghi"; myTable.ApplyLogOnInfo(myLogin); } CrystalReportViewer1.ReportSource=Report; } else if (print=="bookstorereceipt") *etc* </code></pre>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload