Jean: Exactly! Many of us start off by using Legacy just as it was designed--and it works very nicely that way. But often it isn't long before we begin tinkering with different uses for some of the fields in order to get a custom result, just as you're doing. Usually this is quite satisfactory, but I've crossed myself up once or twice by "bending" fields in the Source Writer templates. Sometimes it may help to post a query to the List about "Has anyone tried . . . " but that's not always foolproof since so many people use the software differently. The best course is to try an alternative and then test, test, test. One of the great things about Legacy is its flexibility.
Kirsten -----Original Message----- From: Jean Suplick [mailto:[email protected]] Sent: Thursday, November 25, 2010 6:05 AM To: [email protected] Subject: Re: [LegacyUG] Usage model for Legacy events Thanks, Kristen, Ron, Dennis and everyone! Yesterday, I spent most of the day experimenting with events based on the notion of using them as a way to arrange notes as desired in my report of choice. I get it now. There's the conceptual events model, based on the general ideas that drove its orignal inclusion in the Legacy software package. Then there's the software implementation of the events model, which turns out to have some very useful features that lots of people are exploiting so they can get their reporting just so, or so they can organize their research more intuitively. It was that second bit that was throwing me. So yesterday, since Individual Reports are what I'm after, I fooled around with adding events so that I could add notes that print up towards the top of the report. Excellent! It was just the ticket. My end goal was to have bits of topical commentary in my report, for instance, notes about why I settled on a particular birth date, or notes about the circumstances of why a family member died in Ohio as opposed to their home county in Pennsylvania. So I created events called "Birth notes" and "Death notes". In my opinion, these certainly are *not* events, so I'm breaking the conceptual events model. However, I'm exploiting the implementation model in the software. Thanks once again, everyone. Jean Suplick Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
