Re: [LegacyUG] Legacy update still not working - done

[EMB]

Thank you Chris,

but it didn't work at all.

Fortunately I had all my 160.000 people and pictures well saved, so I
deletet Legacy and did a complete new installation of Legacy. Now it
works again!

Regards,

Eva

Am 23.01.2020 um 13:01 schrieb Chris Hill:


A 'File could not be locked' error usually applies when opening an
Access database which the system thinks is already open. Access
creates a lock file .ldb when it opens a file and removes it when
it closes. The main Legacy database, .fdb, is actually an Access
database and opening that will create the .ldb file. If it is
still present after the program is closed it will stop the file being
'reopened'. Sometimes clears after a reboot or might to be deleted
manually after a reboot. May also apply to the x~hdb.hdb and some
of the various .dbm files that Legacy uses.

Regards

Chris

-- Original Message --
From: "EMB" mailto:kurl...@gmx.de>>
To: "Legacy User Group" mailto:legacyusergroup@legacyusers.com>>
Sent: 23/01/2020 11:43:10
Subject: [LegacyUG] Legacy update still not working


Hallo all,
I downloaded the update via my existing program (German). Download was
ok, the new version is existing on my laptop now. But when I try to open
the program I get following message:
Error Opening Message File  - Datei konnte nicht gesperrt werden
I never wanted to "sperren" (means lock) the data.
I tried the download again - without a firewall, nothing changed.
I don't know where to look for this message. Can anybody help?
Eva
--
LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com <mailto:LegacyUserGroup@legacyusers.com>
To manage your subscription and unsubscribe
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/


-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

[LegacyUG] Legacy update still not working

[EMB]

Hallo all,

I downloaded the update via my existing program (German). Download was
ok, the new version is existing on my laptop now. But when I try to open
the program I get following message:

Error Opening Message File  - Datei konnte nicht gesperrt werden

I never wanted to "sperren" (means lock) the data.

I tried the download again - without a firewall, nothing changed.

I don't know where to look for this message. Can anybody help?

Eva


--

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Re: [LegacyUG] Creating gedcom for Export - UTF8 doesn't work properly

[EMB]

Hi, Chris,

yes, I'm German based and it seems to be a problem between filezilla and 
TNG.


I was looking at the files in Notepad++ and evereything was correct. So 
I have to find out what's between filezilla and TNG.


Thank you again for your help.

Regards,

Eva


Am 08.04.2017 um 15:36 schrieb Chris Hill:


Hi Eva

One immediate thought is whether you running a UK or USA language 
settings in Windows – I guess from one of your earlier messages that 
you may be German based. In theory, that should not cause any issues 
but I have had problems like that in the past.


I am UK based and therefore running on the ‘default’ Windows settings. 
From my tree, I have exported, as GEDCOM 5.5.1 using ANSI and UTF8 and 
have got the following address line (extracted from the GEDCOM file 
using Notepad++)


2 PLAC Norrköping, , Östergötlands län, Sweden

When I export it as ANSEL I get

2 PLAC Norrkèoping, , èOstergèotlands lèan, Sweden

which is what I would have expected.

Looking at the files in Notepad++, it is reporting the ANSI and ANSEL 
versions as being ANSI coded and the UTF as being UTF-8-BOM, so I 
presume that the system or Legacy has placed the Unicode header at the 
start of the file. I would need to do some testing and programming to 
prove that.


Your example suggests that Rüdiger consists of upper case R, upper 
case A with tilde and then a One Quarter – in Unicode hex these are 
U-0052, U-00C3 and U-00BC according to Character Map on Arial. I guess 
that the ¼ should be ë (U-00EB), not sure about the case of the Ã. 
What I am not sure about is whether the German? based system uses 
different codings, which used be a problem 20-30 years ago, but should 
not now.**


I think my first question would be to view the text file, using 
Notepad or Notepad++, to ensure that the format is correct. If that 
says it is wrong, then there is a question about Legacy. If the text 
file is good, then the problem is between Filezilla and the TNG site. 
Again, I have seen issues with FTP systems getting data conversions 
wrong, especially if there are multiple versions of UTF and different 
implementations.


Regards

Chris

*From:*LegacyUserGroup 
[mailto:legacyusergroup-boun...@legacyusers.com] *On Behalf Of *EMB

*Sent:* 08 April 2017 13:07
*To:* Legacy User Group <legacyusergroup@legacyusers.com>; 
legacy-deutsch-ow...@legacyusers.com
*Subject:* [LegacyUG] Creating gedcom for Export - UTF8 doesn't work 
properly


Again, a question. Version 8.0.0.595. Maybe more for the German list.

I created a gedcom file: gedcom 5.5.1 UTF8 and uploaded it via 
filezilla (forced UTF8) to a TNG-Website ( German UTF8). All the 
"Umlaute" (*umlaut* is the name of the two small dots above the 
letters A, O, and U in__German 
<https://simple.wikipedia.org/wiki/German_language>.) were wrong. (like


Rüdiger-).

Before I used creating a gedcom 5.5.1 and ANSI. There everything was 
correct. But I wanted to change to UTF8. What do I do wrong again? Or 
does it not work in Legacy?


Maybe one of you knows how to do properly.

Regards,

Eva B.





-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

[LegacyUG] Creating gedcom for Export - UTF8 doesn't work properly

[EMB]

Again, a question. Version 8.0.0.595. Maybe more for the German list.

I created a gedcom file: gedcom 5.5.1 UTF8 and uploaded it via filezilla 
(forced UTF8) to a TNG-Website ( German UTF8). All the "Umlaute" 
(*umlaut* is the name of the two small dots above the letters A, O, and 
U in__German .) were 
wrong. (like


Rüdiger-).

Before I used creating a gedcom 5.5.1 and ANSI. There everything was 
correct. But I wanted to change to UTF8. What do I do wrong again? Or 
does it not work in Legacy?


Maybe one of you knows how to do properly.

Regards,

Eva B.


-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Re: [LegacyUG] creating a gedcom file in 8.5.. very slow

[EMB]

Hi, Cathy,

yes you were right!!! I think I was mentally blocked ... as I didn't 
understand in time.


I have excluded Shared Events (in German: "Mehrfach genutzte 
Ereignisse") now and the gedcom run faster than ever - in 7 minutes 
finished.


Thank you so much ... especially for your patience.

Eva


Am 07.04.2017 um 13:54 schrieb Cathy Pinner:

Here is the reason that Gedcom Export is taking longer.

I gave the answer from memory a few days ago.
I've now looked up the Bug tracker and there are two issues logged.

Whether or not you have used Shared Events, if you don't exclude 
Shared Events from your Gedcom Export, the Export is taking from 3 to 
10 times longer than when you do exclude Shared Events.


Cathy
Beta Tester with a long memory.

EMB wrote:


Ernie, that's a nice idea buying a faster computer! But that's not the
point.

I wonder why there is the significant difference between version 7.5
and 8 in creating a gedcom.

Cheers, Eva

But


If you really want to kick your computer into warp drive, buy a solid
state hard drive (SSD) it has 39 channels that run your data on.  
It bsp;

took me 4 hours to run a relationship on a 800,000 name file on a
standard hard drive and with the SSD it took only four minutes.  I
am  using a quad four with 8 gig of ram and a SSD.  You can figure
out the math yourself.
Cheers,
Ernie

You will always have neighbors, but not parents!

On Thu, Apr 6, 2017 at 6:34 AM, Chris Hill
<chris.hill.11he...@gmail.com <mailto:chris.hill.11he...@gmail.com>>
wrote:

I don’t think that Shared Events should cause an issue.
Potentially, a minimal impact making the _SHAR records against
not having to produce the multiple copies for the other individuals.

Looking at a test export I can see that the event, in my case
census events, is exported from the MASTER copy with a _SHAR
record to link it to the other indiv iduals it is shared with, and
that it is NOT exported in their details (which also suggests
that shared events should be exported if the target does not
support shared events or with an option to include or exclude them).

It would be worth running a backup, and then check and compress
on the database. There is always the possibility that the
internal tables in the database have extended and the compress
would make it faster for access. Having V7.5 present is not an
issue, though once you have moved to V8 you will have no need for
it (but just ensure that there are none of your files there
before you remove it).

Otherwise, I would suggest raising it as an issue with Legacy –
Tools / Support Tic ket – especially if the same issues occur on a
different PC.

Chris

*From:*LegacyUserGroup
[mailto:legacyusergroup-boun...@legacyusers.com
<mailto:legacyusergroup-boun...@legacyusers.com>] *On Behalf Of *EMB
*Sent:* 06 April 2017 13:02
*To:* legacyusergroup@legacyusers.com
<mailto:legacyusergroup@legacyusers.com>
*Subject:* Re: [LegacyUG] creating a gedcom file in 8.5.. very slow

Thanks, Chris and Cathy.

 I did exactly everything in 8.0.0.595 as I did in 7.5. before. I
had exactly the same data - nothing else. I exported gedcom 5.5.1
in UTF-8 as I have to upload to a TNG-Website monthly. And I
exported from the same comput er as I always do. My system is
i5-4210M  8 GB (as I don't use games at all).

I don't know which Shared Events I could exclude (my english is
not perfect enough to understand).

Could it be that I have those time problems as I still have 7.5
on my computer? But I can't imagine.

At the moment I try to export - all the same - on a different new
Windows 10 computer. I'll see what happens. But I noticed already
it started as slow as the other one. I have Legacy 8.0.0.595
installed there as well (not network).

Any more ideas??

Thanks in advance

Eva B.

Am 06.04.2017 um 11:48 schrieb Cathy Pinner:

I think it's to do with Shared Events. Try excluding them
under Customise button.
I'm sure someone will correct me if I'm wrong - I'm
remembering conversations around the time Legacy 8 was
released. I hardly use Shared Events and rarely make a gedcom
that includes Events.

Cathy

Chris Hill wrote:


Hi

I have just run an export, Legacy format, for my system -
10119 people, 3159
   & nbsp;families and minimal sources - in 34 seconds. That 
would

suggest a 9 minute
run time for 15 people and families. My system is an
i7-6700 with 32GB
of RAM since it is a gaming system.

So, your time of 20 minutes from 7.5 seems reasonable.
When comparing that
to the current, 8.0.0.595 not 8.5 version, there must be
something else that
 bsp;   has cha

Re: [LegacyUG] creating a gedcom file in 8.5.. very slow

[EMB]

Ernie, that's a nice idea buying a faster computer! But that's not the 
point.


I wonder why there is the significant difference between version 7.5 and 
8 in creating a gedcom.


Cheers, Eva

But
If you really want to kick your computer into warp drive, buy a solid 
state hard drive (SSD) it has 39 channels that run your data on.  It  
took me 4 hours to run a relationship on a 800,000 name file on a 
standard hard drive and with the SSD it took only four minutes.  I am  
using a quad four with 8 gig of ram and a SSD.  You can figure out the 
math yourself.

Cheers,
Ernie

You will always have neighbors, but not parents!

On Thu, Apr 6, 2017 at 6:34 AM, Chris Hill 
<chris.hill.11he...@gmail.com <mailto:chris.hill.11he...@gmail.com>> 
wrote:


I don’t think that Shared Events should cause an issue.
Potentially, a minimal impact making the _SHAR records against not
having to produce the multiple copies for the other individuals.

Looking at a test export I can see that the event, in my case
census events, is exported from the MASTER copy with a _SHAR
record to link it to the other individuals it is shared with, and
that it is NOT exported in their details (which also suggests that
shared events should be exported if the target does not support
shared events or with an option to include or exclude them).

It would be worth running a backup, and then check and compress on
the database. There is always the possibility that the internal
tables in the database have extended and the compress would make
it faster for access. Having V7.5 present is not an issue, though
once you have moved to V8 you will have no need for it (but just
ensure that there are none of your files there before you remove it).

Otherwise, I would suggest raising it as an issue with Legacy –
Tools / Support Ticket – especially if the same issues occur on a
different PC.

Chris

*From:*LegacyUserGroup
[mailto:legacyusergroup-boun...@legacyusers.com
<mailto:legacyusergroup-boun...@legacyusers.com>] *On Behalf Of *EMB
*Sent:* 06 April 2017 13:02
*To:* legacyusergroup@legacyusers.com
<mailto:legacyusergroup@legacyusers.com>
*Subject:* Re: [LegacyUG] creating a gedcom file in 8.5.. very slow

Thanks, Chris and Cathy.

 I did exactly everything in 8.0.0.595 as I did in 7.5. before. I
had exactly the same data - nothing else. I exported gedcom 5.5.1
in UTF-8 as I have to upload to a TNG-Website monthly. And I
exported from the same computer as I always do. My system is
i5-4210M  8 GB (as I don't use games at all).

I don't know which Shared Events I could exclude (my english is
not perfect enough to understand).

Could it be that I have those time problems as I still have 7.5 on
my computer? But I can't imagine.

At the moment I try to export - all the same - on a different new
Windows 10 computer. I'll see what happens. But I noticed already
it started as slow as the other one. I have Legacy 8.0.0.595
installed there as well (not network).

Any more ideas??

Thanks in advance

Eva B.

Am 06.04.2017 um 11:48 schrieb Cathy Pinner:

I think it's to do with Shared Events. Try excluding them
under Customise button.
I'm sure someone will correct me if I'm wrong - I'm
remembering conversations around the time Legacy 8 was
released. I hardly use Shared Events and rarely make a gedcom
that includes Events.

Cathy

Chris Hill wrote:


Hi

I have just run an export, Legacy format, for my system -
10119 people, 3159
families and minimal sources - in 34 seconds. That would
suggest a 9 minute
run time for 15 people and families. My system is an
i7-6700 with 32GB
of RAM since it is a gaming system.

So, your time of 20 minutes from 7.5 seems reasonable.
When comparing that
to the current, 8.0.0.595 not 8.5 version, there must be
something else that
has changed. Were you comparing the same data or have you
added a lot more
informatio n to the individuals and a lot of sources
referred all over the
place. Even so, that might only double the run time.

Otherwise, I would be considering if the target for the
export was not on
the PC hard drive but on to a USB or network device. The
next option would
be whether there is a performance problem at the PC level
or some running
software which is using the processor.

Hope this helps, but we really need to know why about what
is happening.

Regards

Chris
-Original Message-
 

Re: [LegacyUG] creating a gedcom file in 8.5.. very slow

[EMB]

Thanks, Chris and Cathy.

 I did exactly everything in 8.0.0.595 as I did in 7.5. before. I had 
exactly the same data - nothing else. I exported gedcom 5.5.1 in UTF-8 
as I have to upload to a TNG-Website monthly. And I exported from the 
same computer as I always do. My system is i5-4210M  8 GB (as I don't 
use games at all).


I don't know which Shared Events I could exclude (my english is not 
perfect enough to understand).


Could it be that I have those time problems as I still have 7.5 on my 
computer? But I can't imagine.


At the moment I try to export - all the same - on a different new 
Windows 10 computer. I'll see what happens. But I noticed already it 
started as slow as the other one. I have Legacy 8.0.0.595 installed 
there as well (not network).


Any more ideas??

Thanks in advance

Eva B.


Am 06.04.2017 um 11:48 schrieb Cathy Pinner:
I think it's to do with Shared Events. Try excluding them under 
Customise button.
I'm sure someone will correct me if I'm wrong - I'm remembering 
conversations around the time Legacy 8 was released. I hardly use 
Shared Events and rarely make a gedcom that includes Events.


Cathy

Chris Hill wrote:


Hi

I have just run an export, Legacy format, for my system - 10119 
people, 3159
families and minimal sources - in 34 seconds. That would suggest a 9 
minute
run time for 15 people and families. My system is an i7-6700 with 
32GB

of RAM since it is a gaming system.

So, your time of 20 minutes from 7.5 seems reasonable. When comparing 
that
to the current, 8.0.0.595 not 8.5 version, there must be something 
else that
has changed. Were you comparing the same data or have you added a lot 
more
informatio n to the individuals and a lot of sources referred all 
over the

place. Even so, that might only double the run time.

Otherwise, I would be considering if the target for the export was not on
the PC hard drive but on to a USB or network device. The next option 
would

be whether there is a performance problem at the PC level or some running
software which is using the processor.

Hope this helps, but we really need to know why about what is happening.

Regards

Chris
-Original Message-
From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] On
Behalf Of EMB
Sent: 06 April 2017 09:50
To: Legacy User Group<legacyusergroup@legacyusers.com>
Subject: [LegacyUG] creating a gedcom file in 8.5.. very slow

Who can help?

When I created a gedcom file in 7.5 of 150.000 persons it took 20 
minutes.
Now I updated to the newest 8.5.. and now it takes more than 4 hours 
to d o

the same!

Does anybody know what happened? Or could I've done something wrong in
updating???

Thanks for any help!

Eva B.





-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

[LegacyUG] creating a gedcom file in 8.5.. very slow

[EMB]

Who can help?

When I created a gedcom file in 7.5 of 150.000 persons it took 20 
minutes. Now I updated to the newest 8.5.. and now it takes more than 4 
hours to do the same!


Does anybody know what happened? Or could I've done something wrong in 
updating???


Thanks for any help!

Eva B.


--

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/