As someone else said, and maybe I paraphrase too generally, we use what we're familiar with, what works for us. Personally, I HATE upgrades, what with the bugs in the initial upgrade releases, etc. I began with old DOS software from LDS years ago. Then, I wanted something compatible with Windows 3.1, then came Windows 5.0, and on and on it goes. But, for now, I'm satisifed to stick with what I have, even if it doesn't do everything I wish it could. I am grateful that some libraries provides several CDs of data files from several sources. It doesn't surprise me that as genealogy continues to grow exponentially as a hobby that more software and reprints and CDs flood the market, some of it with MY errors from early files. (Sorry about that). Still, I am not worried about Broderbund's or anyone else's patents, copyrights, or disclaimers. My research is MY research (as well as that of countless generous cousins) and I will publish whatever I please with it, and I will copyright that, even though some data cannot be copyrighted, only my publication of my thoughts and errors. I don't think I'm going to get an ulcer over paranoia about any software publisher's restrictions on uses of their software to collect, sort, collate, or otherwise manipulate what I produce. While I agree that there's perhaps too strong a profit motive for some publishers' uses of our collected data, I wouldn't expect it to be freely collected, indexed, and produced for me to use. They're not as bad, maybe, as some of the unprincipled types we've heard about who "steal" our data and publish it as their own, for profit sometimes. I am grateful - again - that some cousins have "found" me from my admittedly flawed files on some CDs. I do wish I had better response from some folks who provided their [also flawed] files years and years ago to the LDS folks. I'm glad to have it, but it's surely aggravating to see it, wonder where in the world they got their information, but not be able to contact them. Rant over. Back to your regularly scheduled programs... jim + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - James Wiley, AKA [email protected]