Re: [LegacyUG] line breaks in event detai

[I Macaulay]

Consider notepad (or equiv) as a filter, takes out the unwanted bits and leaves 
the text clean.
Ian This girl said she recognized me from the vegetarian club, but I'd never 
met herbivore.


Ian Macaulay   Carp, Ontario

Open at 10:AM   Close at 5:00 PM

45.2397 N long: 76.0991 W Elv 137 M UTM

    Don't Forget to Save the Stamps



  From: Cathy Pinner 
 To: legacyusergroup@LegacyUsers.com
 Sent: Tuesday, June 23, 2015 11:14 PM
 Subject: Re: [LegacyUG] line breaks in event detai

The only reason to go via Notepad or some other pure text editor is if you are 
getting results in Legacy you don't like.
Otherwise, no reason to at all.
You can't really see what Legacy has done with the paste until you save it.
I use Spartan - a paid version of FreeClips from M8 software. It captures 
everything you copy. You have the choice of pasting with or without formatting 
- and if you set it up with the txt button showing on clips and have set up txt 
to do the cleanup you need - it's just a matter of where you click.

Cathy

Adrian Purkiss wrote:


Purely possible loss of formating from word or strange formatting may
occur if you paste directly into Legacy. Notepad will show exactly how
it will format in legacy note field and will remove and unwanted
formatting codes. Re fonts, although notepad can display in various
fonts pasting into legacy will format in the font, setup in customise
fonts. You cannot have different fonts in notes from that setup in
customise fonts.

Adrian

Sent from my android device.

-Original Message-
From: BARTON LEWIS 
To: legacyusergroup@LegacyUsers.com
Cc: legacyusergroup@LegacyUsers.com, remotes...@wavp.co.uk
Sent: Tue, 23 Jun 2015 4:03 PM
Subject: RE: [LegacyUG] line breaks in event detail

What are the practical consequences of not using Notepad to paste text
into the comments/text field of a source cite? Previously, I copied
and pasted text directly from Word (which I had copied from a database
in Ancestry, for example). My reason for copying into Word first is
that I like to replace all hard carriage returns with semicolons so as
to take up less space on the page. Is there an impact on how the
comments/textappears in reports or when the gedcom is uploaded to
other websites? What is the "default" font and type size when pasting
from Notepad?
Thanks,
Barton
On Tue, Jun 23, 2015 at 02:06 AM, Adrian Purkiss wrote:

    For info only. Memo fields are where ms access store legacy type
    note fields. They have a very large capacity as opposed to normal
    fields which are restricted to a maximum of 256 characters. Memo
    fields can be set up as text only or rtf (richvtext format) which
    means they would support all word type formatting. Legacy appear
    to use the former setting hence the need to use a txt editor such
    as notepad. It is not a user settings but a setting used by legacy
    designers and programmers.

    Adrian

    Sent from my androiddevice.

    -Original Message-
    From: Barton Lewis 
    To: legacyusergroup@LegacyUsers.com
    Cc: remotes...@wavp.co.uk
    Sent: Tue, 23 Jun 2015 2:13 AM
    Subject: RE: [LegacyUG] line breaks in event detail

    Thank, Adrian. I noticed when I input or paste source text into
    text/comments that the font is not consistent. I will use Notepad
    from now on to paste my text from when entering in the
    text/comments field.

    Sorry I don’t know what the “memo fields†are.

    Barton

    *From:*a...@wavp.co.uk [mailto:a...@wavp.co.uk]
    *Sent:* Monday, June 22, 2015 3:37 AM
    *To:* legacyusergroup@LegacyUsers.com
    *Cc:* remotes...@wavp.co.uk
    *Subject:* RE: [LegacyUG] line breaks in event detail

    Legacy/Access store documents as txt but word is not a true text
    editor it is a docx/rtf editor. Notepad is a true txt editor. Very
    strange things can happen when posting from non txt to txt fields.
    It mainly happens vecause various formats/systems have different
    new line characters. CR/LF, CR, LF, LF, CR where CR is carriage
    return and LF line feed ascii codes. Sorry technical. Thus always
    best if having problems to go via notepad.

    Legacy, access can support RTF in memo fields. Have you looked at
    this?

    Adrian

    Sent from my android device.

    -Original Message-
    From: Barton Lewis mailto:bartonle...@optonline.net>>
    To: legacyusergroup@LegacyUsers.com
    
    Cc: remotes...@wavp.co.uk 
    Sent: Mon, 22 Jun 2015 4:14 AM
    Subject: RE: [LegacyUG] line breaks in event detail

    Thanks, Adrian. I really never use Notepad, but your technique of
    pasting into it and then pasting into Legacy worked great (line
    breaks were preserved). Is it standard to copy/paste text/comments
    from Word into Notepad before pasting into Legacy?

    Thanks again,

    Barton

    *From:*a...@wavp.co.uk  [mailto:a...@wavp.co.uk]
    *Sent:* Sunday,

Re: [LegacyUG] line breaks in event detai

[Cathy Pinner]

The only reason to go via Notepad or some other pure text editor is if
you are getting results in Legacy you don't like.
Otherwise, no reason to at all.
You can't really see what Legacy has done with the paste until you save it.
I use Spartan - a paid version of FreeClips from M8 software. It
captures everything you copy. You have the choice of pasting with or
without formatting - and if you set it up with the txt button showing on
clips and have set up txt to do the cleanup you need - it's just a
matter of where you click.

Cathy

Adrian Purkiss wrote:
>
> Purely possible loss of formating from word or strange formatting may
> occur if you paste directly into Legacy. Notepad will show exactly how
> it will format in legacy note field and will remove and unwanted
> formatting codes. Re fonts, although notepad can display in various
> fonts pasting into legacy will format in the font, setup in customise
> fonts. You cannot have different fonts in notes from that setup in
> customise fonts.
>
> Adrian
>
> Sent from my android device.
>
> -Original Message-
> From: BARTON LEWIS 
> To: legacyusergroup@LegacyUsers.com
> Cc: legacyusergroup@LegacyUsers.com, remotes...@wavp.co.uk
> Sent: Tue, 23 Jun 2015 4:03 PM
> Subject: RE: [LegacyUG] line breaks in event detail
>
> What are the practical consequences of not using Notepad to paste text
> into the comments/text field of a source cite? Previously, I copied
> and pasted text directly from Word (which I had copied from a database
> in Ancestry, for example). My reason for copying into Word first is
> that I like to replace all hard carriage returns with semicolons so as
> to take up less space on the page. Is there an impact on how the
> comments/text appears in reports or when the gedcom is uploaded to
> other websites? What is the "default" font and type size when pasting
> from Notepad?
> Thanks,
> Barton
> On Tue, Jun 23, 2015 at 02:06 AM, Adrian Purkiss wrote:
>
> For info only. Memo fields are where ms access store legacy type
> note fields. They have a very large capacity as opposed to normal
> fields which are restricted to a maximum of 256 characters. Memo
> fields can be set up as text only or rtf (richvtext format) which
> means they would support all word type formatting. Legacy appear
> to use the former setting hence the need to use a txt editor such
> as notepad. It is not a user settings but a setting used by legacy
> designers and programmers.
>
> Adrian
>
> Sent from my android device.
>
> -Original Message-
> From: Barton Lewis 
> To: legacyusergroup@LegacyUsers.com
> Cc: remotes...@wavp.co.uk
> Sent: Tue, 23 Jun 2015 2:13 AM
> Subject: RE: [LegacyUG] line breaks in event detail
>
> Thank, Adrian. I noticed when I input or paste source text into
> text/comments that the font is not consistent. I will use Notepad
> from now on to paste my text from when entering in the
> text/comments field.
>
> Sorry I don’t know what the “memo fields” are.
>
> Barton
>
> *From:*a...@wavp.co.uk [mailto:a...@wavp.co.uk]
> *Sent:* Monday, June 22, 2015 3:37 AM
> *To:* legacyusergroup@LegacyUsers.com
> *Cc:* remotes...@wavp.co.uk
> *Subject:* RE: [LegacyUG] line breaks in event detail
>
> Legacy/Access store documents as txt but word is not a true text
> editor it is a docx/rtf editor. Notepad is a true txt editor. Very
> strange things can happen when posting from non txt to txt fields.
> It mainly happens vecause various formats/systems have different
> new line characters. CR/LF, CR, LF, LF, CR where CR is carriage
> return and LF line feed ascii codes. Sorry technical. Thus always
> best if having problems to go via notepad.
>
> Legacy, access can support RTF in memo fields. Have you looked at
> this?
>
> Adrian
>
> Sent from my android device.
>
> -Original Message-
> From: Barton Lewis  >
> To: legacyusergroup@LegacyUsers.com
> 
> Cc: remotes...@wavp.co.uk 
> Sent: Mon, 22 Jun 2015 4:14 AM
> Subject: RE: [LegacyUG] line breaks in event detail
>
> Thanks, Adrian. I really never use Notepad, but your technique of
> pasting into it and then pasting into Legacy worked great (line
> breaks were preserved). Is it standard to copy/paste text/comments
> from Word into Notepad before pasting into Legacy?
>
> Thanks again,
>
> Barton
>
> *From:*a...@wavp.co.uk  [mailto:a...@wavp.co.uk]
> *Sent:* Sunday, June 21, 2015 7:08 PM
> *To:* legacyusergroup@LegacyUsers.com
> 
> *Cc:* remotes...@wavp.co.uk 
> *Subject:* RE: [LegacyUG] line breaks in event detail
>
> I believe it may be the pasting action that is causing the
> problem. If you paste the edited will into notepad does it format
> as you require. Make sure you have wordwrap turned off in notepad.
> If not correct in notepad then add returns there and then paste
> into legacy.
>
> Access by the

RE: [LegacyUG] Next problem - Unsupported format

[CE WOOD]

Quite obviously, if the error message says "unsupported format",  one would 
look in Help for "format". You would not look for "capacity".

Classic problem with Help files, no matter what the program.

CE

Date: Wed, 24 Jun 2015 10:54:35 +0800
Subject: Re: [LegacyUG] Next problem - Unsupported format
From: 2wi...@gmail.com
To: legacyusergroup@LegacyUsers.com

Adrian,
I have gone back over how the folders were originally name and I cannot get the 
path name as any more than 100 characters in total, right  from Z// etc  The 
file name was a simple Page 1 so it can't have been that. As I said - as soon 
as I moved and renamed the folder - no more messages and we were home and dried.
Today is another day and the sun is actually shining so I will tackle the other 
missing 19 media files in his tree and see what happens with those.
Have suggested to Sherry that some form of message should be placed in Help 
regarding unsupported format problems - that is the only place I would think of 
going and if it is not in there I would never have considered looking elsewhere.
Thanks for your help,
Marion
On 23 June 2015 at 22:32, Adrian Purkiss  wrote:
Marion Have had a look in the internal structure of the legacy (access based) 
database structure using ms access and the allowed file lengths are as follows. 
Path name maximum 255 characters plusFile name another 255 characters It should 
be flagged up to support that Legacy gives the most unhelpful error message if 
these lengths are exceeded. Adrian  From: marion wimsett 
[mailto:2wi...@gmail.com]
Sent: 23 June 2015 14:30
To: legacyusergroup@LegacyUsers.com
Subject: Re: [LegacyUG] Next problem - Unsupported format Hi Jenny,I think the 
problem is now solved - it wasn't the actual photos - it was the length of the 
file name (well that is the only thing I can assume). I fiddled a little more 
with the photos and nothing worked so I renamed the file into a shorter version 
than my husband had given in - and lo and behold Legacy accepted the pictures. 
I have not heard of Legacy having a length requirement on folder names but as 
it is now working I can only assume that is the answer.Thank you so much for 
the help and ideas - I will now see if that is the problem with the remaining 
19 pictures - another night for that though!!Regards,Marion On 23 June 2015 at 
21:23, Jenny M Benson  wrote:On 23/06/2015 13:32, marion 
wimsett wrote:As an aside I have even saved it as a different name - and still 
comes up with the same message.
I think I would try opening it in PhotoShop and saving it as, say, a TIFF file 
and see if that will open in Legacy.  If it will, try saving that TIFF again as 
a JPG and try that.

I presume it is not possible to re-create the file by re-scanning the original?


-- Jenny M Benson

Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages after Nov. 21 2009:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/
Archived messages from old mail server - before Nov. 21 2009:
http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
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/legacyusergroup@legacyusers.com/
Archived messages from old mail server - before Nov. 21 2009:
http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
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/legacyusergroup@legacyusers.com/

Archived messages from old mail server - before Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/

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/legacyusergroup@legacyusers.com/

Archived messages from old mail server - before Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/

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

Re: [LegacyUG] Next problem - Unsupported format

[marion wimsett]

Adrian,

I have gone back over how the folders were originally name and I cannot get
the path name as any more than 100 characters in total, right  from Z//
etc  The file name was a simple Page 1 so it can't have been that. As I
said - as soon as I moved and renamed the folder - no more messages and we
were home and dried.

Today is another day and the sun is actually shining so I will tackle the
other missing 19 media files in his tree and see what happens with those.

Have suggested to Sherry that some form of message should be placed in Help
regarding unsupported format problems - that is the only place I would
think of going and if it is not in there I would never have considered
looking elsewhere.

Thanks for your help,

Marion

On 23 June 2015 at 22:32, Adrian Purkiss  wrote:

> Marion
>
>
>
> Have had a look in the internal structure of the legacy (access based)
> database structure using ms access and the allowed file lengths are as
> follows.
>
>
>
> Path name maximum 255 characters
>
> plus
>
> File name another 255 characters
>
>
>
> It should be flagged up to support that Legacy gives the most unhelpful
> error message if these lengths are exceeded.
>
>
>
> Adrian
>
>
>
>
>
> *From:* marion wimsett [mailto:2wi...@gmail.com]
> *Sent:* 23 June 2015 14:30
> *To:* legacyusergroup@LegacyUsers.com
> *Subject:* Re: [LegacyUG] Next problem - Unsupported format
>
>
>
> Hi Jenny,
>
> I think the problem is now solved - it wasn't the actual photos - it was
> the length of the file name (well that is the only thing I can assume). I
> fiddled a little more with the photos and nothing worked so I renamed the
> file into a shorter version than my husband had given in - and lo and
> behold Legacy accepted the pictures. I have not heard of Legacy having a
> length requirement on folder names but as it is now working I can only
> assume that is the answer.
>
> Thank you so much for the help and ideas - I will now see if that is the
> problem with the remaining 19 pictures - another night for that though!!
>
> Regards,
>
> Marion
>
>
>
> On 23 June 2015 at 21:23, Jenny M Benson  wrote:
>
> On 23/06/2015 13:32, marion wimsett wrote:
>
> As an aside I have even saved it as a different name - and still comes up
> with the same message.
>
>
> I think I would try opening it in PhotoShop and saving it as, say, a TIFF
> file and see if that will open in Legacy.  If it will, try saving that TIFF
> again as a JPG and try that.
>
> I presume it is not possible to re-create the file by re-scanning the
> original?
>
>
> --
>
> Jenny M Benson
>
>
>
> Legacy User Group guidelines:
> http://www.LegacyFamilyTree.com/Etiquette.asp
> Archived messages after Nov. 21 2009:
> http://www.mail-archive.com/legacyusergroup@legacyusers.com/
> Archived messages from old mail server - before Nov. 21 2009:
> http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
> 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/legacyusergroup@legacyusers.com/
> Archived messages from old mail server - before Nov. 21 2009:
> http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
> 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/legacyusergroup@legacyusers.com/
> Archived messages from old mail server - before Nov. 21 2009:
> http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
> 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/legacyusergroup@legacyusers.com/

Archived messages from old mail server - before Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/

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

Re: [LegacyUG] Next problem - Unsupported format

[marion wimsett]

Hi Bob,

Just a quick note to let you know that I use Photoshop for all of my photos
and never have any problems. This time I hadn't used Photoshop until I had
the message come up, then I did my usual changes on Photoshop, saved it in
it's original name. and then saved it in a new name.
I tried to open both photos in Legacy, even tried adding Media but each
time it came up with the same message.
It wasn't until I changed the folder name did Legacy then accept all 15
photos in the folder without a problem!!

Thanks for the suggestion though.

Marion

On 23 June 2015 at 21:34, Robert57P_gmail  wrote:

> Or try opening it in some other program (MS-Paint) and saving it as a
> new file.  Maybe Photoshop is putting in some tag that Legacy doesn't
> like - using paint I believe strips off all tags.   If you have some
> other program besides paint and Photoshop, you may want to try that one
> also.
>
> Bob
>
> On 06/23/2015 09:23, Jenny M Benson wrote:
> > On 23/06/2015 13:32, marion wimsett wrote:
> >> As an aside I have even saved it as a different name - and still
> >> comes up with the same message.
> >
> > I think I would try opening it in PhotoShop and saving it as, say, a
> > TIFF file and see if that will open in Legacy.  If it will, try saving
> > that TIFF again as a JPG and try that.
> >
> > I presume it is not possible to re-create the file byre-scanning the
> > original?
> >
> > --
> > Jenny M Benson
> >
> >
> > Legacy User Group guidelines:
> > http://www.LegacyFamilyTree.com/Etiquette.asp
> > Archived messages after Nov. 21 2009:
> > http://www.mail-archive.com/legacyusergroup@legacyusers.com/
> > Archived messages from old mail server - before Nov. 21 2009:
> > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
> > 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/legacyusergroup@legacyusers.com/
>
> Archived messages from old mail server - before Nov. 21 2009:
>
> http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
>
> 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/legacyusergroup@legacyusers.com/

Archived messages from old mail server - before Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/

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

Re: [LegacyUG] Next problem - Unsupported format

[marion wimsett]

Sherry,

I looked in the Help file for "unsupported formats" - which to me seemed
the obvious thing to do - and there was nothing there. I looked at the help
items for Photos and nothing was there that seemed to answer the problem. I
would not even have thought of looking elsewhere or looking under "Program
Capacities" - I wasn't considering it was anything to do with capacity only
an error with the format. Perhaps something should be added into the Help
section as I am sure than this has not just happened to me alone.

Thank you for the information though.

Marion

On 24 June 2015 at 04:27, Sherry/Support 
wrote:

> You don't even need to do that - in the Help file, on the right pane when
> you first open it up, is a list of Program Capacities, which show general
> capacities and field capacities.
>
> It's also on the website under Legacy > Features
>
>
>
> Sincerely,
> Sherry
> Technical Support
> Legacy Family Tree
>
> On Tue, Jun 23, 2015 at 7:32 AM, Adrian Purkiss  wrote:
>
>> Marion
>>
>>
>>
>> Have had a look in the internal structure of the legacy (access based)
>> database structure using ms access and the allowed file lengths are as
>> follows.
>>
>>
>>
>> Path name maximum 255 characters
>>
>> plus
>>
>> File name another 255 characters
>>
>>
>>
>> It should be flagged up to support that Legacy gives the most unhelpful
>> error message if these lengths are exceeded.
>>
>>
>>
>> Adrian
>>
>>
>>
>
>
>
> Legacy User Group guidelines:
> http://www.LegacyFamilyTree.com/Etiquette.asp
> Archived messages after Nov. 21 2009:
> http://www.mail-archive.com/legacyusergroup@legacyusers.com/
> Archived messages from old mail server - before Nov. 21 2009:
> http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
> 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/legacyusergroup@legacyusers.com/

Archived messages from old mail server - before Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/

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

RE: [LegacyUG] Next problem - Unsupported format

[Adrian Purkiss]

Sherry



Quite possibly if you know it’s there and what it’s called. For me a quick zip 
in the database and check. I have been using/designing/supporting multi-user 
access for more years than I care to remember. Useful for others though. Field 
sizes would be a better title than capacities. Just an observation.



That error message needs looking at though.



Regards



Adrian

From: Sherry/Support [mailto:she...@legacyfamilytree.com]
Sent: 23 June 2015 21:27
To: legacyusergroup@LegacyUsers.com
Subject: Re: [LegacyUG] Next problem - Unsupported format



You don't even need to do that - in the Help file, on the right pane when you 
first open it up, is a list of Program Capacities, which show general 
capacities and field capacities.

It's also on the website under Legacy > Features






Sincerely,
Sherry
Technical Support
Legacy Family Tree



On Tue, Jun 23, 2015 at 7:32 AM, Adrian Purkiss  wrote:

Marion



Have had a look in the internal structure of the legacy (access based) database 
structure using ms access and the allowed file lengths are as follows.



Path name maximum 255 characters

plus

File name another 255 characters



It should be flagged up to support that Legacy gives the most unhelpful error 
message if these lengths are exceeded.



Adrian







Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages after Nov. 21 2009:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/
Archived messages from old mail server - before Nov. 21 2009:
http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
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/legacyusergroup@legacyusers.com/

Archived messages from old mail server - before Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/

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

Re: [LegacyUG] Next problem - Unsupported format

[Sherry/Support]

You don't even need to do that - in the Help file, on the right pane when
you first open it up, is a list of Program Capacities, which show general
capacities and field capacities.

It's also on the website under Legacy > Features



Sincerely,
Sherry
Technical Support
Legacy Family Tree

On Tue, Jun 23, 2015 at 7:32 AM, Adrian Purkiss  wrote:

> Marion
>
>
>
> Have had a look in the internal structure of the legacy (access based)
> database structure using ms access and the allowed file lengths are as
> follows.
>
>
>
> Path name maximum 255 characters
>
> plus
>
> File name another 255 characters
>
>
>
> It should be flagged up to support that Legacy gives the most unhelpful
> error message if these lengths are exceeded.
>
>
>
> Adrian
>
>
>




Legacy User Group guidelines:

http://www.LegacyFamilyTree.com/Etiquette.asp

Archived messages after Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Archived messages from old mail server - before Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/

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

RE: [LegacyUG] line breaks in event detai

[Adrian Purkiss]

Purely possible loss of formating from word or strange formatting may occur if 
you paste directly into Legacy. Notepad will show exactly how it will format in 
legacy note field and will remove and unwanted formatting codes. Re fonts, 
although notepad can display in various fonts pasting into legacy will format 
in the font, setup in customise fonts. You cannot have different fonts in notes 
from that setup in customise fonts.

Adrian

Sent from my android device.

-Original Message-
From: BARTON LEWIS 
To: legacyusergroup@LegacyUsers.com
Cc: legacyusergroup@LegacyUsers.com, remotes...@wavp.co.uk
Sent: Tue, 23 Jun 2015 4:03 PM
Subject: RE: [LegacyUG] line breaks in event detail

What are the practical consequences of not using Notepad to paste text
into the comments/text field of a source cite?  Previously, I copied and
pasted text directly from Word (which I had copied from a database in
Ancestry, for example).  My reason for copying into Word first is that I
like to replace all hard carriage returns with semicolons so as to take
up less space on the page.  Is there an impact on how the comments/text
appears in reports or when the gedcom is uploaded to other websites?
What is the "default" font and type size when pasting from Notepad?

Thanks,

Barton




On Tue, Jun 23, 2015 at 02:06 AM, Adrian Purkiss wrote:


For info only. Memo fields are where ms access store legacy type note
fields. They have a very large capacity as opposed to normal fields
which are restricted to a maximum of 256 characters. Memo fields can be
set up as text only or rtf (richvtext format) which means they would
support all word type formatting. Legacy appear to use the former
setting hence the need to use a txt editor such as notepad. It is not a
user settings but a setting used by legacy designers and programmers.



Adrian



Sent from my android device.
-Original Message-
From: Barton Lewis 
To: legacyusergroup@LegacyUsers.com
Cc: remotes...@wavp.co.uk
Sent: Tue, 23 Jun 2015 2:13 AM
Subject: RE: [LegacyUG] line breaks in event detail


Thank, Adrian.  I noticed when I input or paste source text into
text/comments that the font is not consistent.  I will use Notepad from
now on to paste my text from when entering in the text/comments field.

Sorry I don’t know what the “memo fields” are.

Barton


From: a...@wavp.co.uk [mailto:a...@wavp.co.uk]
Sent: Monday, June 22, 2015 3:37 AM
To: legacyusergroup@LegacyUsers.com
Cc: remotes...@wavp.co.uk
Subject: RE: [LegacyUG] line breaks in event detail


Legacy/Access store documents as txt but word is not a true text editor
it is a docx/rtf editor. Notepad is a true txt editor. Very strange
things can happen when posting from non txt to txt fields. It mainly
happens vecause various formats/systems have different new line
characters. CR/LF, CR, LF, LF, CR where CR is carriage return and LF
line feed ascii codes. Sorry technical. Thus always best if having
problems to go via notepad.
Legacy, access can support RTF in memo fields. Have you looked at this?
Adrian
Sent from my android device.
-Original Message-
From: Barton Lewis mailto:bartonle...@optonline.net> >
To: legacyusergroup@LegacyUsers.com

Cc: remotes...@wavp.co.uk 
Sent: Mon, 22 Jun 2015 4:14 AM
Subject: RE: [LegacyUG] line breaks in event detail
Thanks, Adrian.  I really never use Notepad, but your technique of
pasting into it and then pasting into Legacy worked great (line breaks
were preserved).  Is it standard to copy/paste text/comments from Word
into Notepad before pasting into Legacy?

Thanks again,

Barton


From: a...@wavp.co.uk   [mailto:a...@wavp.co.uk
 ]
Sent: Sunday, June 21, 2015 7:08 PM
To: legacyusergroup@LegacyUsers.com

Cc: remotes...@wavp.co.uk 
Subject: RE: [LegacyUG] line breaks in event detail


I believe it may be the pasting action that is causing the problem. If
you paste the edited will into notepad does it format as you require.
Make sure you have wordwrap turned off in notepad. If not correct in
notepad then add returns there and then paste into legacy.
Access by the way is the database where Legacy stores its data. Legacy
is a front-end to an ms access database.
Adrian
Sent from my android device.
-Original Message-
From: Barton Lewis mailto:bartonle...@optonline.net> >
To: legacyusergroup@LegacyUsers.com

Sent: Sun, 21 Jun 2015 10:12 PM
Subject: RE: [LegacyUG] line breaks in event detail
This did not fix it.  It is still breaking differently than what is in
the document.  I don’t know what you mean by “Access database.”  This is
just a Word document in my C drive.  My assumption is that breaks cannot
be preserved and that Legacy wraps according to its own
limitations/specifications.

I wanted to see how it looked in a Descendant Report and have 

RE: [LegacyUG] line breaks in event detail

[Sarrazin]

When I paste in Words, I don't use the "Keep source formating" option but
the "Keep text only" option.
No resulting problems.

Georges Sarrazin



---Original Message---

From: BARTON LEWIS
Date: 2015-06-23 11:05:10
To: legacyusergroup@LegacyUsers.com
Cc: legacyusergroup@LegacyUsers.com;  remotes...@wavp.co.uk
Subject: RE: [LegacyUG] line breaks in event detail

What are the practical consequences of not using Notepad to paste text into
the comments/text field of a source cite?  Previously, I copied and pasted
text directly from Word (which I had copied from a database in Ancestry, for
example).  My reason for copying into Word first is that I like to replace
all hard carriage returns with semicolons so as to take up less space on the
page.  Is there an impact on how the comments/text appears in reports or
when the gedcom is uploaded to other websites?  What is the "default" font
and type size when pasting from Notepad?

Thanks,

Barton



On Tue, Jun 23, 2015 at 02:06 AM, Adrian Purkiss wrote:


For info only. Memo fields are where ms access store legacy type note fields
 They have a very large capacity as opposed to normal fields which are
restricted to a maximum of 256 characters. Memo fields can be set up as text
only or rtf (richvtext format) which means they would support all word type
formatting. Legacy appear to use the former setting hence the need to use a
txt editor such as notepad. It is not a user settings but a setting used by
legacy designers and programmers.

Adrian

Sent from my android device.

-Original Message-
From: Barton Lewis 
To: legacyusergroup@LegacyUsers.com
Cc: remotes...@wavp.co.uk
Sent: Tue, 23 Jun 2015 2:13 AM
Subject: RE: [LegacyUG] line breaks in event detail


Thank, Adrian.  I noticed when I input or paste source text into
text/comments that the font is not consistent.  I will use Notepad from now
on to paste my text from when entering in the text/comments field.

Sorry I don’t know what the “memo fields” are.

Barton

From: a...@wavp.co.uk [mailto:a...@wavp.co.uk]
Sent: Monday, June 22, 2015 3:37 AM
To: legacyusergroup@LegacyUsers.com
Cc: remotes...@wavp.co.uk
Subject: RE: [LegacyUG] line breaks in event detail

Legacy/Access store documents as txt but word is not a true text editor it
is a docx/rtf editor. Notepad is a true txt editor. Very strange things can
happen when posting from non txt to txt fields. It mainly happens vecause
various formats/systems have different new line characters. CR/LF, CR, LF,
LF, CR where CR is carriage return and LF line feed ascii codes. Sorry
technical. Thus always best if having problems to go via notepad.

Legacy, access can support RTF in memo fields. Have you looked at this?

Adrian

Sent from my android device.

-Original Message-
From: Barton Lewis 
To: legacyusergroup@LegacyUsers.com
Cc: remotes...@wavp.co.uk
Sent: Mon, 22 Jun 2015 4:14 AM
Subject: RE: [LegacyUG] line breaks in event detail
Thanks, Adrian.  I really never use Notepad, but your technique of pasting
into it and then pasting into Legacy worked great (line breaks were
preserved).  Is it standard to copy/paste text/comments from Word into
Notepad before pasting into Legacy?

Thanks again,

Barton

From: a...@wavp.co.uk [mailto:a...@wavp.co.uk]
Sent: Sunday, June 21, 2015 7:08 PM
To: legacyusergroup@LegacyUsers.com
Cc: remotes...@wavp.co.uk
Subject: RE: [LegacyUG] line breaks in event detail

I believe it may be the pasting action that is causing the problem. If you
paste the edited will into notepad does it format as you require. Make sure
you have wordwrap turned off in notepad. If not correct in notepad then add
returns there and then paste into legacy.

Access by the way is the database where Legacy stores its data. Legacy is a
front-end to an ms access database.

Adrian

Sent from my android device.

-Original Message-
From: Barton Lewis 
To: legacyusergroup@LegacyUsers.com
Sent: Sun, 21 Jun 2015 10:12 PM
Subject: RE: [LegacyUG] line breaks in event detail
This did not fix it.  It is still breaking differently than what is in the
document.  I don’t know what you mean by “Access database.”  This is just a
Word document in my C drive.  My assumption is that breaks cannot be
preserved and that Legacy wraps according to its own
limitations/specifications.

I wanted to see how it looked in a Descendant Report and have several
questions about that.  First, when I click on “Publishing Center” and choose
“Descendant Book Report” I get a 66 page document for this particular
ancestor.  When I choose “Descendant Book Report” I get an 88 page document.
 I am not changing any settings.  What are the functional differences
between these 2 reports?  Also, for the first report, no source detail
prints with the source.  For the second report, source detail is showing for
certain sources (e.g. censuses) but not for the will of my ancestor which I
added as an Event.  I find no option in the report for including or not
including source detail.  I am su

RE: [LegacyUG] line breaks in event detail

[BARTON LEWIS]

What are the practical consequences of not using Notepad to paste text
into the comments/text field of a source cite?  Previously, I copied and
pasted text directly from Word (which I had copied from a database in
Ancestry, for example).  My reason for copying into Word first is that I
like to replace all hard carriage returns with semicolons so as to take
up less space on the page.  Is there an impact on how the comments/text
appears in reports or when the gedcom is uploaded to other websites? 
What is the "default" font and type size when pasting from Notepad?
 
Thanks,
 
Barton

 
 
 
On Tue, Jun 23, 2015 at 02:06 AM, Adrian Purkiss wrote:
 
 
For info only. Memo fields are where ms access store legacy type note
fields. They have a very large capacity as opposed to normal fields
which are restricted to a maximum of 256 characters. Memo fields can be
set up as text only or rtf (richvtext format) which means they would
support all word type formatting. Legacy appear to use the former
setting hence the need to use a txt editor such as notepad. It is not a
user settings but a setting used by legacy designers and programmers.



Adrian



Sent from my android device.
-Original Message-
From: Barton Lewis 
To: legacyusergroup@LegacyUsers.com
Cc: remotes...@wavp.co.uk
Sent: Tue, 23 Jun 2015 2:13 AM
Subject: RE: [LegacyUG] line breaks in event detail


Thank, Adrian.  I noticed when I input or paste source text into
text/comments that the font is not consistent.  I will use Notepad from
now on to paste my text from when entering in the text/comments field.
 
Sorry I don’t know what the “memo fields” are.
 
Barton
 

From: a...@wavp.co.uk [mailto:a...@wavp.co.uk]
Sent: Monday, June 22, 2015 3:37 AM
To: legacyusergroup@LegacyUsers.com
Cc: remotes...@wavp.co.uk
Subject: RE: [LegacyUG] line breaks in event detail

 
Legacy/Access store documents as txt but word is not a true text editor
it is a docx/rtf editor. Notepad is a true txt editor. Very strange
things can happen when posting from non txt to txt fields. It mainly
happens vecause various formats/systems have different new line
characters. CR/LF, CR, LF, LF, CR where CR is carriage return and LF
line feed ascii codes. Sorry technical. Thus always best if having
problems to go via notepad.
Legacy, access can support RTF in memo fields. Have you looked at this?
Adrian
Sent from my android device.
-Original Message-
From: Barton Lewis mailto:bartonle...@optonline.net> >
To: legacyusergroup@LegacyUsers.com

Cc: remotes...@wavp.co.uk 
Sent: Mon, 22 Jun 2015 4:14 AM
Subject: RE: [LegacyUG] line breaks in event detail
Thanks, Adrian.  I really never use Notepad, but your technique of
pasting into it and then pasting into Legacy worked great (line breaks
were preserved).  Is it standard to copy/paste text/comments from Word
into Notepad before pasting into Legacy? 
 
Thanks again,
 
Barton
 

From: a...@wavp.co.uk   [mailto:a...@wavp.co.uk
 ]
Sent: Sunday, June 21, 2015 7:08 PM
To: legacyusergroup@LegacyUsers.com

Cc: remotes...@wavp.co.uk 
Subject: RE: [LegacyUG] line breaks in event detail

 
I believe it may be the pasting action that is causing the problem. If
you paste the edited will into notepad does it format as you require.
Make sure you have wordwrap turned off in notepad. If not correct in
notepad then add returns there and then paste into legacy.
Access by the way is the database where Legacy stores its data. Legacy
is a front-end to an ms access database.
Adrian
Sent from my android device.
-Original Message-
From: Barton Lewis mailto:bartonle...@optonline.net> >
To: legacyusergroup@LegacyUsers.com

Sent: Sun, 21 Jun 2015 10:12 PM
Subject: RE: [LegacyUG] line breaks in event detail
This did not fix it.  It is still breaking differently than what is in
the document.  I don’t know what you mean by “Access database.”  This is
just a Word document in my C drive.  My assumption is that breaks cannot
be preserved and that Legacy wraps according to its own
limitations/specifications. 
 
I wanted to see how it looked in a Descendant Report and have several
questions about that.  First, when I click on “Publishing Center” and
choose “Descendant Book Report” I get a 66 page document for this
particular ancestor.  When I choose “Descendant Book Report” I get an 88
page document.  I am not changing any settings.  What are the functional
differences between these 2 reports?  Also, for the first report, no
source detail prints with the source.  For the second report, source
detail is showing for certain sources (e.g. censuses) but not for the
will of my ancestor which I added as an Event.  I find no option in the
report for including or not including source detail.  I am sure it is
somewhere – can you tell me where?
 
Th

RE: [LegacyUG] Next problem - Unsupported format

[Adrian Purkiss]

Marion



Have had a look in the internal structure of the legacy (access based) database 
structure using ms access and the allowed file lengths are as follows.



Path name maximum 255 characters

plus

File name another 255 characters



It should be flagged up to support that Legacy gives the most unhelpful error 
message if these lengths are exceeded.



Adrian





From: marion wimsett [mailto:2wi...@gmail.com]
Sent: 23 June 2015 14:30
To: legacyusergroup@LegacyUsers.com
Subject: Re: [LegacyUG] Next problem - Unsupported format



Hi Jenny,

I think the problem is now solved - it wasn't the actual photos - it was the 
length of the file name (well that is the only thing I can assume). I fiddled a 
little more with the photos and nothing worked so I renamed the file into a 
shorter version than my husband had given in - and lo and behold Legacy 
accepted the pictures. I have not heard of Legacy having a length requirement 
on folder names but as it is now working I can only assume that is the answer.

Thank you so much for the help and ideas - I will now see if that is the 
problem with the remaining 19 pictures - another night for that though!!

Regards,

Marion



On 23 June 2015 at 21:23, Jenny M Benson  wrote:

On 23/06/2015 13:32, marion wimsett wrote:

As an aside I have even saved it as a different name - and still comes up with 
the same message.


I think I would try opening it in PhotoShop and saving it as, say, a TIFF file 
and see if that will open in Legacy.  If it will, try saving that TIFF again as 
a JPG and try that.

I presume it is not possible to re-create the file by re-scanning the original?




--
Jenny M Benson



Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages after Nov. 21 2009:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/
Archived messages from old mail server - before Nov. 21 2009:
http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
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/legacyusergroup@legacyusers.com/
Archived messages from old mail server - before Nov. 21 2009:
http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
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/legacyusergroup@legacyusers.com/

Archived messages from old mail server - before Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/

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

Re: [LegacyUG] Next problem - Unsupported format

[Robert57P_gmail]

Or try opening it in some other program (MS-Paint) and saving it as a
new file.  Maybe Photoshop is putting in some tag that Legacy doesn't
like - using paint I believe strips off all tags.   If you have some
other program besides paint and Photoshop, you may want to try that one
also.

Bob

On 06/23/2015 09:23, Jenny M Benson wrote:
> On 23/06/2015 13:32, marion wimsett wrote:
>> As an aside I have even saved it as a different name - and still
>> comes up with the same message.
>
> I think I would try opening it in PhotoShop and saving it as, say, a
> TIFF file and see if that will open in Legacy.  If it will, try saving
> that TIFF again as a JPG and try that.
>
> I presume it is not possible to re-create the file byre-scanning the
> original?
>
> --
> Jenny M Benson
>
>
> Legacy User Group guidelines:
> http://www.LegacyFamilyTree.com/Etiquette.asp
> Archived messages after Nov. 21 2009:
> http://www.mail-archive.com/legacyusergroup@legacyusers.com/
> Archived messages from old mail server - before Nov. 21 2009:
> http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
> 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/legacyusergroup@legacyusers.com/

Archived messages from old mail server - before Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/

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

Re: [LegacyUG] Next problem - Unsupported format

[marion wimsett]

Hi Jenny,
I think the problem is now solved - it wasn't the actual photos - it was
the length of the file name (well that is the only thing I can assume). I
fiddled a little more with the photos and nothing worked so I renamed the
file into a shorter version than my husband had given in - and lo and
behold Legacy accepted the pictures. I have not heard of Legacy having a
length requirement on folder names but as it is now working I can only
assume that is the answer.
Thank you so much for the help and ideas - I will now see if that is the
problem with the remaining 19 pictures - another night for that though!!
Regards,
Marion

On 23 June 2015 at 21:23, Jenny M Benson  wrote:

>  On 23/06/2015 13:32, marion wimsett wrote:
>
> As an aside I have even saved it as a different name - and still comes up
> with the same message.
>
>
> I think I would try opening it in PhotoShop and saving it as, say, a TIFF
> file and see if that will open in Legacy.  If it will, try saving that
> TIFF again as a JPG and try that.
>
> I presume it is not possible to re-create the file by re-scanning the
> original?
>
> --
> Jenny M Benson
>
>
>
> Legacy User Group guidelines:
> http://www.LegacyFamilyTree.com/Etiquette.asp
> Archived messages after Nov. 21 2009:
> http://www.mail-archive.com/legacyusergroup@legacyusers.com/
> Archived messages from old mail server - before Nov. 21 2009:
> http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
> 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/legacyusergroup@legacyusers.com/

Archived messages from old mail server - before Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/

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

Re: [LegacyUG] Next problem - Unsupported format

[Jenny M Benson]

  
  
On 23/06/2015 13:32, marion wimsett
  wrote:

As an aside I have even saved it as a different name -
  and still comes up with the same message.

I think I would try
opening it in PhotoShop and saving it as, say, a TIFF file and see if that will open in Legacy.  If it will, try saving that
TIFF again as a JPG and try that.

I presume it is not possible to
  re-create the file by re-scanning the original?
  
--
Jenny M Benson
  



Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages after Nov. 21 2009:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/
Archived messages from old mail server - before Nov. 21 2009:
http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
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

Re: [LegacyUG] Next problem - Unsupported format

[marion wimsett]

As an aside I have even saved it as a different name - and still comes up
with the same message.

On 23 June 2015 at 20:28, marion wimsett <2wi...@gmail.com> wrote:

> Hi Mike,
>
> They are all jpg's - and I opened one in Adobe Photoshop, fiddled a bit
> with it (as I do with all of my own photos) and save it, and it still
> wouldn't work. At this stage I am running out of ideas! (The details I gave
> were after it had been saved by Photoshop).
>
> Marion
>
> On 23 June 2015 at 19:58, MikeFry  wrote:
>
>> On 2015/06/23 13:21 PM, marion wimsett wrote:
>>
>> > The photos are all *.jpg and detail on just one of them are:
>>
>> Spelling of the file extension was always a problem Legacy doesn't like
>> .jpeg .
>> It prefers .jpg.
>>
>> If that's the case, then it might be down to an unsupported, internal
>> compression method within the jpg file. Open it with something that
>> doesn't
>> bitch and save it with a different compressiom method.
>>
>> --
>> Regards,
>> Mike Fry (Jhb)
>>
>>
>>
>>
>> Legacy User Group guidelines:
>>
>> http://www.LegacyFamilyTree.com/Etiquette.asp
>>
>> Archived messages after Nov. 21 2009:
>>
>> http://www.mail-archive.com/legacyusergroup@legacyusers.com/
>>
>> Archived messages from old mail server - before Nov. 21 2009:
>>
>> http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
>>
>> 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/legacyusergroup@legacyusers.com/

Archived messages from old mail server - before Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/

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

Re: [LegacyUG] Next problem - Unsupported format

[marion wimsett]

Hi Mike,

They are all jpg's - and I opened one in Adobe Photoshop, fiddled a bit
with it (as I do with all of my own photos) and save it, and it still
wouldn't work. At this stage I am running out of ideas! (The details I gave
were after it had been saved by Photoshop).

Marion

On 23 June 2015 at 19:58, MikeFry  wrote:

> On 2015/06/23 13:21 PM, marion wimsett wrote:
>
> > The photos are all *.jpg and detail on just one of them are:
>
> Spelling of the file extension was always a problem Legacy doesn't like
> .jpeg .
> It prefers .jpg.
>
> If that's the case, then it might be down to an unsupported, internal
> compression method within the jpg file. Open it with something that doesn't
> bitch and save it with a different compressiom method.
>
> --
> Regards,
> Mike Fry (Jhb)
>
>
>
>
> Legacy User Group guidelines:
>
> http://www.LegacyFamilyTree.com/Etiquette.asp
>
> Archived messages after Nov. 21 2009:
>
> http://www.mail-archive.com/legacyusergroup@legacyusers.com/
>
> Archived messages from old mail server - before Nov. 21 2009:
>
> http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
>
> 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/legacyusergroup@legacyusers.com/

Archived messages from old mail server - before Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/

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

Re: [LegacyUG] Registration Date - which one?

[Jenny M Benson]

  
  
On 23/06/2015 13:10, Rob Miller wrote:

Should I be using as the date the day the informant
  completed the form or the date the Registrar stamped the paper
  (often the day after).
  
  Or are they really two different animals? The date the informant
  completed the form is the one that I am creating the event for.
  The date that it was stamped really has no bearing. Correct?

I think I would agree with you that the date
  the Informant acted is the date that is relevant to their Event. 
  The Registrar's action is related more to a
Birth Registration Event if you have one, or might be included
in Birth Notes. 

--
Jenny M Benson
  



Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages after Nov. 21 2009:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/
Archived messages from old mail server - before Nov. 21 2009:
http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
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

[LegacyUG] Registration Date - which one?

[Rob Miller]

Thanks to everyone who helped me with wording of my Informant Event. I now
have one connected question.

Should I be using as the date the day the informant completed the form or
the date the Registrar stamped the paper (often the day after).

Or are they really two different animals? The date the informant completed
the form is the one that I am creating the event for. The date that it was
stamped really has no bearing. Correct?

Thanks!

Rob




Legacy User Group guidelines:

http://www.LegacyFamilyTree.com/Etiquette.asp

Archived messages after Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Archived messages from old mail server - before Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/

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

Re: [LegacyUG] Next problem - Unsupported format

[MikeFry]

On 2015/06/23 13:21 PM, marion wimsett wrote:

> The photos are all *.jpg and detail on just one of them are:

Spelling of the file extension was always a problem Legacy doesn't like .jpeg .
It prefers .jpg.

If that's the case, then it might be down to an unsupported, internal
compression method within the jpg file. Open it with something that doesn't
bitch and save it with a different compressiom method.

--
Regards,
Mike Fry (Jhb)




Legacy User Group guidelines:

http://www.LegacyFamilyTree.com/Etiquette.asp

Archived messages after Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Archived messages from old mail server - before Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/

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

[LegacyUG] Next problem - Unsupported format

[marion wimsett]

Me again!
In linking the photos to the imported file there are a few that are
missing. I can see where they are and am trying to link them - but - they
will not link - either manually or relinking.
The message comes up with "unsupported format".
The photos are all *.jpg and detail on just one of them are:
Dimensions: 1692 x 2741
Width: 1692 pixels
Height: 2742 pixels
Horizontal resolution: 72 dpi
Vertical resolution: 72 dpi
Bit depth: 8
Resolution Unit: 2
Colour representation Uncalibrated.

I have tied everything I can think of from unlinking the original, opening
it in Photoshop and changing it, moving the folder to a different place and
trying to link it from there, and nothing is working. There seems no
logical reason that these would not be "supported".

I have a headache - any help would be appreciated.

Marion




Legacy User Group guidelines:

http://www.LegacyFamilyTree.com/Etiquette.asp

Archived messages after Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Archived messages from old mail server - before Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/

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

Re: [LegacyUG] Re: You do not have permission to post to the legacyusergroup@legacyusers.com list

[MikeFry]

On 2015/06/23 08:03 AM, Dick D Staley wrote:

People! Pay attention to the Subject field!

--
Regards,
Mike Fry (Jhb)




Legacy User Group guidelines:

http://www.LegacyFamilyTree.com/Etiquette.asp

Archived messages after Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Archived messages from old mail server - before Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/

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

Re: [LegacyUG] Re: You do not have permission to post to the legacyusergroup@legacyusers.com list

[Cathy Pinner]

Hi Dick,

You can do a Detailed Search.
(Search - find - Detailed Search tab)

Individual - Given Names - contains -  (or equal to if you know her
full name)
AND
2nd condition
Individual - Spouse's Surname - equals - x

Cathy

Jenny M Benson wrote:
>
> On 23/06/2015 07:03, Dick D Staley wrote:
>>
>> In a Legacy 8.0 Demo and Class at Burbank Jamboree Believe I saw
>> that you can search for a wife's maiden name by using or knowing married
>> name, Is this true or was I imaging it?
>
>
>
> Entry 2.8 in the Customise menu gives you the option to have Legacy
> generate a default married surname (husband's surname) in addition to
> her maiden surname. From the Options in Name List or Index view you can
> then choose to show the Married Names in addition to the Maiden Name.
>
> If you Search for a woman by her Surname (with or without Forename) and
> you have the option selected in Name List, the Search result will show
> the two entries - maiden and surnames.
>
> All this, of course, presupposes that you knew and entered the woman's
> maiden name in the first place!
>
> Personally, I do not use the Married Surname option, preferring, for
> lack of ambiguity, to refer to women always by their maiden names.




Legacy User Group guidelines:

http://www.LegacyFamilyTree.com/Etiquette.asp

Archived messages after Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Archived messages from old mail server - before Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/

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

Re: [LegacyUG] Re: You do not have permission to post to the legacyusergroup@legacyusers.com list

[Jenny M Benson]

On 23/06/2015 07:03, Dick D Staley wrote:
> In a Legacy 8.0 Demo and Class at Burbank Jamboree Believe I saw
> that you can search for a wife's maiden name by using or knowing married
> name,  Is this true or was I imaging it?


Entry 2.8 in the Customise menu gives you the option to have Legacy
generate a default married surname (husband's surname) in addition to
her maiden surname.  From the Options in Name List or Index view you can
then choose to show the Married Names in addition to the Maiden Name.

If you Search for a woman by her Surname (with or without Forename) and
you have the option selected in Name List, the Search result will show
the two entries - maiden and surnames.

All this, of course, presupposes that you knew and entered the woman's
maiden name in the first place!

Personally, I do not use the Married Surname option, preferring, for
lack of ambiguity, to refer to women always by their maiden names.

--
Jenny M Benson





Legacy User Group guidelines:

http://www.LegacyFamilyTree.com/Etiquette.asp

Archived messages after Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Archived messages from old mail server - before Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/

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