Changes

== The SELECT clause ==

== The SELECT clause ==

* The "Parents" column contains the parents' last names if the parents are in the database, and contains a portion of the Birth Event note if the Birth Event note appears to list the parents' names. If you don't intend to use the Birth Event note to store the names of in-laws, then you can replace the 4-line expression that uses cascading IF functions with just<br>

* The "Parents" column contains the parents' last names if the parents are in the database, and contains a portion of the Birth Event note if the Birth Event note appears to list the parents' names. If you don't intend to use the Birth Event note to store the names of in-laws, then you can replace the 4-line expression that uses cascading IF functions with just<br>CONCAT(d.lastname,' & ',m.lastname) as Parents

CONCAT(d.lastname,' & ',m.lastname) as Parents

* The "Spouse" & Marriage Date ("marrdate") columns generate multiple mostly-redundant rows in the report if there are multiple spouses.

*The "Spouse" & Marriage Date ("marrdate") columns generate multiple mostly-redundant rows in the report if there are multiple spouses.

* The "Tag" column indicates which cited event the query found.

*The "Tag" column indicates which cited event the query found.

* The "Place" column is the place associated with the Tag.

*The "Place" column is the place associated with the Tag.

* The Event note is the note associated with the Tag, and it is supposed to contain "GRid=nnnn" plus a description of the FindAGrave page.

* The Event note is the note associated with the Tag, and it is supposed to contain "GRid=nnnn" plus a description of the FindAGrave page.

* Citation fields: citetext and page. Remember that these are the only Citations data fields (that is, excluding the foreign keys to the sourceID and the personID/eventID that survive the Ancestry.com  >> FTM >> gedcom >> TNG interface.

* Citation fields: citetext and page. Remember that these are the only Citations data fields (that is, excluding the foreign keys to the sourceID and the personID/eventID that survive the Ancestry.com  >> FTM >> gedcom >> TNG interface.

* Source Title - which is really pretty useless. We really don't care which FindAGrave source is used.  In fact, I actually use my Gedcom Converter mod to merge all FindAGrave sources into one source titled 'FindAGrave.com'

* Source Title - which is really pretty useless. We really don't care which FindAGrave source is used.  In fact, I actually use my Gedcom Converter mod to merge all FindAGrave sources into one source titled 'FindAGrave.com'

* Why - This expression, made up of cascading IF functions, is intended to give the user (or more particularly, me, a sense of which error condition caused this record to be included in the query result.  This expression will only find one error condition, even if the record has several.

* Why - This expression, made up of cascading IF functions, is intended to give the user (or more particularly, me, a sense of which error condition caused this record to be included in the query result.  This expression will only find one error condition, even if the record has several. The error conditions it finds, in order, are:

The error conditions it finds, in order, are:

*# page: The Citation Page field does not contain a GRid number or is too short to include the GRID and the person's name.

*# page: The Citation Page field does not contain a GRid number or is too short to include the GRID and the person's name.

*# note: The burial or death event note does not contain a GRid number or is too short to include a description of the FindAGrave page.

*# note: The burial or death event note does not contain a GRid number or is too short to include a description of the FindAGrave page.