I get around this problem by referencing the file as a comment like
        "see genealogy\surname\1891Census\filename.jpg"
Not as convenient as a hyperlink, as that would take you directly to the file.
The problem with both my approach and hyperlinks will be on how a gedcom export 
will handle these references.  Gedcom does not like "\" in some fields and 
ignores them as if they did not exist.  I have no idea on what it will do with 
a hyperlink but you can be sure it will not work.
To expect it to work between genealogical software platforms is, I suspect, 
years away.

Alan

-----Original Message-----
From: Margaret & Evan Klatt [mailto:[email protected]]
Sent: 24 January 2013 22:57
To: [email protected]
Subject: RE: [LegacyUG] Can you embed a Hyperlink into Legacy

I have downloaded a large number of census and other pages so a link to 
individual pages would be useful.

The only downside I can see is that you would need to keep any subscription 
sites such as ancestry or findmypast up to date. If you stopped subscribing, I 
imagine you would 'lose' that page.

Evan

-----Original Message-----
From: Cliff Gittens [mailto:[email protected]]
Sent: Friday, 25 January 2013 7:16 AM
To: [email protected]
Subject: Re: [LegacyUG] Can you embed a Hyperlink into Legacy

Syble,

I'm inclined to agree with you that a clickable Hyperlink would be a useful 
tool.  Sure they may change in the future a risk we take.  I recently saw that 
Roots Magic offer the feature and I quite liked it.

Cliff Gittens





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


Reply via email to