To detect these and other possible but unlikely cases add the following Rows filters to the Query: Exclude unless %INDI.DEAT[1].NOTE2[1]% is null Exclude unless %INDI.DEAT[1].CAUS% is null Exclude unless %INDI.DEAT[1].SOUR[1]>% is null Exclude unless %INDI.DEAT[1].NOTE[1]>% is null Regards, Mike Tate -----Original Message----- From: family-historian-users-bounces@rootsweb.com [mailto:family-historian-users-bounces@rootsweb.com] On Behalf Of John James Sent: 18 October 2011 14:52 To: family-historian-users@rootsweb.com Subject: Re: [FHU] "He died" Hi George, Child fields hang off the field you're looking at. So, for example, if you had a local Note attached to the Death Event, or a Source, they would also be deleted, as there would then be no 'parent' field for them to hang off. HTH John From: family-historian-users-bounces@rootsweb.com [mailto:family-historian-users-bounces@rootsweb.com] On Behalf Of bush.lyme Sent: Tuesday, October 18, 2011 2:44 PM To: family-historian-users@rootsweb.com Subject: Re: [FHU] "He died" Thanks for that Jane. However, when I run the query and then try to delete the 1400 odd instances that it produces I get the warning " When a field is deleted, if it has any 'child' fields these will also be deleted." I apologise if I am being particularly obtuse, but I have no idea what this means. What exactly will I delete if I go ahead? George

I hope you are right about these cases being unlikely , Mike, because I have already run the original query. I suppose I could go back to yesterday's back-up copy and start again, but now I come to think of it, the chances of my having any of them without even an approximate date are pretty slim, so I don't think I will bother. Regards George