Do it right 100 times in a row and you never hear a thing, but do it wrong just once, and you hear about it FOREVER <:-) My thanks to all who have responded, both on and off the list, including Alfred who sent me a list of ALL taglines which are now "filed" away, and to Bruce for taking the time to straighten me out. I thank one and all, but you can stop the responses now. I think the problem is that I am home on a Friday, and I am very rarely home on any weekday, and I do "dangerous things" when I have extra time on my hands <G>. Thanks again to one and all. David *********** REPLY SEPARATOR *********** On 06/08/2001, at 12:05 PM, Alfred Eller wrote: >Evidentially we have everything fixed, except for David's wayward delete >finger <};-) > >Alfred <snip> MSgt David E. Cann, USMC (Ret'd) Phone: 540-372-7868 Fax: 540-372-7707 E-mail: decann@infi.net Family home page: http://homepages.rootsweb.com/~decann

Any chance there's a tool in FO for deleting a family and all it's descendants? I copied over a person and all descendants with spouses, without knowing how many individuals were involved. I should have specified only 2 generations and didn't. Now I have added 4,783 additional individuals in my database of 10,000 that I don't want there. (Yes, I could go back to backup but don't have one from the last week or so. Don't know how many other changes I could lose.) Ideas? Stan Harder Web page: http://www.smharder.com

"Stanley Harder" <stan@smharder.com> wrote: >Any chance there's a tool in FO for deleting a family and all it's >descendants? I copied over a person and all descendants with spouses, >without knowing how many individuals were involved. I should have specified >only 2 generations and didn't. Now I have added 4,783 additional individuals >in my database of 10,000 that I don't want there. (Yes, I could go back to >backup but don't have one from the last week or so. Don't know how many >other changes I could lose.) Ideas? > If you choose to select people to drag & drop to a new database; then you first mark everyone in the database and then highlight one of the persons you copied over and unmark everyone related to that highlighted person. This actually unmarks everyone in the tree which you just copied over, not necessarily just people related to that person. The people left marked that will be copied over to the new database should be only the ones that were in your database to start with. Wayne League