Although letter case is not important, for clarity, UPPER case will be used for the first letter of a word embedded in a picture script name. This will be used when pictures are amended only, to avoid creating unnecessary differences. Record names always have the first letter capitalized now.
The database name is followed by . and the last year digit and month of the change. This is shown in the picture script for plan detailBox.
Murray also supplied it as a self extracting exe file which you might like to use instead of the zip version - Elton55.612.exe
Elton55.612 6 changes from Elton55.611 in December 2006
1. New Census script validate for its Source.date in the lifetime of an individual that will only work on new records if the Source link has already been entered. If placed by default 2-way linking, this link only happens after the save is processed – after the validate
if individual present and source.date present then
if source.date<individual.birth.date
then source.date source.type"<birth" individual.birth.date | end
if source.date<individual.christening.date
then source.date source.type"<christening" individual.christening.date | end
if individual.death.date present and source.date>individual.death.date
then source.date source.type ">death" individual.death.date | end
if individual.burial.date present and source.date>individual.burial.date
then source.date source.type ">burial" individual.burial.date | end
end
2. Census filter (for copy and paste, but not add to scripts) to list errors:
individual present and source.date<individual.birth.date or
individual present and source.date>individual.death.date or
individual present and source.date<individual.christening.date or
individual present and source.date>individual.burial.date
3. Census script detailBox replace [|individual] by
[|datesLine(individual)]
[|"ERROR" validate()]
4. Person script validate
Replace if birth.date present
by if birth.date>1000
in order to ignore birthdays without year. The equivalent filter has been changed above in section 611. The full script with new ERROR and WARNING messages is now:
if burial.date present and burial.date < death.date then "ERROR burial<death"| end
if burial.date present and burial.date < birth.date then "ERROR burial<birth"| end
if christening.date present and christening.date < birth.date then "ERROR christening<birth"| end
if death.date present and death.date < birth.date then "ERROR death<birth"| end
if death.date present and death.date < christening.date then "ERROR death<christening"| end
if birth.date>1000 and birth.date < parents.marriage.date
then "WARNING birth < parents.marriage" parents.marriage.date | end
if christening.date present and christening.date < parents.marriage.date
then "WARNING christening < parents.marriage" parents.marriage.date | end
if mother.death.date present and mother.death.date < birth.date
then "ERROR mother.death" mother.death.date "< birth" | end
5. Person script detailBox
Add [| validate()] after treepar() in order to show errors and warnings above.
Remove | from [ treepar()] to avoid a blank line before parents.
Move | from front to back of
[ families()|] to separate the rest of personal detail from last child.
6. Marriage script detailBox
Add [|"ERROR" validate()] before [!”husband:”
If you install Elton55.612 then you can use PedClone to update your own DB by copying the following scripts from Elton55 to your DB:
| Person | Pictures | validate |
| detailBox | ||
| Plan pictures | detailBox {to makeDB= Elton55.612} | |
| Marriage | Pictures | detailBox |
| Census | Pictures | validate |
| detailBox |
Murray also supplied it as a self extracting exe file which you might like to use instead of the zip version - Elton55.611.exe
Elton55.611 5 changes from Elton55.610 in November 2006
1. occupation picture script ‘major’ had space and comma extra so remove the", " before end.
if not title contains ";" then title end
2. Person table ‘validation’ created for Person index filtered by any of these 3 filters which were split up to avoid problems with list filter sizes in Pedigree.
birth.date present and birth.date<parents.marriage.date or
mother.death.date present and mother.death.date<birth.date
christening.date present and christening.date<parents.marriage.date or
mother.death.date present and mother.death.date< christening.date
burial.date present and burial.date<death.date or
burial.date present and burial.date<birth.date or
christening.date present and christening.date<birth.date or
death.date present and death.date<birth.date or
death.date present and death.date<christening.date
The above filters have been limited to size of a filter acceptable to Pedigree if using PediTree before v3.310, otherwise they can be one filter joined by ‘or’.
3. The Person ‘validation’ table column 2 uses a new Person script called ‘validate’ which is also used when saving a Person edit. This is the script:
if burial.date present and burial.date < death.date then "burial<death" end
if burial.date present and burial.date < birth.date then "burial<birth" end
if christening.date present and christening.date < birth.date then "christening<birth" end
if death.date present and death.date < birth.date then "death<birth" end
if death.date present and death.date < christening.date then "death<christening" end
if birth.date present and birth.date < parents.marriage.date
then "warning birth < parents.marriage" parents.marriage.date end
if christening.date present and christening.date < parents.marriage.date
then "warning christening < parents.marriage" parents.marriage.date end
if mother.death.date present and mother.death.date < birth.date
then "mother.death" mother.death.date "< birth" end
4. Marriage table ‘validation’ created for list filtered by
husband.death.date present and husband.death.date<marriage.date or husband.burial.date present and husband.burial.date<marriage.date or marriage.date present and husband.christening.date>marriage.date or marriage.date present and husband.birth.date>marriage.date
Now for wife:
wife.death.date present and wife.death.date<marriage.date or
wife.burial.date present and wife.burial.date<marriage.date or
marriage.date present and wife.christening.date>marriage.date or
marriage.date present and wife.birth.date>marriage.date
The above have been limited by size of a filter acceptable to Pedigree if using PediTree before v3.310, otherwise they can be one filter joined by ‘or’.
5. The Marriage ‘validation’ table column 2 uses a new Marriage script called ‘validate’ which is also used when saving a Marriage edit. This is the script:
if husband.death.date present and husband.death.date < marriage.date
then husband.death.date "husband.death.date < marriage.date" end
if wife.death.date present and wife.death.date < marriage.date
then wife.death.date "wife.death.date < marriage.date" end
if husband.burial.date present and husband.burial.date < marriage.date
then husband.burial.date "husband.burial.date < marriage.date" end
if wife.burial.date present and wife.burial.date < marriage.date
then wife.burial.date "wife.burial.date < marriage.date" end
if marriage.date present and husband.christening.date > marriage.date
then husband.christening.date "husband.christening.date > marriage.date" end
if marriage.date present and wife.christening.date > marriage.date
then wife.christening.date "wife.christening.date > marriage.date" end
if marriage.date present and husband.birth.date > marriage.date
then "husband.birth.date > marriage.date" end
if marriage.date present and wife.birth.date > marriage.date
then wife.birth.date"wife.birth.date > marriage.date" end
PedClone procedure for 611 – copy these items to your DB instead of typing them in PediTree:
| Groups | ||
|---|---|---|
| occupation | Pictures | major |
| Records | ||
| Person | Pictures | validate |
| Plan pictures | detailBox | |
| Tables | validation | |
| Marriage | Pictures | validate |
| Tables | validation |
Murray also supplied it as a self extracting exe file which you might like to use instead of the zip version - Elton55.610.exe
Murray says "I should have sent version 602 and 603 before now, so they are not on PUGweb although they may be on CDROMs that users have received as upgrades. This zip or exe file will create an elton55.ped folder in the path that you specify (e.g.c:\pedigree), so do not include \elton55.ped yourself."
These are the changes from v601. The first one is most important. All of these can be applied together. There is no need to build them up and change Person PLANdetailbox to anything other than "DB=Elton55.610".
Elton55.602 one important change from Elton55.601 February 2006
Person script ‘BORN’ was changed wrongly in v601 and should be just:
if birth.date present then birth.date else christening.date end
Elton55.603 one change from Elton55.602 July 2006
Marriage script ‘wifeName’ to add prefix and title
wife.prefix wife.forenames
if wifeSurname present
then wifeSurname "M.S." end
surname(wife)
wife.postfix ["(" wife.nickname ")"] [";" wife.title]
if showrins=y then [" ^" wife.rin] end
life(wife)
Elton55.610 5 changes from Elton55.603 in October 2006
Murray also supplied it as a self extracting exe file which you might like to use instead of the zip version - Elton55.601.exe
Change scripts and remember to alter DB=Elton55.601 in Person PLANdetailBox, if you don’t just load Elton55 from CD or download. Then make a New DB from Elton55.ped and import your GEDCOM made from your old DB.
add title into cite(Source ) and a space after ref: to ease swiping filenames,
[|" source^"RIN type date title ["ref: "refnum]]
In Census list script insert ["at" source.place]
After Source.date so that the place of the census appear after “Mentioned in” Person detailBox.
Add a Person script called briefLine using
separator=”,”
name()
if birth.date present or christening.date present
or death.date present or burial.date present
then "(
if birth.date present
then brief(birth)
else ["bapt." brief(christening)]
end
if death.date present
then "-" brief(death) else ["-bur." brief(burial)]
end
")"
end
Then in Descendants Chart brief script, change 2 uses of datesLine to briefLine so that places as well as dates appear.
In datesline insert at the beginning separator=”,” which prevents extra lines when you have more than one event of the same type.
v3.291 was ready for mulitpage reports
Person Individual report changes to assist multipages for long notes or families.
Use Pedigree to change the report design as follows.
In the horizontal line called NOTES, delete it from home, Alt+B, end, Alt+B, Alt+D.
In the side lines, complete them by going above and below the new gaps with Alt+L to redraw the lines.
Put the cursor into area U and press F5. Alt+C to copy the picture.
Put the cursor into area T and F3. Cursor down until the area expands down to the bottom of the black area and Return to finish.
Similar changes to PersonPhoto and SourcePhoto report are best obtained by looking at an Elton55.601 download from PUGweb. The essential change is to ensure that the last text area (not the photo) is at a lower line than any other area, and contains the variable length text and repeated groups that cause truncated areas, so that it can be continued onto the next page at full width.
Space before \path\filenames by altering scripts for objects:
brief :date[" " file]
detail: date title [" "file] format
Note that from PediTree v3.292, you can prevent ages for dead people being shown by using the following picture script for BORN
if death.date absent and burial.date absent
or burial.date absent and death.date > today
or death.date absent and burial.date > today
if birth.date present then birth.date else christening.date end
Export GEDCOM v5.5 made more compatible with FTM and GED2HTML by changing the occupation OCCU script and residence RESI script by replacing “-“ by “AND” in the following phrase
"2 DATE "["BET"from"AND"]to
Murray also supplied it as a self extracting exe file which you might like to use instead of the zip version - Elton55.402.exe
Murray also supplied it as a self extracting exe file which you might like to use instead of the zip version - Elton55.310.exe
If you are making these changes to your own database:
Click Test button to save this change.
Remember to change the version DB=Elton55.310 in the Person script for PLANdetailBox,
and press test.
Elton55.zip contains version 305 of the Elton55.ped database used in PediTree version 3.270 or later. It can also be used in earlier PediTree versions, but will not give an option for GEDCOM v5.5 for which it was designed. However it has a number of other advantages.
Copy it to c:\pedigree - then expand it using Winzip (or whtever you use) and extract it to c:\pedigree\Elton55.ped
To use it in PediTree, export your database (using GEDCOM 4). Open the Elton55 database. Make a New DB from it with your name. In Edit mode, import your old GEDCOM just made, click Add, and wait while PediTree makes indexes (if you have v3.166 or later).
Person PLANLineDown picture script became:
if
treeMarriage.marriage.notes between " (" and ")" then "line=|" end
if
treeMarriage.spouse.treeRef contains "A" then "Color=red Width=2" end
v3.125 Note that treeMarriage. has been inserted before spouse.treeRef to Elton.101 and can be added by users to this script in earlier DB versions. It ensures that the line down appears correctly for multiple marriages of a person against the spouse carrying descendancy.
Marriage wifeName add brackets i.e.[" ^"wife.rin]to prevent ^ when no wife.
Links pictures added to Person, Marriage, Source and Census records.
To show the Census detail as a group in the Person record when imported
from 1881 Census Wizard from Barney Tyrrwhitt-Drake via GEDutils option 7:
Use Options Definitions Person to add census of type event.
To show
occupations as TYPE of event add 'type' in picture event detail to:
if
notes between "(" and ")"
then notes date type ["in" place]
else date
type ["in" place] notes
end
cite(source)
and in the picture
Person detailBox add in an appropriate place:
[| "Census"
detail(census)]
To ensure Pedigree puts marriage detail on a new line, replace the
following line in Marriage detailBox:
[|treedetail()]
by
| [treeDetail()]
Colour or emphasise wide tree lines for your ancestors or illegitimate descendants.
Delete the following line from Marriage detailBox picture because it is
already obtained from the treeDetail picture:
[|"div."div
detail(divorce)]
This affects the families picture used in Person detailBox and Person report named Detailed.
GEDutils v5+ allows you to import from a PAF3/4 or other system that exports its data the GEDCOM 5.5 standard. These may have notes records instead of notes fields CONC tags denoting concatenation instead of CONTinuation lines with carriage returns and level 3 tags into CONTs. Use option 7 to import the final .GED file into a Pedigree database based on the PAF3 made as follows, or your own that caters for the tags in the input GEDCOM file. Make a new empty database from Families called PAF3, and then type PAF3 This adds Note and Repostry (sic) records to the usual Person, Marriage and Source.
GEDCOM utilities database for importing a Census.ped exported database for creating tables, filed as documents and then converted to GEDCOM by PedGED55.exe for import to Family Tree Maker for Windows. It includes Census records as Individual Person Groups.