This is actually a very god idea. I found it usefull when exporting all people from the tree to excel. Whenever I do that I know ID is unique number and I can update people easily from my previous export.
yes, i agree unique ID is a must, but if i have entered say 100 people and say nex year m sister has a newborn - somehow i would like to make this newborn with ID somewhere in nearest range 10th, 2th, but definitely not 101st and after relatives of 5th generation... and it's a pitty it's not possible to change... :(
You have maiden name and name after marriage forwife.... adn what about husband... my example is just like that... :-) i have taken my wife's surname after marriage... so i am openly offering you to consider to add this option (married name for husband) with next update.
Rather than adding a field for Husbands maiden name, I would suggest adding a field that could be applied to either the husband or the wife, and call it "Legal name", or "Chosen Name".
Several of my female family members use different family names. One uses her maiden name, even though she is married, another uses a hyphenated name with her husbands name coming first. I have heard of some females using hyphenated name with the females name coming first.
I have another sister who still uses her ex-husbands last name, even though they are divorced. Her name is not shown correctly, no matter which naming preference I choose. If there were a field called "Chosen Name", the user could enter the name exactly as the person chooses to be called, and your software wouldn't have to figure out whether the person is married, divorced, hyphenated, etc.
...well "...hyphenated name with the females name coming first" you can meet this for e.g. in my native country Lithuania...
but i would say that a field with Husbands maiden name is neccesary (as per my own example). So, there are maiden names, the names after marriage and both being legal ones. Only then comes as you mention "chosen name". as "chosen name" it's not necessarily legal name, but rather as you have said "as person chooses to be called"...
In addition to the instances detailed in the previous messages, surnames for males (or females for that matter) change or evolve during immigration too. For example, my grandfather was born Czudek in Austria/Hungary but died Chudek in USA. So the idea to allow both birth names and other evolved names will be good. I also believe it is custom in Spanish heritage that the man takes the womans surname (if I recall correctly).
Dear MH Team, So couple of suggestion for FACTs tab in FTB: 1. Arrangement of facts: you have like only one arrangement option - by date. But not all facts may have date - what to do then? To addition: even if I save after arrangement by date, then close "edit information" an then enter again to facts tab - the facts are back to initial sequence they were before arrangement ... so what's the benefit of this if the option doesn't work...?... Per my opinion the best and most simple way if the numbers of facts (which by default are assigned in the sequence fact is entered) would be changeable manually. ...and savable of course :) 2A. There are groups of facts (common, birth, death, etc.) - per my opinion there should be a separate group called occupation or work or something like this. And this group can have facts like: occupation, profession, courses, probationary, practice and similar. 2B. if I choose particular group and then after particular fact, e.g. from group "Education" choose fact "education" I’ve expect that my selection will remain as it was done. But no, after I have done "save", reenter again to edit information and check the education fact, by some kind of default group "education" is converted to group "common". I would say this really needs tuning up... 3. Date for fact. E.g. I choose input with date selection "date within range". Entering figures, saving. When reentering - surprise surprise - it has become "date in free text". That shouldn't be like that, right? What do you think is it possible for you to initiate some purposive changes? BR Andrius P.S. myself I am Lithuanian. So, I do not know who has translated English to Lithuanian for you, but if the person is still in your Company you should reduce his salary ;-) ...as some things translated in the way you may think it was the person who doesn't know Lithuanian language... if you'll have interest and ask me I’ll be more than glad to help you to polish Lithuanian translation
as for the problem with the range of dates - I was not able to reproduce it. It would help if you could send me you project file to support (at) Myheritage(dot)com. You can find this file in My Documents \ My Heritage \ (your project name) \ Database
We will be happy to use your help in translation to Lithuanian. I have given your email to our Translation Department,
I would like to ask, if there is a possibility to add in your software a name-day option with auto notice in mails from myheritage.com?
And the second question I have is where I can display more than three generations in Family Tree Builder (Tree view like in your demo screen in the download part of your website)? It is very useful to see more than 10 people on one borad without switching a view.
Thanks a lot for reply and developing this software. It is the best I ever seen for genealogy research, of course, for free!
Thanks a lot for reply. I will be looking forward to the new features of My Heritage software. Is there a possibility to join MyHeritage developer team for example as translator to Czech, or something like this?
And when we can expect a new version of Family Tree Builder?
I started doing my heritagae search for my grand daughter who wanted to know where she comes from. Well her school project is over and I am moving forward with more searching. It would be wonderful if there was an option to add a flag from the country or origin to the first generation that (for me came to the US) emmigratedto my country. I am having a hard time remembering which person from which lineage was the first to get here. A visual aid would be awsome.
Thanks for letting me offer an idea, Kristin Butler : }