As far as the images go, if they are "Linked" to the location of where you are saving them, then that same location will need to be available to everyone that will be opening the rtf or doc files.
The best thing to do is have a separate folder that you can copy and provide to the other users. For an example, the Legacy file name is JonesFamily, I would have a subfolder under the same folder that the JonesFamily file is located in, named JoneFamilyImages. Now these reports can be made and using the same folder of images from the same subfolder of images. This way the Legacy file, and/or the reports that have "Links" to this subfolder can be copied to a CD, USB drive or other external devices and the images would be available to all who opened the files from the external device. This is one of the reasons I do not like that Legacy by default puts ALL of the images in the subfolder under the Program folder. Thanks, David C Abernathy Email disclaimers ---------------------------------------------------------------------------- This message represents the official view of the voices in my head. ---------------------------------------------------------------------------- http://www.SchmeckAbernathy.com == All outgoing and incoming mail is scanned by F-Prot Antivirus == -----Original Message----- From: Ellen [mailto:[email protected]] Sent: Saturday, May 25, 2013 11:14 PM To: [email protected] Subject: Re: [LegacyUG] Photos not embedded in the reports Cheryl, the User IDs are working fine. We just didn't want to have to delete MRINs that we pre-selected not to print. Our main issue is getting the photos and scans to show up in computers other than the one that the .rtf or .doc was produced on. The publisher will need to be able to see and print those photos. We hate the thought of having to embed each one manually. God bless, Ellen On May 25, 2013, at 8:13 PM, singhals wrote: > Ellen wrote: >> We are nearing the end of preparation of a book series on the family. It >> will be over 2500 pages and cover 23 different immigrant lines. However, we >> are noticing that photos only show up in the RTFs in the computer where we >> are initiating the reports. We cannot see photos in RTFs or DOCs that we >> load and bring back from Dropbox or from documents loaded onto a thumbdrive. >> It doesn't matter if we are doing this on the same or a different computer. >> We have check marked the option to embed photos, but it isn't working. We >> have hundreds of photos, have made zillions of modifications in the reports >> and cannot go back and rerun reports anymore. What other options can we do >> now? What other options can we do in the future? >> >> We found that we cannot use Word 2010 to do the reports because the files >> are way too large and Word stops responding and saving. We have to use Word >> 2003 or 2007. It would be nice for Legacy 8 to come out and upgrade to the >> newer Word. It doesn't matter if we are going between Word versions or >> using the same one. >> >> Would someone either respond publicly or privately to me. We are supposed >> to send the 23 lines and introduction to the publisher by the end of this >> week. >> >> Also we noticed that despite the fact that we checked to only include User >> ID numbers, the MRINS are showing up in the reports anyway. We have spent >> TONS of hours just removing the MRINs alone. Any idea how to get them not >> to show up in the reports? > > IME: if you want User IDs you'll have dele the MRINs manually. Better > also look at the index entries, because, again IME, they'll have the > RIN attached no matter what you've checked. My personal logic would > suggest that if the user wants User IDs, perhaps he'd like them in the > index as well, but apparently programmers don't see it that way. > > And, IME, Word2003 didn't distinguish itself by its behaviour trying > to edit a document about half the size of yours. If you can make it > behave for your doc, please send me off-list instructions, because I'm > going to have to do it again soon. :( > > Cheryl > > > > 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 > Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on > our blog (http://news.LegacyFamilyTree.com). > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > > 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 Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp 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 Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
