Toolbar is missing in Crystal Report Viewer (version 13)

asp.netcrystal-reportsvisual studio 2012

I am using the latest version of Crystal Report in my ASP.Net web application project. My IDE is Visual Studio Ultimate 2012 Version 11.0.6.

My problem is that when I run the aspx file that contains the Crystal Report Viewer, the toolbar is missing. Please see the attached image:
enter image description here

I already tried copying the toolbar folder to my root folder. I also tried hard-coding ToolbarImagesFolderUrl. I also tried copying crystalreportviewers from inetpub/wwwroot to my root folder. But nothing solved my problem.

Any suggestion?

Best Answer

It has to do with the default table css in Visual Studio 2012 projects. Remove the table, th, td, and tr stuff under tables and it will fix it. I just spent almost a whole day trying to figure out why it was doing this.

Related Solutions

Crystal report fails to load when application is deployed in IIS

I know this is an old post. but For anyone still looking for the answer:

You need to register crystal reports in page markup

<% @ Register Assembly="CrystalDecisions.Web, Version=13.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"
    Namespace="CrystalDecisions.Web" TagPrefix="CR" %>

Set the property 'Copy to Output Directory' of the report to 'Copy always'

the path of the file in the crystalreportsource will be ~/bin/YOURFOLDER/YOURFILE

<CR: CrystalReportSource ID ="CrystalReportSource1" runat ="server">
            <Report FileName="~/bin/oilmovement/rptOMDayEnd.rpt">
            </Report>
        </CR: CrystalReportSource>

Now the report should work

Backbone.save POST instead of PUT

According to Backbone documentation, saving a new model will result in a POST request, and saving an existing model (having an id) will emit a PUT request.

save model.save([attributes], [options])
...
If the model isNew, the save will be a "create" (HTTP POST), if the model already exists on the server, the save will be an "update" (HTTP PUT).

And if you are wondering if Backbone should use a POST for creation, check

PUT vs POST in REST
RESTful web services on Wikipedia

In the light of these articles, I'd say that, in the context of Backbone, the verbs are correctly used:

saving a new model causes a change in the system, a new URL is added, the action is not idempotent, it should be a POST,
saving a known model replaces a resource at a given URL, the action is idempotent, it should be a PUT.

Best Answer

Related Solutions

Crystal report fails to load when application is deployed in IIS

Backbone.save POST instead of PUT

Related Topic