Re: [LegacyUG] Can I have both Legacy 7 and Legacy 9 running concurrently (different data file)?

[Ian Thomas]

Another 'solution' to having Legacy 8 Deluxe (NOT v7 or 7.5) and Legacy 9 
running on the same computer is to rename the family file (.fdb) within the 
installed Legacy v9, then install your v8 with its v8 Customer Number. This may 
require extraction of the "v8" files from the latest v8 backup ZIP files - 2 of 
them, both database and media. The newly-installed v8 would 'look for' the 
family file database files with the previous filenames; the v9 new install 
would 'know about' the renamed database.

Given the wide range of (in)experience of Legacy users exhibited here, I would 
warn that this does require some 'advanced' knowledge of computer use.

As expressed by Bob and Kris, I was surprised that the Legacy v8 was totally 
removed by the v9 install - except for the backup ZIP files and the database 
files, which Legacy v9 restructured so that v8 is not able to use them. I 
checked C:\Program Files (x86)\ folder, of course - and see only C:\Program 
Files (x86)\Legacy9\

As I wrote previously, there are a couple of glitches with the install, which I 
thought should not have happened from a professional organization. This is 
quite independent of testing by users and by the coders - but I would assume 
that user testers would have objected to this replacement.

Ian Thomas

Albert Park, Victoria 3206 Australia





-Original Message-
From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] On 
Behalf Of Bob Austen
Sent: Thursday, 20 April 2017 3:55 AM
To: 'Legacy User Group' <legacyusergroup@legacyusers.com>
Subject: Re: [LegacyUG] Can I have both Legacy 7 and Legacy 9 running 
concurrently (different data file)?



I renamed my Legacy8 folders before installing v9 so I can now run both v8 and 
v9 concurrently (after naming the v8 files back to the original).  Of course 
the databases are different as v9 has converted the database to the new version 
- however, I had made copies of the database as well.



Some attributes of v9 show up in v8 now so There must be some overlap in the 
user file settings.



Any file changes made in v9 will not be reflected in the 'old' v8 database.

I would suggest that for most people not being able to run the two versions 
concurrently should not be an issue.  I have some family that won't be 
upgrading to v9 anytime soon and I still help them so I just wanted to be able 
to use the same version.



Bob



-Original Message-

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

Sent: Wednesday, April 19, 2017 9:25 AM

To: Legacy User Group

Subject: Re: [LegacyUG] Can I have both Legacy 7 and Legacy 9 running 
concurrently (different data file)?



I agree with Robert, and taking it even further (sorry!), I disagree with the 
Sherry's statement (below).  While it is true that pretty much every program 
will install over an existing version for "updating," this is not the case for 
"upgrading."  Updates for v.8 should install in the Legacy 8 directory, but v.9 
shouldn't remove or install over an existing version of a different number -- 
it should have its own directory, as Robert indicates, and leave previous 
versions alone.



I don't recall ever installing a new version of a program that 
overwrites/deletes a previous version without asking for instructions from me 
first.  This case is particularly troubling since Legacy 8 and Legacy 9 have 
different directory names, and Legacy 8 is apparently "gone."  The installer 
seems to be doing something to Legacy 8 that it shouldn't be doing.



Any new version of a program is going to have issues -- some more significant 
than others -- and users shouldn't be required to commit until these bugs are 
found and corrected.  Anyone who installs a brand new version in its infancy is 
basically beta testing and it's the user who should be in control of that role.



I think it's great that Legacy support posted information about good practices 
(backup, check file, etc.), but there are good practices for software 
developers, too.



I'm not sure why it's set up this way, but don't think saving "support a lot of 
headaches" would be the reason.  Obviously, it's just caused new and different 
ones.  :-D



I've looked through the new features, and v.9 isn't for me unless the report 
formatting problems have been fixed this time.



On 4/19/2017 10:41 AM, Robert57P_gmail wrote:

> Sherry,

>

> While technically it really doesn't matter, but I beg to differ with

> your comment.

> My Legacy 8 was installed at:

> C:\Program Files (x86)\Legacy8

>

> My Legacy 9 got installed to:

> C:\Program Files (x86)\Legacy9

>

> Note the version # at the very end of the folder name.  So Legacy 9 is

> either deleting the old Legacy8 folders, or it is renaming them.

>

> Seeing the different folder names is why I thought I was safe, why I

> thought I'd be able to have

Re: [LegacyUG] Can I have both Legacy 7 and Legacy 9 running concurrently (different data file)?

[Bob Austen]

I renamed my Legacy8 folders before installing v9 so I can now run both v8
and v9 concurrently (after naming the v8 files back to the original).  Of
course the databases are different as v9 has converted the database to the
new version - however, I had made copies of the database as well.  

Some attributes of v9 show up in v8 now so There must be some overlap in the
user file settings.

Any file changes made in v9 will not be reflected in the 'old' v8 database.
I would suggest that for most people not being able to run the two versions
concurrently should not be an issue.  I have some family that won't be
upgrading to v9 anytime soon and I still help them so I just wanted to be
able to use the same version.

Bob

-Original Message-
From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] On
Behalf Of Kris
Sent: Wednesday, April 19, 2017 9:25 AM
To: Legacy User Group
Subject: Re: [LegacyUG] Can I have both Legacy 7 and Legacy 9 running
concurrently (different data file)?

I agree with Robert, and taking it even further (sorry!), I disagree 
with the Sherry's statement (below).  While it is true that pretty much 
every program will install over an existing version for "updating," this 
is not the case for "upgrading."  Updates for v.8 should install in the 
Legacy 8 directory, but v.9 shouldn't remove or install over an existing 
version of a different number -- it should have its own directory, as 
Robert indicates, and leave previous versions alone.

I don't recall ever installing a new version of a program that 
overwrites/deletes a previous version without asking for instructions 
from me first.  This case is particularly troubling since Legacy 8 and 
Legacy 9 have different directory names, and Legacy 8 is apparently 
"gone."  The installer seems to be doing something to Legacy 8 that it 
shouldn't be doing.

Any new version of a program is going to have issues -- some more 
significant than others -- and users shouldn't be required to commit 
until these bugs are found and corrected.  Anyone who installs a brand 
new version in its infancy is basically beta testing and it's the user 
who should be in control of that role.

I think it's great that Legacy support posted information about good 
practices (backup, check file, etc.), but there are good practices for 
software developers, too.

I'm not sure why it's set up this way, but don't think saving "support a 
lot of headaches" would be the reason.  Obviously, it's just caused new 
and different ones.  :-D

I've looked through the new features, and v.9 isn't for me unless the 
report formatting problems have been fixed this time.

On 4/19/2017 10:41 AM, Robert57P_gmail wrote:
> Sherry,
>
> While technically it really doesn't matter, but I beg to differ with
> your comment.
> My Legacy 8 was installed at:
> C:\Program Files (x86)\Legacy8
>
> My Legacy 9 got installed to:
> C:\Program Files (x86)\Legacy9
>
> Note the version # at the very end of the folder name.  So Legacy 9 is
> either deleting the old Legacy8 folders, or it is renaming them.
>
> Seeing the different folder names is why I thought I was safe, why I
> thought I'd be able to have both 8 (deluxe) and 9 (basic) installed at
> the same time.
>
> I realize that "installing on top of" the old version (or "installing
> and DELETING/RENAMING old version as Legacy 9 apparently does") saves
> support a lot of headaches - I remember many forum e-mails from people
> going from 7 to 8 that kept getting confused on which icon to use, which
> datafile to use, etc.  But since all(?) previous versions of Legacy
> allowed the old version to stay in place, this version should either do
> the same ('cause that is what Legacy users are used to) OR it should
> give an obvious warning that version 8 will NOT be available after the
> install.  A blatant warning is ESPECIALLY important since the program
> folder names are different and thus the install (as it is now) IMPLIES
> that version 8 will be "safe and usable" after version 9 is installed.
> (And, if it could offer to leave version 8 around that would even be
> better).
>
> If I had known my version 8 would be blown away, I would have initially
> installed version 9 in a "sandbox" (VM machine) until I was truly ready
> to do the real upgrade.
>
> Bob
>
> On 04/18/2017 20:48, Sherry wrote:
>> Margaret,
>>
>> v9 doesn't "delete" v8 - it installs over it, like practically every
>> other program does when upgrading.



-- 

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] Can I have both Legacy 7 and Legacy 9 running concurrently (different data file)?

[Kris]

I agree with Robert, and taking it even further (sorry!), I disagree 
with the Sherry's statement (below).  While it is true that pretty much 
every program will install over an existing version for "updating," this 
is not the case for "upgrading."  Updates for v.8 should install in the 
Legacy 8 directory, but v.9 shouldn't remove or install over an existing 
version of a different number -- it should have its own directory, as 
Robert indicates, and leave previous versions alone.


I don't recall ever installing a new version of a program that 
overwrites/deletes a previous version without asking for instructions 
from me first.  This case is particularly troubling since Legacy 8 and 
Legacy 9 have different directory names, and Legacy 8 is apparently 
"gone."  The installer seems to be doing something to Legacy 8 that it 
shouldn't be doing.


Any new version of a program is going to have issues -- some more 
significant than others -- and users shouldn't be required to commit 
until these bugs are found and corrected.  Anyone who installs a brand 
new version in its infancy is basically beta testing and it's the user 
who should be in control of that role.


I think it's great that Legacy support posted information about good 
practices (backup, check file, etc.), but there are good practices for 
software developers, too.


I'm not sure why it's set up this way, but don't think saving "support a 
lot of headaches" would be the reason.  Obviously, it's just caused new 
and different ones.  :-D


I've looked through the new features, and v.9 isn't for me unless the 
report formatting problems have been fixed this time.


On 4/19/2017 10:41 AM, Robert57P_gmail wrote:

Sherry,

While technically it really doesn't matter, but I beg to differ with
your comment.
My Legacy 8 was installed at:
C:\Program Files (x86)\Legacy8

My Legacy 9 got installed to:
C:\Program Files (x86)\Legacy9

Note the version # at the very end of the folder name.  So Legacy 9 is
either deleting the old Legacy8 folders, or it is renaming them.

Seeing the different folder names is why I thought I was safe, why I
thought I'd be able to have both 8 (deluxe) and 9 (basic) installed at
the same time.

I realize that "installing on top of" the old version (or "installing
and DELETING/RENAMING old version as Legacy 9 apparently does") saves
support a lot of headaches - I remember many forum e-mails from people
going from 7 to 8 that kept getting confused on which icon to use, which
datafile to use, etc.  But since all(?) previous versions of Legacy
allowed the old version to stay in place, this version should either do
the same ('cause that is what Legacy users are used to) OR it should
give an obvious warning that version 8 will NOT be available after the
install.  A blatant warning is ESPECIALLY important since the program
folder names are different and thus the install (as it is now) IMPLIES
that version 8 will be "safe and usable" after version 9 is installed.
(And, if it could offer to leave version 8 around that would even be
better).

If I had known my version 8 would be blown away, I would have initially
installed version 9 in a "sandbox" (VM machine) until I was truly ready
to do the real upgrade.

Bob

On 04/18/2017 20:48, Sherry wrote:

Margaret,

v9 doesn't "delete" v8 - it installs over it, like practically every
other program does when upgrading.


--

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] Can I have both Legacy 7 and Legacy 9 running concurrently (different data file)?

[Ernie Anderson]

Why don't you install 8 on a flash drive and remove it and then install 9
on your hard drive., then you can run them both at the same time.
Ernie

You will always have neighbors, but not parents!

On Wed, Apr 19, 2017 at 9:41 AM, Robert57P_gmail 
wrote:

> Sherry,
>
> While technically it really doesn't matter, but I beg to differ with your
> comment.
> My Legacy 8 was installed at:
> C:\Program Files (x86)\Legacy8
>
> My Legacy 9 got installed to:
> C:\Program Files (x86)\Legacy9
>
> Note the version # at the very end of the folder name.  So Legacy 9 is
> either deleting the old Legacy8 folders, or it is renaming them.
>
> Seeing the different folder names is why I thought I was safe, why I
> thought I'd be able to have both 8 (deluxe) and 9 (basic) installed at the
> same time.
>
> I realize that "installing on top of" the old version (or "installing and
> DELETING/RENAMING old version as Legacy 9 apparently does") saves support a
> lot of headaches - I remember many forum e-mails from people going from 7
> to 8 that kept getting confused on which icon to use, which datafile to
> use, etc.  But since all(?) previous versions of Legacy allowed the old
> version to stay in place, this version should either do the same ('cause
> that is what Legacy users are used to) OR it should give an obvious warning
> that version 8 will NOT be available after the install.  A blatant warning
> is ESPECIALLY important since the program folder names are different and
> thus the install (as it is now) IMPLIES that version 8 will be "safe and
> usable" after version 9 is installed.  (And, if it could offer to leave
> version 8 around that would even be better).
>
> If I had known my version 8 would be blown away, I would have initially
> installed version 9 in a "sandbox" (VM machine) until I was truly ready to
> do the real upgrade.
>
> Bob
>
> On 04/18/2017 20:48, Sherry wrote:
>
>> Margaret,
>>
>> v9 doesn't "delete" v8 - it installs over it, like practically every
>> other program does when upgrading.
>>
>> You can run v7 and v9 side-by-side but the files are not compatible. You
>> will have to covert a v7 file to the v9 format and in v9 you will need to
>> make a gedcom to import into v7, which can lose several things like shared
>> events, hashtags, history list, bookmarks, relationships, etc.
>>
>> Did you realize that LTools doesn't fully support the v7 database,
>> particularly events? It should work with the v8 or v9 database (except for
>> events). I haven't tried it yet.
>>
>> Sherry
>>
>>
>>
>> On Tue, Apr 18, 2017 at 5:38 PM, Margaret Turner > > wrote:
>>
>> I understand installing v9 deletes v8.
>>  I would like to have both versions instlled.
>> I would do changes in v7, and when required, copy legacy data file
>> and open it (ie no updates) in 9.
>> Then I would go back to work on v7 data using v7
>>
>> I am dependent on ltools.
>>
>> Thanks
>>
>> :)
>>
>> Margaret
>>
>>
>>
>>
>>
>
> --
>
> 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/
>
-- 

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] Can I have both Legacy 7 and Legacy 9 running concurrently (different data file)?

[Robert57P_gmail]

Sherry,

While technically it really doesn't matter, but I beg to differ with 
your comment.

My Legacy 8 was installed at:
C:\Program Files (x86)\Legacy8

My Legacy 9 got installed to:
C:\Program Files (x86)\Legacy9

Note the version # at the very end of the folder name.  So Legacy 9 is 
either deleting the old Legacy8 folders, or it is renaming them.


Seeing the different folder names is why I thought I was safe, why I 
thought I'd be able to have both 8 (deluxe) and 9 (basic) installed at 
the same time.


I realize that "installing on top of" the old version (or "installing 
and DELETING/RENAMING old version as Legacy 9 apparently does") saves 
support a lot of headaches - I remember many forum e-mails from people 
going from 7 to 8 that kept getting confused on which icon to use, which 
datafile to use, etc.  But since all(?) previous versions of Legacy 
allowed the old version to stay in place, this version should either do 
the same ('cause that is what Legacy users are used to) OR it should 
give an obvious warning that version 8 will NOT be available after the 
install.  A blatant warning is ESPECIALLY important since the program 
folder names are different and thus the install (as it is now) IMPLIES 
that version 8 will be "safe and usable" after version 9 is installed.  
(And, if it could offer to leave version 8 around that would even be 
better).


If I had known my version 8 would be blown away, I would have initially 
installed version 9 in a "sandbox" (VM machine) until I was truly ready 
to do the real upgrade.


Bob

On 04/18/2017 20:48, Sherry wrote:

Margaret,

v9 doesn't "delete" v8 - it installs over it, like practically every 
other program does when upgrading.


You can run v7 and v9 side-by-side but the files are not compatible. 
You will have to covert a v7 file to the v9 format and in v9 you will 
need to make a gedcom to import into v7, which can lose several things 
like shared events, hashtags, history list, bookmarks, relationships, etc.


Did you realize that LTools doesn't fully support the v7 database, 
particularly events? It should work with the v8 or v9 database (except 
for events). I haven't tried it yet.


Sherry



On Tue, Apr 18, 2017 at 5:38 PM, Margaret Turner > wrote:


I understand installing v9 deletes v8.
 I would like to have both versions instlled.
I would do changes in v7, and when required, copy legacy data file
and open it (ie no updates) in 9.
Then I would go back to work on v7 data using v7

I am dependent on ltools.

Thanks

:)

Margaret







--

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] Can I have both Legacy 7 and Legacy 9 running concurrently (different data file)?

[Margaret Turner]

I worded the question very badly.
Thanks
:)
Margaret

On 19 April 2017 at 13:09, Margaret Turner  wrote:

> Thanks Larry.
> I did not want running concurrently, but both installed , so I could run
> the version I wanted at that time, as required.
> :)
> Margaret
>
> On 19 April 2017 at 12:09, Larry Maddocks  wrote:
>
>> FYI,
>>
>> You can have two instances of Legacy running simultaneously, even the
>> same version.  One instance would run in a separate environment using
>> sandboxie, a windows app.  When you run it, it makes it's own copy of data
>> files that it edits.  I won't go into detail, but sometimes I find it
>> useful.  Or you can have one version of Legacy with two windows with their
>> own data files.  Sometimes that crashes the program, though, unless that
>> bug has been fixed. -- Larry
>>
>> On 4/18/2017 6:55 PM, Margaret Turner wrote:
>>
>> Thanks Sherry.
>> I was not clear in my posting, I do realise the data files are not
>> compatible.
>> Will check out LTools and v9 later.
>> Thanks
>> :)
>> Margaret
>>
>> On 19 April 2017 at 10:48, Sherry  wrote:
>>
>>> Margaret,
>>>
>>> v9 doesn't "delete" v8 - it installs over it, like practically every
>>> other program does when upgrading.
>>>
>>> You can run v7 and v9 side-by-side but the files are not compatible. You
>>> will have to covert a v7 file to the v9 format and in v9 you will need to
>>> make a gedcom to import into v7, which can lose several things like shared
>>> events, hashtags, history list, bookmarks, relationships, etc.
>>>
>>> Did you realize that LTools doesn't fully support the v7 database,
>>> particularly events? It should work with the v8 or v9 database (except for
>>> events). I haven't tried it yet.
>>>
>>> Sherry
>>>
>>>
>>>
>>> On Tue, Apr 18, 2017 at 5:38 PM, Margaret Turner 
>>> wrote:
>>>
 I understand installing v9 deletes v8.
  I would like to have both versions instlled.
 I would do changes in v7, and when required, copy legacy data file and
 open it (ie no updates) in 9.
 Then I would go back to work on v7 data using v7

 I am dependent on ltools.

 Thanks

 :)

 Margaret


>>>
>>>
-- 

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] Can I have both Legacy 7 and Legacy 9 running concurrently (different data file)?

[Margaret Turner]

Thanks Larry.
I did not want running concurrently, but both installed , so I could run
the version I wanted at that time, as required.
:)
Margaret

On 19 April 2017 at 12:09, Larry Maddocks  wrote:

> FYI,
>
> You can have two instances of Legacy running simultaneously, even the same
> version.  One instance would run in a separate environment using sandboxie,
> a windows app.  When you run it, it makes it's own copy of data files that
> it edits.  I won't go into detail, but sometimes I find it useful.  Or you
> can have one version of Legacy with two windows with their own data files.
> Sometimes that crashes the program, though, unless that bug has been fixed.
> -- Larry
>
> On 4/18/2017 6:55 PM, Margaret Turner wrote:
>
> Thanks Sherry.
> I was not clear in my posting, I do realise the data files are not
> compatible.
> Will check out LTools and v9 later.
> Thanks
> :)
> Margaret
>
> On 19 April 2017 at 10:48, Sherry  wrote:
>
>> Margaret,
>>
>> v9 doesn't "delete" v8 - it installs over it, like practically every
>> other program does when upgrading.
>>
>> You can run v7 and v9 side-by-side but the files are not compatible. You
>> will have to covert a v7 file to the v9 format and in v9 you will need to
>> make a gedcom to import into v7, which can lose several things like shared
>> events, hashtags, history list, bookmarks, relationships, etc.
>>
>> Did you realize that LTools doesn't fully support the v7 database,
>> particularly events? It should work with the v8 or v9 database (except for
>> events). I haven't tried it yet.
>>
>> Sherry
>>
>>
>>
>> On Tue, Apr 18, 2017 at 5:38 PM, Margaret Turner 
>> wrote:
>>
>>> I understand installing v9 deletes v8.
>>>  I would like to have both versions instlled.
>>> I would do changes in v7, and when required, copy legacy data file and
>>> open it (ie no updates) in 9.
>>> Then I would go back to work on v7 data using v7
>>>
>>> I am dependent on ltools.
>>>
>>> Thanks
>>>
>>> :)
>>>
>>> Margaret
>>>
>>>
>>
>>
>
>
>
>
> --
>
> 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/
>
>
-- 

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] Can I have both Legacy 7 and Legacy 9 running concurrently (different data file)?

[Larry Maddocks]

FYI,

You can have two instances of Legacy running simultaneously, even the 
same version.  One instance would run in a separate environment using 
sandboxie, a windows app.  When you run it, it makes it's own copy of 
data files that it edits.  I won't go into detail, but sometimes I find 
it useful.  Or you can have one version of Legacy with two windows with 
their own data files. Sometimes that crashes the program, though, unless 
that bug has been fixed. -- Larry



On 4/18/2017 6:55 PM, Margaret Turner wrote:

Thanks Sherry.
I was not clear in my posting, I do realise the data files are not 
compatible.

Will check out LTools and v9 later.
Thanks
:)
Margaret

On 19 April 2017 at 10:48, Sherry > wrote:


Margaret,

v9 doesn't "delete" v8 - it installs over it, like practically
every other program does when upgrading.

You can run v7 and v9 side-by-side but the files are not
compatible. You will have to covert a v7 file to the v9 format and
in v9 you will need to make a gedcom to import into v7, which can
lose several things like shared events, hashtags, history list,
bookmarks, relationships, etc.

Did you realize that LTools doesn't fully support the v7 database,
particularly events? It should work with the v8 or v9 database
(except for events). I haven't tried it yet.

Sherry



On Tue, Apr 18, 2017 at 5:38 PM, Margaret Turner
> wrote:

I understand installing v9 deletes v8.
 I would like to have both versions instlled.
I would do changes in v7, and when required, copy legacy data
file and open it (ie no updates) in 9.
Then I would go back to work on v7 data using v7

I am dependent on ltools.

Thanks

:)

Margaret








-- 

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] Can I have both Legacy 7 and Legacy 9 running concurrently (different data file)?

[Margaret Turner]

Thanks Sherry.
I was not clear in my posting, I do realise the data files are not
compatible.
Will check out LTools and v9 later.
Thanks
:)
Margaret

On 19 April 2017 at 10:48, Sherry  wrote:

> Margaret,
>
> v9 doesn't "delete" v8 - it installs over it, like practically every other
> program does when upgrading.
>
> You can run v7 and v9 side-by-side but the files are not compatible. You
> will have to covert a v7 file to the v9 format and in v9 you will need to
> make a gedcom to import into v7, which can lose several things like shared
> events, hashtags, history list, bookmarks, relationships, etc.
>
> Did you realize that LTools doesn't fully support the v7 database,
> particularly events? It should work with the v8 or v9 database (except for
> events). I haven't tried it yet.
>
> Sherry
>
>
>
> On Tue, Apr 18, 2017 at 5:38 PM, Margaret Turner 
> wrote:
>
>> I understand installing v9 deletes v8.
>>  I would like to have both versions instlled.
>> I would do changes in v7, and when required, copy legacy data file and
>> open it (ie no updates) in 9.
>> Then I would go back to work on v7 data using v7
>>
>> I am dependent on ltools.
>>
>> Thanks
>>
>> :)
>>
>> Margaret
>>
>>
>
>
-- 

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] Can I have both Legacy 7 and Legacy 9 running concurrently (different data file)?

[Sherry]

Margaret,

v9 doesn't "delete" v8 - it installs over it, like practically every other
program does when upgrading.

You can run v7 and v9 side-by-side but the files are not compatible. You
will have to covert a v7 file to the v9 format and in v9 you will need to
make a gedcom to import into v7, which can lose several things like shared
events, hashtags, history list, bookmarks, relationships, etc.

Did you realize that LTools doesn't fully support the v7 database,
particularly events? It should work with the v8 or v9 database (except for
events). I haven't tried it yet.

Sherry



On Tue, Apr 18, 2017 at 5:38 PM, Margaret Turner 
wrote:

> I understand installing v9 deletes v8.
>  I would like to have both versions instlled.
> I would do changes in v7, and when required, copy legacy data file and
> open it (ie no updates) in 9.
> Then I would go back to work on v7 data using v7
>
> I am dependent on ltools.
>
> Thanks
>
> :)
>
> Margaret
>
>
-- 

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] Can I have both Legacy 7 and Legacy 9 running concurrently (different data file)?

[Margaret Turner]

I understand installing v9 deletes v8.
 I would like to have both versions instlled.
I would do changes in v7, and when required, copy legacy data file and open
it (ie no updates) in 9.
Then I would go back to work on v7 data using v7

I am dependent on ltools.

Thanks

:)

Margaret
-- 

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/