How do I find out why I'm getting #Error in a textbox cell (no formula)

  • Sql Server 2008 SP3 - Using Report Manager for users to access and run reports.

    I have a couple of reports that produce #error in SOME of the textbox cells. These reports are pulling data directly from an odbc data source, no expression in the text boxes. Some of the numbers are showing #error instead of the value from the database. This only happens in our "production" environment. I have many other reports that work just fine in production, using the same data source.

    sample output from production:

    OEC amtfin vend deal term

    6529.92 6429.92 751.73 5678.19 36

    4432.91 4332.91 478.21 3854.7 13

    4793.28 4693.28 525.24 4168.04 33

    #Error #Error #Error #Error #Error

    22351.68 22101.68 2665.44 19436.24 60

    5815.57 5715.57 658.55 5057.02 33

    10691.57 10591.57 1294.39 9297.18 57

    6219.41 6119.41 711.23 5408.18 24

    2532.06 2532.06 244.74 2287.32 24

    If I run this in VS2010 (development environment), connecting to the production database, I get a perfect report. I deployed the report to our "test" server, also running 2008 SP3, and it works fine, connecting to the test odbc database (almost identical to production).

    As far as I can tell, the data is fine, so how do I find out what is causing this problem?

  • Do you have specific format applied to the cells? Just guessing but I'd be there is some kind of illegal character in the source data that is causing your format to cause an error.

  • There is no format on the cell, it is pulling raw data which is valid. As I said, it works fine using the IDE, pulling from the same database.

  • Would you have shared some screenshots, it would have been easier to comment.

    Would I have been in your situation, I would have simply recreated the matrix. There have been many many times when I have got problems fixed by recreateing the objects, specially in formatting or cosmetic issues.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply