Hello all, The discussion of my proposal to split up the Wiltshire Lovelocks database was not very conclusive, and it would have been helpful to have a few more opinions. Many thanks to Jeremy, Robert and Graham for their useful comments. The solution I've adopted is somewhat of a compromise: I've split the Wiltshire database into three, as follows: - "Wiltshire Trees 1", which contains the Lieflock Line, the Wootton Rivers Tree and the Tangley Tree. There are indirect links (by marriages) between these trees, so it was natural to group them together. - "Wiltshire Trees 2", which contains the other established Wiltshire trees, namely: - The Lyneham Line - The Wroughton/Tidcombe Tree - The Ramsbury Tree - The Shrewton Tree - The Warminster Tree - The Wootton Rivers Tree 2 - The Lyneham Tree 2 - "Wiltshire Extras", which contains any remaining fragments and isolated families. The gedcom files have been redefined accordingly, and the three new gedcom files are available on the gedcom files page: http://perso.numericable.fr/~lovjames/family-history/lovelock/gedcom.htm These files will be updated when one of the corresponding databases is changed. So, for example, any new material affecting the Lyneham Line will be added to the "Wiltshire Trees 2" database, and the corresponding gedcom file will be updated. I don't envisage updating the "Wiltshire Extras" database, but this is not excluded if there are good reasons for doing so. If one of the fragments in this database is developed, it may be best to remove it and either add it to one of the other databases (and corresponding gedcom file) or start a new database (and gedcom file). I have preserved the old "Wiltshire and beyond" gedcom file, and it is accessible from the gedcom files database. However, this file will no longer be updated. It's not clear to me how many list subscribers actually download these gedcom files, or whether everyone is aware of the interest of them. So I've added some notes to the gedcom files page explaining briefly what a gedcom file is and how it can be used. Finally, I decided to discontinue support for the Ahn applet, which allowed one to browse the gedcom files. This tool performs a similar job to the PhpGedView tool, and I think that the latter is clearly superior in terms of visual presentation, structuring of information, etc. Furthermore, it is open source software which enjoys a considerable measure of support, so it continues to evolve and improve. Up to now only the Lieflock Line and the Wallingford Berks Tree could be browsed with the PhpGedView tool. However, I have now extended this to cover all the trees in the new databases, "Wiltshire Trees 1" and "Wiltshire Trees 2" (but not the fragments in the "Wiltshire Extras" database) as well as the Wallingford Berks Tree. At some time in the future I shall probably add further trees (e.g. other Berks and Hants trees). In order to facilitate use of the PhpGedView tool, I've added links for each established tree on the "Wiltshire Trees" page which take one to the individual at the head of the tree on the corresponding PhpGedView database (a new browser window is opened for this, so that you can continue to navigate the Lovelock Web site). I would be very grateful for any feedback on these changes (positive or negative) and any ideas which could improve the Web site. James