RootsWeb.com Mailing Lists
Total: 2/2
    1. Fw: Re: [Clooz] People database
    2. Patrick A Shaul
    3. Whoa, I thought Liz's answer was to the point and very polite. Without getting into a long discussion on how you would be able to make this work if you had the MS Access version of the software versus the standalone version, there really is no other answer. If the original person has the MS Access version, they could develop their own process over all of the databases, linking the various people tables and create reports when duplicates happen. But, without linking the people tables from each and every database, there is no easy solution. This is why I have one database for my genealogy data and one database for Clooz. The reporting will allow separation, when you add other organizational overlays (like multiple databases) you are asking for complexity that I would not want. Rick -------Original Message------- From: Phil Warn Date: 11/25/05 11:53:01 To: Clooz-L@rootsweb.com Subject: Re: [Clooz] People database Elizabeth, You may feel the need some time to review this answer. <vbg> It is not a very helpful answer to what I consider to be a very reasonable question. Your answer, smacks of granny sucking eggs, and looks remarkably patronising, even if that was not your intent. I will refrain from further comment, but ask that you re-consider your reply on another day. I hope you do not take umbrage at my view. Phil. At 14:22 25/11/2005, Elizabeth Kelley Kerstens, CG, CGL wrote: >This is not a glitch. Each database in Clooz is a completely >separate database. If you had two different genealogy program >databases, the same thing would happen. That's why you keep >different databases. If you want all the numbers not to duplicate, >you need to keep just one database. This is how databases operate. ============================== View and search Historical Newspapers. Read about your ancestors, find marriage announcements and more. Learn more: http://www.ancestry.com/s13969/rd.ashx

    11/25/2005 05:04:01
    1. Re: Fw: Re: [Clooz] People database
    2. Bob Clark
    3. I agree. I have always argued for a one-database approach. I don't think that Liz could have been any more polite, without going into a discussion of database theory, which is way beyond the scope of this list, and certainly not something that she has time for. Again, think ONE database. There is no advantage to multiples. At 11:04 AM 11/25/2005, you wrote: >Whoa, I thought Liz's answer was to the point and very polite. Without >getting into a long discussion on how you would be able to make this work if >you had the MS Access version of the software versus the standalone version, >there really is no other answer. If the original person has the MS Access >version, they could develop their own process over all of the databases, >linking the various people tables and create reports when duplicates happen. > But, without linking the people tables from each and every database, there >is no easy solution. This is why I have one database for my genealogy >data and one database for Clooz. The reporting will allow separation, when >you add other organizational overlays (like multiple databases) you are >asking for complexity that I would not want. > > >Rick > > > >-------Original Message------- > >From: Phil Warn >Date: 11/25/05 11:53:01 >To: Clooz-L@rootsweb.com >Subject: Re: [Clooz] People database > >Elizabeth, > >You may feel the need some time to review this answer. <vbg> > >It is not a very helpful answer to what I consider to be a very >reasonable question. > >Your answer, smacks of granny sucking eggs, and looks remarkably >patronising, even if that was not your intent. > >I will refrain from further comment, but ask that you re-consider >your reply on another day. > >I hope you do not take umbrage at my view. > >Phil. >At 14:22 25/11/2005, Elizabeth Kelley Kerstens, CG, CGL wrote: > > >This is not a glitch. Each database in Clooz is a completely > >separate database. If you had two different genealogy program > >databases, the same thing would happen. That's why you keep > >different databases. If you want all the numbers not to duplicate, > >you need to keep just one database. This is how databases operate. > > > > >============================== >View and search Historical Newspapers. Read about your ancestors, find >marriage announcements and more. Learn more: >http://www.ancestry.com/s13969/rd.ashx > > > >============================== >Find your ancestors in the Birth, Marriage and Death Records. >New content added every business day. Learn more: >http://www.ancestry.com/s13964/rd.ashx

    11/27/2005 06:40:02