Cathy The mystery remains.
The Options 2.2 are all checked (I had not changed them; assume that is the default – and it suits me). Entering incorrect dates was not the problem – but as you point out, it’s easy to do – I’ve found myself putting married date instead of birth date on occasions. None of those errors contributed to my stated problem. This part of the branch of the history was collated by another person, in late 1999. It remains to validate much more from that Descendants File (I believe that it was created by “Brothers Keeper for Word”), as one of the re-entered children is obviously born too close to another. Legacy shows the problem, correctly. Of course that makes me suspicious of the rest of the data – but that is a separate issue from the problem that I encountered – and have now made disappear. I didn’t get to discover the sorting possible on the Childrens’ Settings, nor the global sort. I charged ahead and unlinked and then relinked. Before doing so, I closed Legacy, backing up to separate backups (not overwriting) each time, and reopened it some time later. 3 or 4 times. I wasn’t aware of how the .usr files are maintained. Having programmed and maintained Microsoft SQL Server and Access databases for a few decades, i would be hesitant to delete stuff without the developers’ OK (the lock file shouldn’t come into play anyway, as Legacy is always single-user afaik). Though I do have write caching problems with some software, that requires a forced memory flush – usually by refreshing Windows Explorer, F5: so let’s blame it on Windows :) Ian Thomas Albert Park, Victoria 3206 Australia From: LegacyUserGroup [mailto:[email protected]] On Behalf Of Cathy Pinner Sent: Wednesday, 3 August 2016 2:19 PM To: Legacy User Group <[email protected]> Subject: Re: [LegacyUG] Children problem Ian, On the Facebook Group you can add screenshots. So much easier. I think you are saying you've done a Check/Repair. If that's returning no problems, then you really do need to check Options. Options - Customise 2.2 is the one covering automatic sorting of children. But if visually they are in the right order in Family View in the Child Area, then that's probably not the problem. But do carefully check that you haven't inadvertently put 1986 instead of 1886 or 1800 instead of 1900 etc. It's so easily done. If the children really are in the wrong order, if you right click on a child on Family View and choose Children's settings OR click the little icon in the top left corner of the Family View screen, you'll find a Sort button on that Children's settings screen. There's also a global sort at Tools - Other Tools. It' s not the .ldb file that you'd delete! That is the lock on the database and usually deletes itself. The only time to think about deleting this file is if Legacy has crashed and when you start Legacy again, it says the file is in use - which means the .ldb file didn't get deleted. You do occasionally get PP alerts which vanish on exploring - but I've only seen it in the special events. Are these PP alerts persisting but still disappearing if you close and then reopen Legacy? If so, I'd go to /Documents/Legacy Family Tree/_AppData/usr/ and delete Probslist.usr and Rptprobs.usr All the usr files are your settings files. If deleted, they're just recreated when needed the next time you open Legacy. They sometimes get corrupted. Cheers, Cathy PS As you get more familiar with the program, it will stop being a hassle everytime you try to do something. :) Ian Thomas wrote: This might be easier t o show with a series of pictures, or a video – but I will try to describe the problem. Despite check repair, etc I have a problem with 9 children added with birth date (no death date) for all, in a single session of about 20 minutes. This is a simple family (no half-siblings, etc) and all born between 1884 and 1900, all marked as deceased. They show as for example, “birth date of child 4 is before birth date of child 3” – previously, I thought that the order in which children are added is not important, and I believe I saw that Legacy sorts them appropriately. When I click the red exclamation mark, to display the Potential Problems red explanation/warning description, the Potential Problems List window (a rather large one) pops up - but is empty - and immediately a messagebox (*Attention*) pops up over it, informing me that _there isn’t a problem_. I haven’t changed the “r ules” relating to births of children in any way, since starting to use Legacy v8 – I find it’s simpler to leave the defaults for many/most things (so, I’m happy to accept that 120 is a reasonable age for a life, rather than change it down to 99). And, as stated above, I have done the suggested repairs and do a new backup each time I quit. There are about 500 people in the database – a modest size. My only thought is to unlink all 9 from the parents, and link them back in again. But it’s worrying that (A) the program seems to think they should be in birth-date order as listed in the lower panel, and (B) the error that is generated is “dismissed” by the program itself as not real. I think there is some stuff-up in the Microsoft Access database, but I’m unwilling to delete .ldb files. Ian Thomas Albert Park, Victoria 3206 Australia
-- LegacyUserGroup mailing list [email protected] To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/[email protected]/
