I received a gedcom for one of my family lines. I made a separate database, made a printout and checked it against my information in my database. When I came to a branch of the tree I did not have entered, I decided to drag and drop that branch. First I cleaned up all the place names. Then I dropped the head of the family and his descendants onto the same person in my database and merged them. Then I checked the new people in my database against the Decendancy report I had previously printed. All was well until I found a person who had a name, but no spouse or children. The printout had a spouse and children. When I investigated, the person's name was Jimmie and they had come in as male so Family Origins did not accept the spouse and children. What alerted me was that, in the printout, it said "he" married a person who obviously had a male name. I went back and changed the sex of Jimmie to Female and added her husband and her child manually. I was under the impression that, when things were imported, they came in as they were. I found it quite interesting that Family Origins would not accept in a drag and drop something it would not allow me to enter. I wonder if there is a difference in the drag and drop vs the gedcom. In gedcom, there is usually a list of things not accepted. If I had not checked my database (after the drag and drop) against the printout, I would not have known this family was not accepted. Betty

I think that there is something else at work here Betty. I edited a short GEDCOM so that one lady with a child became a male. I then imported it into FOW 9.02 with no problems, added another child to this ‘male’ and ‘his’ husband’s family. Then I created a new database and dragged that line of the family to it, everything came across just fine. I could not drag just one half of that family, then the other and then expect to re attach the two “males” as husband and wife though. Family Origins evidently does not check the sex of the spouses in a relationship when importing a GEDCOM, only when we try to enter them into the program individually. It seems that Bruce wrote that the “drag and drop” used a GEDCOM behind the scenes. I believe that anything you can export to a GEDCOM using FOW 9.02, you can expect to import into another FOW 9.02 without loosing any data, so there shouldn’t be any need for a “LST” file for dragging and dropping. In other words, I am trying to tell you that this is not a program fault, it ’s probably just another case of ‘operator error’ <};-) Good Luck, Alfred ============ ----- Original Message ----- From: "Betty Stokes" <jstokes@houston.rr.com> > I received a gedcom for one of my family lines. I made a separate database, made a printout and checked it against my information in my database. When I came to a branch of the tree I did not have entered, I decided to drag and drop that branch. First I cleaned up all the place names. Then I dropped the head of the family and his descendants onto the same person in my database and merged them. Then I checked the new people in my database against the Decendancy report I had previously printed. > > All was well until I found a person who had a name, but no spouse or children. The printout had a spouse and children. When I investigated, the person's name was Jimmie and they had come in as male so Family Origins did not accept the spouse and children. What alerted me was that, in the printout, it said "he" married a person who obviously had a male name. > > I went back and changed the sex of Jimmie to Female and added her husband and her child manually. > > I was under the impression that, when things were imported, they came in as they were. I found it quite interesting that Family Origins would not accept in a drag and drop something it would not allow me to enter. > > I wonder if there is a difference in the drag and drop vs the gedcom. In gedcom, there is usually a list of things not accepted. If I had not checked my database (after the drag and drop) against the printout, I would not have known this family was not accepted. > > Betty

I get FO238 errors when making a website from the database and wonder how to correct that. It comes up when making a rather large database of names, but the smaller databases make up just fine. Suggestions to correct appreciated. Thank you. Darci

238 errors are about the only ones I know anything about. They occur when FOW cannot find a graphics file to move to the website folder. Either you have moved or renamed it, or the name isn't one that is recognized by the web page editor. Any pictures that you have in the scrapbook, or the 'GIF' files that Family Origins uses for buttons or backgrounds that can't be found will cause this error. Now for the fun part, Trying to find which graphics are lost. I think some of the HTML editors will find which links are not working. I have Arachnophilia which will analyze a site to see which links aren't resolved. I know that it is a real job trying to find a bunch of these by going through the site and checking each link. Good Luck, Alfred ----- Original Message ----- From: "Darci" <djohn@netnet.net> > I get FO238 errors when making a website from the database and wonder how to > correct that. It comes up when making a rather large database of names, but > the smaller databases make up just fine. Suggestions to correct appreciated. > Thank you. Darci >