Yes, I agree with the pop up question to give the user the option to view additional field.
George in AZ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Geoff Rasmussen Sent: Tuesday, June 17, 2008 9:59 AM To: LegacyUserGroup@legacyfamilytree.com Subject: RE: [LegacyUG] V7: Accessed date for lumped US Census Entries - for Geoff Your experience below has given me what I think could be a good idea. You, and others have not noticed that there were more fields to be filled in. In our Merging feature, when comparing two individuals, if there are more events than will fit on the screen, you can scroll to view them. If you attempt to merge the two people without scrolling to see all of the events, Legacy pops up a statement saying "You haven't looked at all of the events yet. Would you still like to merge the people anyway?" What do you think about this idea - if you click on the Save button in the SourceWriter, but there are more fields that you haven't scrolled down to see, Legacy could pop up a statement/question about the additional fields. This may prevent us from not noticing the additional fields. Thanks, Geoff Rasmussen Millennia Corporation [EMAIL PROTECTED] www.LegacyFamilyTree.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gail Nestor Sent: Monday, June 16, 2008 8:01 PM To: LegacyUserGroup@legacyfamilytree.com Subject: Re: [LegacyUG] V7: Accessed date for lumped US Census Entries - for Geoff Thanks Dave! Man, I know it's getting pretty late bacause I just totally missed the scroll bar on my detail screen! Now it works perfectly!! It's really too bad the fields can't all fit on one page because I'll bet you that more people than just me are going to overlook this too. It might be worth it to try to reformat this a little in a future update. Geoff, I apologize for taking up so much of your time on this because I know you are very busy with other stuff right now. I think we will all really appreciate the hard work you have put into this source writer once we get used to using the input fields. I still would love it if you could share with us some of the practices you have used in converting your sources over. Do you update a single census master source for a single county and then convert all the detail associated with that new source, or do you work through all the master sources first and then work through the myriad details attached to them? This is just something that I'm sure would benefit many of us. You could sort of bring us along on your learning curve. Anyway, I can now go to sleep and dream about tomorrow's task ahead of me in converting at least some of my census sources. The output looks good to me now! Gail Rich Nestor Smyrna, Georgia www.roots2buds.net Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
