1

Topic: Report crashes

Using the Report Wizard, I created a report with the following fields
Survey Name
Event Data
Event Location
Event Location Name
Event Spatial Reference
Taxon Common Name
Taxon Abundance Adult
Obs Source

Sorted by 1) Taxon Common Name and 2) Event Date

If this was run with just one species selected the report ran fine. However, if I tried to run the report with several species selected, the report crashed with an unhandled error. The exception message is "String or binary data would be truncated". Restarting or continuing the application makes no difference - i.e. very repeatable. Attached on the report which causes the crash

Post's attachments

test-rare.wzd 2.2 kb, 5 downloads since 2013-04-07 

You don't have the permssions to download the attachments of this post.
Harry Clarke
Surrey County Butterfly Recorder

2

Re: Report crashes

Sorry for the delay in looking at this. I suspect it is about the way one of the fields is  concatenated and is only occuring with certain data combinations.  Most likely  Taxon Abundance Adult or Obs Source. Could you see if it runs without taxon Occurrence Adult and /or Obs Source.

Mike Weideli

3 (edited by TeresaF 08-07-2013 10:11:05)

Re: Report crashes

I am having a similar problem - it is obs source that is the main issue although I think occasionally the comments field also causes it. I am yet to find any report wizard which returns a record with an obs source that works. I also get the same thing with XML reports. We have a lot of documents here (1500) and the obs source is a very useful field for reporting, so I'm finding this frustrating and would really appreciate any tips on how to fix it.

I first noticed the issue in March, now on 6.18 and it is still doing it. It is possible the update from 6.16.241 to 6.17.1 which we did in January was when the problem started and I didn't notice straight away.

-----------------
Teresa Frost | Wetland Bird Survey National Organiser | BTO
Other hat  | National Forum for Biological Recording Council
(Old hats  | NBN Board, ALERC Board, CBDC, KMBRC)

4

Re: Report crashes

Many thanks for investigating this. I can now duplicate it and can see that the field length in the Report_Field_table is too short for a complex source.  We will fix in release 6.20, but it can be fixed immediately in a number of ways depending on what access you have to the database,

In Sql Server tools the following query will fix 

Update Report_field set Field_size = 300 Where Report_Field_Key = 'JNCCDEV100000006'

Or you can go into the Report_Field_Table in SQL Server tools or in MS Access and change the Field Size for the Obs Source field from 100 to 300. 

Otherwise I can providea batch update which will make the change.

Mike Weideli

5

Re: Report crashes

Thank you very much Mike, I ran your query and it now works. :)

-----------------
Teresa Frost | Wetland Bird Survey National Organiser | BTO
Other hat  | National Forum for Biological Recording Council
(Old hats  | NBN Board, ALERC Board, CBDC, KMBRC)

6

Re: Report crashes

I have had several error reports lately. How do I send them to you?

Ron Elliott/VC45

7

Re: Report crashes

Initially create a new topic on the forum and give details brief of what has happened.  Include the version of R6 you are running.  You can attach the error report file to the post if you wish or if not keep it in case we need it.

Mike Weideli