Larry,
There are some strange speed issue things sometimes especially with
large databases. There is discussion of one thing that helps in this
article. It's counter intuitive. Use less cores.
http://support.legacyfamilytree.com/article/AA-01072/9/Legacy-Family-Tree/If-Legacy-is-really-slow-try-this.html
Re dates in the search.
Just enter in the order you normally do. eg for 15 Jan 2001 I just enter
15 1 2001
That matches my region setting date entry.
With your search you don't give the connectors between your conditions.
I find it easier to use all AND or all OR or do two searches with the
second searching the search list. For some reason I can't get my head
around the logic of using the mix of AND and OR so it's quicker for me
to do two searches.
Cathy
Larry Lachance wrote:
I have attempted a “Detailed Search” using three conditions:
1. Individual; Given Name; Contains
2. Individual; Surname; Equals
3. Individual; Death Date; AFTER (tried specific date 15 JAN 2001 and
just a year 2001)
After 5 minutes I get “not responding” – Somehow I think I might need
to include the date in a specific format but don’t know what that
might be or even IF it needs to be.
How long SHOULD a search like this take (in excess of 190,000
individuals)?
I understand OS, RAM, and CPU have much to do with this however I note
that the machine is quite fast running Windows10 Pro with 64 Gb RAM
and Intel Core i7-8700K CPU which combined should be quite fast
enough. I have both the latest version of Legacy AND the latest
updates as well.
Thanks for any insight –
Larry
--
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]/
