I used Legacy Search and Replace once. It caused me no end of grief. After that experience whenever I needed to I would load my fdb into MS Access to do major Search & Replace activity. It's much easier, finds things more reliably and I can see all the records that will be affected. And if I recall correctly Access has an undo which Legacy doesn't. I could be wrong about that though since it's been 4-5 years since I had to do it. At any rate I've made the decision, at least for now, just to use the Legacy output, run it through Ltools and make a few other mods within the html output. I've got my new site designed and I'm currently working on the mods to the Legacy html pages. As usual, css is causing me problems. It works fine with my other site pages but when I add css from my site css to the Ltools css the Legacy pages get all out of whack. So, I'm currently working through that. Does anyone know where I can get some whack? :-D
On Wed, Mar 25, 2015 at 10:21 PM, Cathy Pinner <[email protected]> wrote: > Gordon, > > Do you know you can do a Search and Replace within Legacy, which would > probably do the editing you want OR in the Gedcom in a text editor. > The Gedcom export also has some options to do with changing formatting > codes to html. > > Cath > > Gordon Small wrote: > > > TMG would be my preferred way for web presentation except for one > minor detail. I'm pretty sure my legacy output to a GEDCOM file would > not work. I started using Legacy back in the early days with the > intent of putting all the info on the web but legacy didn't have the > capability of outputting "everything" I wanted in their web page > generator, or it wasn't in the format I wanted it to be in. So, I > improvised and used a lot of HTML references in the person's "Events" > that I'm pretty sure won't translate in a GEDCOM export. The fi rst > time I decided that the Legacy web output wasn't doing what I'd hoped > I decided to improvise a way to get the output to display the way I > wanted it to display. Then I had to go back through the database and > revisit every person. I just don't have the desire to go back through > all my sources and events and revisit all my documentation *again*. > Actually, I'm happy with the Legacy output and while updating the web > isn't a one click event it only takes me a day or so to massage the > Legacy web output and get it uploaded. > > > > > 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://support.legacyfamilytree.com > 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://support.legacyfamilytree.com > 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://support.legacyfamilytree.com 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
