RE: [LegacyUG] Next problem - Unsupported format

[Brian L. Lightfoot]

I’m almost sorry I asked. With the file path that you have given, I get by my 
account a total of 96 characters plus whatever the file name was. However, the 
folder “\\NAS  ” represent relative addressing 
instead of absolute addressing. As such, that particular folder could have its 
own path which is another 100 characters deep, not really likely but still 
possible.



Regardless, this is still a far cry from the supposed 255 character limit. The 
plot thickens… so now it’s time for some destructive testing in Legacy to see 
what the “real” limit is. Hopefully, it actually is 255 and the OP’s namespace 
for files is in need of some cleanup.





Brian in CA



PS – I know you said it’s your husbands tree but did anyone every point out 
that you have a “Percy Mott” folder inside of another folder which is inside of 
another “Percy Mott” folder. Good grief. To each their own, I guess. Whatever 
works for you.







From: marion wimsett [mailto:2wi...@gmail.com]
Sent: Wednesday, June 24, 2015 10:13 PM
To: legacyusergroup@LegacyUsers.com
Subject: Re: [LegacyUG] Next problem - Unsupported format



I will try and elucidate on the Folders and Files, and in counting I included 
all spaces and the drive details, it went along in this manner:



(\\NASXXX\   (Z)/Family Tree AW/The Lloyds/Percy 
Mott/Percy Thurger Leonard Mott/Percy Mott/Service Record



In the Service Record folder there were 15 pages of jpgs, all within the format 
required for Legacy.

In the Percy Mott folder there was also one page called Opening Record which 
opened up in Legacy media without a problem. (In other words the ones that 
wouldn't open were in one extra Folder)/.

I played with Page 1, saved it as the original name and saved it as a new name, 
and still none of the photos would open up in Legacy Media in the Service 
Record Folder.



In desperation I moved the folder from The Lloyds and placed it in the Family 
Tree AW folder.I cannot remember at this stage if the photos would open or not 
(I was a little frustrated to say the least)



I have a feeling they still didn't open as I then moved the Service Record 
folder into the Percy Mott folder, together with the Opening Record jpg which 
was also in there.



At this stage I went back into Legacy and did the search to link the photo of 
page 1 - and the record linked, and so did the remaining 14 pages.



This left the original Folder of Percy Thurger Leonard Mott obsolete so that 
was deleted.



All photos are now under:  (\\NASXXX\   (Z)/Family 
Tree AW/Percy Mott.



Hope this explains some of the steps I undertook - whether it gives us any 
answers as to why the photos would not open in a path that was less than 255 
characters I have no idea.



Please, before anyone says that it is not a good idea to have so many Folders, 
as I have explained in previous posts, this is my husband's tree. The files 
have been brought over to the NAS from his Mac and they are in the order he 
stored them!!!



I appreciate everyone's input and if there is an answer I would be eternally 
grateful!.



Marion



On 25 June 2015 at 02:01, Brian L. Lightfoot  wrote:

I’m curious about the number of characters in your file path compared to 
Legacy’s claim of 255 maximum. In a previous post you mentioned something about 
100 characters which I find quite large unless your file is buried several 
additional folders deep. If you counted all the characters in your file path, 
how does that compare to Legacy’s claim of 255?



Hopefully it’s not a misunderstanding of Windows so-called library folders such 
as “My Documents” or “My Pictures” because those names are just shortcuts and 
the true path is usually something like “C:\Users\\My Documents\”.





Brian in CA







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]

I will try and elucidate on the Folders and Files, and in counting I
included all spaces and the drive details, it went along in this manner:

(\\NASXXX\ (Z)/Family Tree AW/The Lloyds/Percy Mott/Percy Thurger
Leonard Mott/Percy Mott/Service Record

In the Service Record folder there were 15 pages of jpgs, all within the
format required for Legacy.
In the Percy Mott folder there was also one page called Opening Record
which opened up in Legacy media without a problem. (In other words the ones
that wouldn't open were in one extra Folder)/.
I played with Page 1, saved it as the original name and saved it as a new
name, and still none of the photos would open up in Legacy Media in the
Service Record Folder.

In desperation I moved the folder from The Lloyds and placed it in the
Family Tree AW folder.I cannot remember at this stage if the photos would
open or not (I was a little frustrated to say the least)

I have a feeling they still didn't open as I then moved the Service Record
folder into the Percy Mott folder, together with the Opening Record jpg
which was also in there.

At this stage I went back into Legacy and did the search to link the photo
of page 1 - and the record linked, and so did the remaining 14 pages.

This left the original Folder of Percy Thurger Leonard Mott obsolete so
that was deleted.

All photos are now under:  (\\NASXXX\ (Z)/Family Tree AW/Percy Mott.

Hope this explains some of the steps I undertook - whether it gives us any
answers as to why the photos would not open in a path that was less than
255 characters I have no idea.

Please, before anyone says that it is not a good idea to have so many
Folders, as I have explained in previous posts, this is my husband's tree.
The files have been brought over to the NAS from his Mac and they are in
the order he stored them!!!

I appreciate everyone's input and if there is an answer I would be
eternally grateful!.

Marion

On 25 June 2015 at 02:01, Brian L. Lightfoot 
wrote:

> I’m curious about the number of characters in your file path compared to
> Legacy’s claim of 255 maximum. In a previous post you mentioned something
> about 100 characters which I find quite large unless your file is buried
> several additional folders deep. If you counted all the characters in your
> file path, how does that compare to Legacy’s claim of 255?
>
>
>
> Hopefully it’s not a misunderstanding of Windows so-called library folders
> such as “My Documents” or “My Pictures” because those names are just
> shortcuts and the true path is usually something like
> “C:\Users\\My Documents\”.
>
>
>
>
>
> Brian in CA
>
>
>
>
>
> *From:* Adrian Purkiss [mailto:a...@wavp.co.uk]
> *Sent:* Wednesday, June 24, 2015 9:39 AM
> *To:* legacyusergroup@LegacyUsers.com
> *Subject:* RE: [LegacyUG] Next problem - Unsupported format
>
>
>
> Sherry
>
>
>
> I think you missed the note where it was confirmed the solution was length
> of file name.
>
> From: marion wimsett [mailto:2wi...@gmail.com <2wi...@gmail.com>]
>
> Sent: 23 June 2015 14:30
>
> Hence the discussion on field size
>
>
>
> 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

[LegacyUG] Help?

[Dick D Staley]

In a Legacy 8.0 Demo and Class at Burbank Jamboree... Believe I saw that
you can search for a wife's madien name by using or knowing married
name, is this true or was I imaging it?  Thank you.




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 detail

[CE WOOD]

Too logical.

CE

Date: Wed, 24 Jun 2015 15:10:09 -0400
From: bartonle...@optonline.net
Subject: Re: [LegacyUG] line breaks in event detail
To: legacyusergroup@LegacyUsers.com
CC: legacyusergroup@LegacyUsers.com

Thanks, Cathy, but I don't consider this to be a comparative explanation of the 
differences between the two versions of the Descendant Book Report, as accessed 
in Reports or alternatively in Publishing Center.  Rather, it's an explanation 
of the features and options available by generating the report in the 
Publishing Center.  It's left to the user to determine those differences by 
comparing the two.  As an example, in the sentence where you bolded "overall 
index and list of source citations," it isn't stated that this is an option 
limited to the Publishing Center (as far as I can tell, only the full name 
index is limited to the Publishing Center version).  There may be other 
differences, too, but again, no one would know unless they generated the 
reports from both places, fully explored the respective options, and compared 
the two. I feel if Legacy is going to allow the same report to be generated in 
multiple ways, with different features and options for the report depending on 
where it's generated, Legacy should spell those out somewhere.   Respectfully, 
Barton On Mon, Jun 22, 2015 at 12:51 AM, Cathy Pinner wrote:  Hi Barton,



Try reading the Help again - I know it can be difficult when you're
looking for exactly the terminology in your head.

If it isn't clear enough, put in a suggestion. It seems clear to me but
I've been using Legacy since Legacy 2.



Publishing Center


You can create professional-looking books by assembling the various
reports and charts available in Legacy into one single document. This
can include ancestor and descendant book reports, pedigree charts,
family group records, picture scrapbooks and much more. You can also add
 a table of contents, other introductory sections and an overall index and list 
of source
citations.



...

The Additional Tab
Â
Source Options

To include source citations throughout the book,
select the checkbox
to the left of the Source Options button.  To set (or change) the

options, click the button to see the Source Options screen.

Â

Index Options
By selecting the checkbox to the left of the Index
 Options
button, you can have Legacy generate an alphabetical index and an
optional
Location index for the entire book report.  The index includes each
person who
is shown on each page.  The index can be lined or unlined and printed in
 one,
two or three columns.  Click the Index Options button to make
changes in
the index format.  (See Index Options for more
information.)






Cathy



Barton Lewis
  Monday, 22 June
2015 11:12 AM
  Thanks Cathy, but I opened
 the Help file and read what is there on the Publishing Center.  I do
not see anywhere addressed the functional differences between a
descendant book generated there or from the Descendant Book Report tab.
  It would be nice if that were explained somewhere, in my opinion.

You
 directions for changing the options for printing text/comments of the
source detail worked perfectly; thank you.

Barton



-Original
 Message-
From: Cathy Pinner [mailto:genea...@gmail.com]
Sent:
 Sunday, June 21, 2015 10:07 PM
To: legacyusergroup@LegacyUsers.com
Subject:
 Re: [LegacyUG] line breaks in event detail

Hi Barton,
Sorry, I
 thought since you were talking about soft breaks, you'd know how to do
the search and replace in Word.

Testing this morning, Legacy
automatically changed soft breaks into hard breaks.

The line
length is preserved unless the line length is beyond the width of your
report page with your chosen font. How it looks on the screen in the
General Notes or Event Notes depends on the size of the window but there
 will be a new line where those breaks were but there may be others as
well if the original was longer than the width of display or report
page.

Access is the database part of Microsoft Office. Legacy
data is stored in an Access database. Placing material with soft breaks
directly into Access results in the soft break being replaced with a
hard break.

You say that the Report options are the same for the
Publishing Centre choosing Descendant Report and just a Descendant
Report then go on to detail differences.
The Publishing Centre has
its own place for choosing some options like Index and Sources rather
than using the particular report options.
Differences in Source
choices and Index sources are probably what is accounting for the
different page count.  Do read the Help file on the Publication Centre.

Whether
 or not Source Detail prints is controlled from where you added the
Source itself.

Note that the Source Detail is made up of
different parts. There's the Source Detail itself on the front tab, then
 Source Detail Text and Source Detail Comments on the next tab, then
Media, then Repository.

The easy way to see what will print is to
 op

Re: [LegacyUG] line breaks in event detail

[BARTON LEWIS]

Thanks, Cathy, but I don't consider this to be a comparative explanation
of the differences between the two versions of the Descendant Book
Report, as accessed in Reports or alternatively in Publishing Center. 
Rather, it's an explanation of the features and options available by
generating the report in the Publishing Center.  It's left to the user
to determine those differences by comparing the two.  As an example, in
the sentence where you bolded "overall index and list of source
citations," it isn't stated that this is an option limited to the
Publishing Center (as far as I can tell, only the full name index is
limited to the Publishing Center version).  There may be other
differences, too, but again, no one would know unless they generated the
reports from both places, fully explored the respective options, and
compared the two.
 
I feel if Legacy is going to allow the same report to be generated in
multiple ways, with different features and options for the report
depending on where it's generated, Legacy should spell those out
somewhere.  
 
Respectfully,
 
Barton 
 

 
 
 
On Mon, Jun 22, 2015 at 12:51 AM, Cathy Pinner wrote:
 
 
Hi Barton,



Try reading the Help again - I know it can be difficult when you're
looking for exactly the terminology in your head.

If it isn't clear enough, put in a suggestion. It seems clear to me but
I've been using Legacy since Legacy 2.




Publishing Center

You can create professional-looking books by assembling the various
reports and charts available in Legacy into one single document. This
can include ancestor and descendant book reports, pedigree charts,
family group records, picture scrapbooks and much more. You can also add
  a table of contents, other introductory sections and an overall index
and list of source
citations.



...


The Additional Tab 

Source Options

To include source citations throughout the book,
select the checkbox
to the left of the Source Options button.  To set (or change) the

options, click the button to see the Source Options screen.

 

Index Options

By selecting the checkbox to the left of the Index
  Options
button, you can have Legacy generate an alphabetical index and an
optional
Location index for the entire book report.  The index includes each
person who
is shown on each page.  The index can be lined or unlined and printed
in
  one,
two or three columns.  Click the Index Options button to make
changes in
the index format.  (See Index Options   for
more
information.)





Cathy





Barton Lewis 


   Monday, 22 June
2015 11:12 AM



Thanks Cathy, but I opened
  the Help file and read what is there on the Publishing Center.  I do
not see anywhere addressed the functional differences between a
descendant book generated there or from the Descendant Book Report tab.
   It would be nice if that were explained somewhere, in my opinion.
You
  directions for changing the options for printing text/comments of the
source detail worked perfectly; thank you.
Barton

-Original
  Message-
From: Cathy Pinner [mailto:genea...@gmail.com
 ]
Sent:
  Sunday, June 21, 2015 10:07 PM
To: legacyusergroup@LegacyUsers.com

Subject:
  Re: [LegacyUG] line breaks in event detail
Hi Barton,
Sorry, I
  thought since you were talking about soft breaks, you'd know how to do
the search and replace in Word.
Testing this morning, Legacy
automatically changed soft breaks into hard breaks.
The line
length is preserved unless the line length is beyond the width of your
report page with your chosen font. How it looks on the screen in the
General Notes or Event Notes depends on the size of the window but there
  will be a new line where those breaks were but there may be others as
well if the original was longer than the width of display or report
page.
Access is the database part of Microsoft Office. Legacy
data is stored in an Access database. Placing material with soft breaks
directly into Access results in the soft break being replaced with a
hard break.
You say that the Report options are the same for the
Publishing Centre choosing Descendant Report and just a Descendant
Report then go on to detail differences.
The Publishing Centre has
its own place for choosing some options like Index and Sources rather
than using the particular report options.
Differences in Source
choices and Index sources are probably what is accounting for the
different page count.  Do read the Help file on the Publication Centre.
Whether
  or not Source Detail prints is controlled from where you added the
Source itself.
Note that the Source Detail is made up of
different parts. There's the Source Detail itself on the front tab, then
  Source Detail Text and Source Detail Comments on the next tab, then
Media, then Repository.
The easy way to see what will print is to
  open the Assigned Sources screen and on the Output tab at the bottom
ch

RE: [LegacyUG] Next problem - Unsupported format

[Brian L. Lightfoot]

I’m curious about the number of characters in your file path compared to 
Legacy’s claim of 255 maximum. In a previous post you mentioned something about 
100 characters which I find quite large unless your file is buried several 
additional folders deep. If you counted all the characters in your file path, 
how does that compare to Legacy’s claim of 255?



Hopefully it’s not a misunderstanding of Windows so-called library folders such 
as “My Documents” or “My Pictures” because those names are just shortcuts and 
the true path is usually something like “C:\Users\\My Documents\”.





Brian in CA





From: Adrian Purkiss [mailto:a...@wavp.co.uk]
Sent: Wednesday, June 24, 2015 9:39 AM
To: legacyusergroup@LegacyUsers.com
Subject: RE: [LegacyUG] Next problem - Unsupported format



Sherry



I think you missed the note where it was confirmed the solution was length of 
file name.

From: marion wimsett [mailto:2wi...@gmail.com]

Sent: 23 June 2015 14:30

Hence the discussion on field size



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] Next problem - Unsupported format

[Adrian Purkiss]

Sherry



I think you missed the note where it was confirmed the solution was length of 
file name.

From: marion wimsett [mailto:2wi...@gmail.com]

Sent: 23 June 2015 14:30

Hence the discussion on field size



Adrian



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



Did you look under Picture: Formats - Displaying Pictures"?? Programs don't 
normally tell you the negative - what they can't do - but the positive - what 
they can do!

>From that Help topic:



Supported Formats

Legacy supports the loading, displaying and converting of the following picture 
file formats:



Bitmap .BMP

PCX .PCX

Tiff .TIF (without LZW compression)

PICT .PCT

JPEG .JPG

.CAL

.CMP

.EPS

.FAX

.GIF

.IMG

.MSP

.PCD

.PNG

.TGA

.GIF

.WPG

.DIS

.EFX

.FIL

.KRN

.THK

.TWN



​I'm not sure why Adrian was looking in Access for file capacities when the 
discussion was on file formats?​




Sincerely,
Sherry
Technical Support
Legacy Family Tree



On Tue, Jun 23, 2015 at 7:39 PM, marion wimsett <2wi...@gmail.com> wrote:

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







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

[LegacyUG] Individual Chart

[Jo Poi]

Just updated to 8.0.0.501 and now find that when I click on individual
chart for a person it goes straight into the print preview screen
instead of the options window.
Easy enough to get back by pressing the close button, but is this how
it is now ?
Jo Poi



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

[Chris Seens]

Actually Sherry, Adrian is quite correct. Programmer's refer to field size
as
the number of characters a field can hold.

Sent using CloudMagic
[https://cloudmagic.com/k/d/mailapp?ct=ti&cv=6.4.27&pv=8.3]
On Wed, Jun 24, 2015 at 10:31 AM, legacyusergroup@legacyusers.com
 wrote:
Did you look under Picture: Formats - Displaying Pictures"?? Programs don't
normally tell you the negative - what they can't do - but the positive -
what
they can do!

 From that Help topic:

Supported Formats

Legacy supports the loading, displaying and converting of the following
picture
file formats:



Bitmap .BMP

PCX .PCX

Tiff .TIF (without LZW compression)

PICT .PCT

JPEG .JPG

.CAL

.CMP

.EPS

.FAX

.GIF

.IMG

.MSP

.PCD

.PNG

.TGA

.GIF

.WPG

.DIS

.EFX

.FIL

.KRN

.THK

.TWN


I'm not sure why Adrian was looking in Access for file capacities when the
discussion was on file formats?
Sincerely,
Sherry
Technical Support
Legacy Family Tree
On Tue, Jun 23, 2015 at 7:39 PM, marion wimsett < 2wi...@gmail.com
[2wi...@gmail.com] > wrote:
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



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]

Did you look under Picture: Formats - Displaying Pictures"?? Programs don't
normally tell you the negative - what they can't do - but the positive -
what they can do!

>From that Help topic:

*Supported Formats*

Legacy supports the loading, displaying and converting of the following
picture file formats:



Bitmap .BMP

PCX .PCX

Tiff .TIF (without LZW compression)

PICT .PCT

JPEG .JPG

.CAL

.CMP

.EPS

.FAX

.GIF

.IMG

.MSP

.PCD

.PNG

.TGA

.GIF

.WPG

.DIS

.EFX

.FIL

.KRN

.THK

.TWN

​I'm not sure why Adrian was looking in Access for file capacities when the
discussion was on file formats?​

Sincerely,
Sherry
Technical Support
Legacy Family Tree

On Tue, Jun 23, 2015 at 7:39 PM, marion wimsett <2wi...@gmail.com> wrote:

> 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
>
>




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]

Capacity and size are two different things. A "size" is a dimension, like
1" x 2" or 56 KB.  A capacity is how much that size holds.  The bucket can
be 4x6x2 (size) and hold a gallon of liquid (capacity).

It really doesn't matter what a field "size" is - it's the capacity that's
important.

Most of our customers are totally unfamiliar with Access.


Sincerely,
Sherry
Technical Support
Legacy Family Tree

On Tue, Jun 23, 2015 at 2:37 PM, Adrian Purkiss  wrote:

> 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

Re: [LegacyUG] line breaks in event detai

[Jenny M Benson]

  
  
On 24/06/2015 04:24, I Macaulay wrote:

Consider
notepad (or equiv) as a filter, takes out the unwanted bits and
leaves the text clean.
This brief message you
just sent quotes about 11 previous messages in their entirety
and includes 11 sets of LUG Guidelines etc.

PLEASE trim your
posts to include only what is necessary.
--
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] line breaks in event detai

[Adrian Purkiss]

Put eloquently. There is an excellent article in Wikipedia on reasons fot the 
original problem which was loss of soft and hard returns when pasting into 
legacy on Wikipedia. https://en.m.wikipedia.org/wiki/Newline

Adrian

Sent from my android device.

-Original Message-
From: I Macaulay 
To: legacyusergroup@LegacyUsers.com
Sent: Wed, 24 Jun 2015 4:24 AM
Subject: Re: [LegacyUG] line breaks in event detai

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] li