[Legacy-Nederlands] Nieuwe versie Legacy lost foutmelding #62 op

[Irma Lommen - Salden]

Evert Van Dijken heeft het onderstaande bericht geplaatst in de Legacy groep
op Facebook:

 

Er is een nieuwe update beschikbaar voor Legacy

 

Door deze update worden de opties in 8.2 teruggezet naar de
standaardwaarden. Dus als iemand dat ooit heeft aangepast dan na de update
weer terugzetten naar de gewenste waarden.

Verder wordt er meteen na de update bij het starten van het programma een
controle van de bronnen gedaan (er wordt niets gewijzigd aan de bron zelf,
alleen wordt alles gekopieerd naar een extra kolom in de database zodat
FamilySearch deze bron ook kan gebruiken als een gebruiker besluit om deze
bron te kopiëren naar FamilySearch).

Natuurlijk ook veel bugfixes zoals de problemen met het Gezinsbladrapport.

 

Hieronder de tekst zoals die gepost is in de Engelstalige LUG

 

Legacy 9 Update 279

Yes, we have been promising another Legacy 9 update for days... It is here

now. Yes, it fixes the Error 62 problem with Family group Report. (I am sure

that many of you will be glad of that!)

 

It also fixes a number of other issues that you can see from the revision

history. I am not going to go into all of them as you can read that list,

and most are self explanatory.

 

What I do wish to share with you are a few very visible changes.

 

First, we discovered that we needed to check all of your source records as

we were finding that many users have records that are missing a field needed

by FamilySearch. It does not hurt your data, but it does make it difficult

to transfer sources properly to Legacy FamilySearch and other tools.

 

When you open your Family File for the first time with this update, you will

see a display where is says "Checking Sources" This may take a short while

if you have a lot of sources. Do not worry. This is not changing any of your

sources, but, after it is complete, your sources will now transfer

correctly.

 

Another major changes is that, in response to numerous requests, we have

done a major revision to how we handle the various IDs you see displayed

while running Legacy and that you add to reports. We have this project about

90% complete, but it is so much better that we did not want to hold up a new

update to resolve the last few issues as they are relatively minor. (Yes, I

anticipate some of you dinging us for anything missing; we do want to hear

from you to tell us if we are missing something you think we really need!)

 

Before you start working with this new update, we need you to open the

Customize tool and go to option 8.2 and set it up as you want numbers to

display in Legacy.

 

The Option 8.2 settings will now have no effect on any reports!

 

Option 8.2 has 2 sections:

 

"On Family, Pedigree, and Descendant Views"

and

"Show RINs on all Name Lists"

 

The first section, if checked, will allow you to display a RIN and/or one or

none of the "non-RIN IDs" after names in Family Viewm Pedigree View, and

Descendant View .

 

The non-RIN IDs are: AFN, User ID, FamilySearch ID, or FindaGrave ID.

RIN will be displayed in square brackets after a name, eg. John Smith [231].

The non-RIN ID will be displayed after a name as {L8SJ-WLR} in curly

brackets.

 

The second section, if checked, will add RINs to Name Lists. That, of

course, includes Search Lists and Share Event with lists. It will add them

to Marriage lists, Show Lists, Name Lists in Master Location List, etc. And

it is supposed to be smart enough to assure a RIN is not shown twice. IE,

Show Lists normally have a RIN column; we do not add a RIN to them.

 

The Relationship Calculator has its own RIN control and that works

independently now of Option 8.2. Similarly, Chronology View on its Display

Options Formatting tab now has an independent control to display BOTH RINs

and MRINs.

 

Reports

 

All reports now have their own independent controls to determine what IDs

will be shown. The number of IDs that a report will be able to display is

dependent on what we felt was necessary or feasible for the Report.

 

All Reports will have an option as part of its Report Options to display

RINs; many will also have MRINs; some will also allow you to select ONE of

the non-RIN IDs; and some will also allow you to select all of the non-RIN

IDs.

 

The display of the IDs will be done on a report with labels so it is clear

which ID is being displayed:

 

RIN: [nnn]

MRIN: [MRIN: nnn]

 

Non-RIN IDs:

 

AFN: {AFN: nnn}

User ID: {UsrID: nnn}

FamilySearch ID: {FSID: nnn}

FindaGrave ID: {FGID: nnn}

 

This is the design. I am sure you will find a few glitches as there are a

lot of tools to check and different user settings may give different

results.

(John Lisle)

 

Michele Simmons Lewis, CGR

 

Gr,

 

Irma

 

Irma Lommen – Salden

  irmalom...@home.nl

  www.limburgemigrant.nl

 

-- 
___
Legacy-Nederlands mailing list
Legacy-Nederlands@legacyusers.com

Re: [Legacy-Nederlands] Fout 62 Input past end of file

[Dirk JW Detmar]

Beste Pierre,

Deze fout is al eerder gemeld.
Legacy weet ervan, zij werken aan een oplossing.

Groet,
--


Dirk JW Detmar

phone: +55 86 981254397
address: R. Lincoln F. Guimarães, 120
Cond. São Cristovão Park, blc. Orquídea, apt. 203
Santa Isabel, CEP: 64053-240
Teresina, Piauí, Brasil

web: djw-detmar.nl/wordpress 
email: dirk.det...@djw-detmar.nl 



Pierre Debecker schreef op 13.januari.2019 om 14:02:

Op 8 januari heb ik hulp gevraagd omtrent de vermelde fout.
Kan iemand mij helpen?
Bedankt op voorhand.

Pierre Debecker


-- 
___
Legacy-Nederlands mailing list
Legacy-Nederlands@legacyusers.com
http://legacyusers.com/mailman/listinfo/legacy-nederlands_legacyusers.com

Re: [Legacy-Nederlands] Fout 62 Input past end of file

[Irma Lommen - Salden]

Er is een nieuwe versie uit waarmee deze fout is opgelost!

 

Kijk bij de update van het programma.

 

Gr,

 

Irma

 

Irma Lommen – Salden

  irmalom...@home.nl

  www.limburgemigrant.nl

 

Van: Legacy-Nederlands  Namens 
Pierre Debecker
Verzonden: zondag 13 januari 2019 18:03
Aan: Legacy 
Onderwerp: [Legacy-Nederlands] Fout 62 Input past end of file

 

Op 8 januari heb ik hulp gevraagd omtrent de vermelde fout.

Kan iemand mij helpen?

Bedankt op voorhand.

 

Pierre Debecker

-- 
___
Legacy-Nederlands mailing list
Legacy-Nederlands@legacyusers.com
http://legacyusers.com/mailman/listinfo/legacy-nederlands_legacyusers.com

[Legacy-Nederlands] Fout 62 Input past end of file

[Pierre Debecker]

Op 8 januari heb ik hulp gevraagd omtrent de vermelde fout.
Kan iemand mij helpen?
Bedankt op voorhand.

Pierre Debecker
-- 
___
Legacy-Nederlands mailing list
Legacy-Nederlands@legacyusers.com
http://legacyusers.com/mailman/listinfo/legacy-nederlands_legacyusers.com