1 Topic by AndyFoy

  • AndyFoy
  • Consultant
  • Offline
  • Registered: 09-08-2006
  • Posts: 219

Topic: Custodian field set to NULL on NAME record

Hi

Recorder has been crashing recently when trying to open the Names & Address form.  On investigation it seems to be caused by a record in the NAME table that has a Custodian value of NULL.  Setting the Custodian value correctly has resolved the issue and enables the Name & Address form to open.  I don't know if this behaviour (Recorder crashing when NAME record Custodian value is NULL) is new or has always happened.

This has now happened 3 times over the last few weeks despite setting the Custodian value correctly for all NAME records each time it occurs.  So I suspected that these were new NAME records being created during a species import, or they were existing NAME records imported from another copy of Recorder.  However, the NAME record that was in error on the most recent occasion is a record that was first created in 2000 in the local copy Recorder, and it has not been updated since 2000.  So it appears something is setting the Custodian field to NULL for some reason.

Does anyone have any idea why this would happen?  Has anyone experienced anything similar?

Thanks
Andy

Andy Foy
Systems Manager
Greenspace Information for Greater London (GiGL) CIC
www.gigl.org.uk

2 Reply by charliebarnes (edited by charliebarnes 16-11-2016 14:13:28)

  • charliebarnes
  • Veteran
  • Offline
  • From: Greater Lincolnshire
  • Registered: 07-09-2008
  • Posts: 1,396

Re: Custodian field set to NULL on NAME record

That sounds like it's because of this in the latest release:

326 – The icons next to Locations, Individual and Organisations have been changed to indicate whether the Site is the custodian of the record.  A round icon indicates that site is the custodian of the record, or that the entry is system suppled.  A square icon indicates that it is not.  The purpose of this is to make it easier for users to choose the most appropriate Location, Individual or Organisation when matching or making selections during import.  This is for   use as a manual check only and does not restrict the selection. This option can be turned off (see Mantis 508).

Charlie Barnes
Information Officer
Greater Lincolnshire Nature Partnership

charliebarnes's Website

3 Reply by AndyFoy

  • AndyFoy
  • Consultant
  • Offline
  • Registered: 09-08-2006
  • Posts: 219

Re: Custodian field set to NULL on NAME record

Hi Charlie

Thanks for the info ... I wasn't aware of that new change (but I had noticed the icons).  So any idea why something would be resetting  a Custodian field to NULL?

Andy

Andy Foy
Systems Manager
Greenspace Information for Greater London (GiGL) CIC
www.gigl.org.uk

4 Reply by charliebarnes

  • charliebarnes
  • Veteran
  • Offline
  • From: Greater Lincolnshire
  • Registered: 07-09-2008
  • Posts: 1,396

Re: Custodian field set to NULL on NAME record

Fraid not - we've used Recorder extensively since updating (imports, manual adds etc.) and none of our NAMES are custodian-less.

Charlie Barnes
Information Officer
Greater Lincolnshire Nature Partnership

charliebarnes's Website

5 Reply by MikeWeideli

  • MikeWeideli
  • Administrator
  • Offline
  • From: Littlefield Consultancy
  • Registered: 05-07-2006
  • Posts: 2,645

Re: Custodian field set to NULL on NAME record

I suspect that 6.25 is highlighting something which went wrong in the past. It is a trigger on the table which sets the Custodian for new records so I don't think anything in 6.25 will change an existing Custodian. However the change in 6.25 is probably the reason for the errors as the assumption will be that all records have a Custodian.  Custodian didn't exist in the tables in 2000, so something could have gone wrong in the transfer of the data to R6.

Mike Weideli

MikeWeideli's Website