If you would like to make a backup for your project on your computer you should do the following:

Please open your program, then open "file", choose "back up project", and then "back upto file on the disk".

Please pay attention to the place on your computer, where the file is saved.

Regards,

Isolda,

MyHeritage.com team

Hi Harold,

In Family Tree Builder you can import the following file types:

Photos: jpg, jpe, jpeg, bmp, gif

videos: avi, wmv, mpg, mpe, m1v, mpe, mov, qt, flv, mp4

documents: doc, docx, xls, xlsx, ppt, pptx, pps, pdf, txt, text, rft

audio:  wav, snd, aif, aifc, aiff, wma, mp3, aud, midi, mid

Best Regards, 

Esther / MyHeritage Team 

Esther:

Many thanks for your answer (partly) to my question. I do appreciate it.

However, this Dummy is unable to import a file which I saved in MS  Word in PDF format.

I am using the on-line version of the software rather than FTB, because I want other family members to be able to contribute.

I am working with articles a lot.  The way I did it until now is to store longer documents with pictures on my own server.  I compose the text of the actual article (usually quite short -- 30 lines or less) in MS Word using Arial 8 point fonts, then copy and paste the text into the window for composing the article.  The MyHeritage software is able to inherit most formatting from MS Word, such as font size and colors.  This also includes hyperlinks.  The family members are then able to read the long documents accompanying the article by clicking on the hyperlinks in the article.

What doesn't work yet is to include figures in the articles - they don't get copied correctly from MS Word, and also, you need to be careful with lists (numbered or bulleted), because they get inherited incorrectly.  When I use lists, I copy the text from Word up to the beginning of the list, then create the list directly in MyHeritage, copying each item separately.

The software for composing articles that MyHeritage offers still contains bugs, i.e., is much less robust and powerful than e.g. vBulletin, but  it's better than nothing.

--François

I am the administrator of the Cellier website (http://www.myheritage.com/site-members-129424911/cellier).  This website lists on the tree all people with Swiss roots that carry the name Cellier as well as their spouses, but not their parents and/or children who don't carry the name.  This restriction was introduced by me in order to prevent the tree from growing in an uncontrolled fashion.  I maintain the tree online, there are by now 71 site members, and they can all contribute to the tree.  The tree itself shows currently 820 people living between 1480 and 2011.

 One of the people shown on the tree is a Marianne Schreiber (born Cellier).  She is alive, but she is old, lives in a nursing home, and doesn't have access to a computer.  Hence she is not a site member.

Her daughter is Silvia Schreiber.  She is not shown on the tree since she doesn't carry the name Cellier.  yet, she is a member of the website.

I invited Silvia to the website some time ago.  A little while later, the MyHeritage software "decided" to merge the records of Marianne and Silvia into one.  Thus, I now have a member called Silvia Schreiber, whose profile points at her mother Marianne.

This morning I tried to fix the problem.  To this end, I temporarily added Silvia to the tree, then removed her from the website as a member, then invited Silvia afresh using the same email address.  Then I removed Silvia again from the tree.

This seemed to work for a while ... but two hours later, the two records were again amalgamated into one.

There seems to be a bug in the code.  Could someone, please, look at the problem?

--François Cellier

I did send an email to you with the requested information about a week ago or so.  Did you receive it?  Were you able to look into the issue?

--François

Thanks, Esther.  Your solution did the trick ... with a small caveat.

 I had tried something similar before, and it seemed to work at least for a while, but after about 2-3 hours, the two records magically merged again into one mixed record.

The problem, as I now discovered, was the following.  When the two records of Silvia and her mother merged originally (I still don't know why this happened), Silvia's record, which didn't have a birth date associated with it, inherited her mother's birth date.  Thus, a little while after I had untangled the two records, your software, too smart for its own good, recognized that there were two females with identical family names and identical birth dates ... and once again merged the two records into one.

This time around, I fixed Silvia's birth date,  and now the two records stayed separate as they should.

--François