I’ve only just caught up with this thread but wondered if the following
suggestion might help.
I am assuming that you are using Legacy v7 and that your sources are in the
‘old format’ rather than SourceWriter. I don’t use Sourcewriter so I’m not
familiar how it exports into a Gedcom.
If you download a previous version of Legacy e.g. v6 you can run both versions
at the same time as long as you install them into separate folders e.g.
c:\legacy and c:\legacy6. The steps are as follows:-
1. Download a previous version of Legacy from
http://www.legacyfamilytree.com/helpDownloadVersion6.asp and install into a
separate folder from your existing installation.
2. Open your old database in Legacy v7 and export the data into Gedcom
5.5 format.
3. Open Legacy v6, create a new empty database and import the Gedcom
created in Step2. You can drag this database to your 2nd monitor so that you
can see both databases at once. I find that having different colour schemes
for each version of Legacy helps me identify which database is which.
This way, you can have 2 versions of your database open on both monitors – a
‘read only’ copy in Legacy v6 and your new database in Legacy v7 into which you
can transcribe the information that you want.
I’ve just tried this with one of my databases and it was simple to do.
Kind regards
Gill
From: Ian GARDENER [mailto:[email protected]]
Sent: 25 June 2012 13:01
To: [email protected]
Subject: RE: [LegacyUG] Legacy split screen view on 2 monitors
Hmmm I had vaguely thought along those lines but reverse verifying the
info(after merge) mostly won’t work for me.
======================================================================================
This is strictly speaking off topic & I’ve been avoiding and dancing around
this but I’ll have to explain.
I cannot work backwards, at least not efficiently. I cannot continually
import/merge info then check if its correct, my brain will not do it over and
over again. I can happily go back checking and correcting data every now and
then as I find new info. But I have thousands of records to do right now and
the merge/import is (for me) working backward. For repetitive work, I must
build forward, find data, verify it and enter it. It gets weirder:
I am totally unable to open a sealed letter most of the time. Offer me a
million dollars to do it and I won’t. But once in a while I just do it, no
probs! I will happily present to an audience of hundreds but cannot, for a
million dollars, enter a strangers house, at least most of the time. There are
a couple of other strange little quirks too. But as long as my wife and kids
open the mail, I live a 99.9% normal life.
Its a fact of life for me. I cannot rationalize it, nor can my neurosurgical
team but it has been seen before.
After having several tumours removed from my brain & inside my brain stem, I
was left with almost total paralysis/quadriplegia plus some. Years of rehab &
gut busting has me now able to use nearly all my body and even walk reasonably
with a stick, but in the process of the brain retraining itself and
finding/developing new pathways and nerve functions, it developed a few quirks.
There are some things I cannot do, just weird little things like not opening a
letter, my brain sees it as an act of torturous horror & generates scale 10
pain. I can read it if you open it but I cannot open it, I start to break down.
My ability to research and learn is also limited to certain operating &
learning styles.
This is not a whinge, I'm supremely happy with where I'm at. My intellect is
intact but I have to deal with a half dozen strange quirks. Please no “sorry”
replies because I put that behind me long ago.
My issues aside, I can think of several scenarios where researchers might want
to have one file open while working another, manual data comparison for
example. So....I search :)
Please keep any constructive thoughts coming though, I will find a way around
this. What is frustrating is that MS Access (legacy’s heart) can easily run two
databases simultaneously and run multiple copies of access at once, not sure
why the legacy team have chosen to lock it out but I’m sure they have their
reasons.
Just as a footnote to this, I have an old xp desktop pc in the garage
somewhere, worst comes to worst I could replace the dead processor and heat
sink and run legacy on separate pc’s. Its just that it will take up so much
more desk space than my laptop & its dual monitors.
Cheers
Ian G
From: familytree [mailto:[email protected]]
Sent: Monday, 25 June 2012 8:54 PM
To: [email protected]
Subject: RE: [LegacyUG] Legacy split screen view on 2 monitors
It sounds to me as though you still need to think in terms of creating
temporary working databases...leaving both your original database and the new
one as your reference and intact. Once that's done create the new database. Tag
and Export the records whose notes/sources you want changed from your master
file into the new data base ...only do a few as a practise if deep breathing is
a problem. Then go to your new untouched data base file and do the
same....REMEMBER BOTH those files still have original, untouched info...if you
screw up you can go back and access the original information again...once info
from both of the new data files are in the same file...then go ahead and
play....remember, you still have both files with the original info Combine your
sources, add notes...make your working database as pretty and functional as you
can...and when you are done....go back to your original master file, create a
second new database file and do another export...then go to your prettied data
base and do the same....this time, do a merge. You should wind up with:
Your original database file.
A new database file will the info you want added
A working database file that contains info from both files you want combined
but not perfected
And the perfected, merged file...that becomes your new master file
When it comes to originally selecting folks for the first export, only choose
the events that you want....deselect as much as makes sense because
remember...when you do the FINAL merge.that's when you would be allowing the
new and improved database with the corrected sources etc to be combined with
your original info. It may sound complex but it does preserve your info at
every step of the way
-------Original Message-------
From: Ian GARDENER
Date: 6/25/2012 1:05:16 AM
To: [email protected]
Subject: RE: [LegacyUG] Legacy split screen view on 2 monitors
Thank you for your input but it fails to address the issue, it does not achieve
the required result. Copy and paste never came into it, at least not from me.
I DO NOT WANT TO/CANNOT IMPORT PEOPLE FOR REASONS OF MY OWN, I am dealing with
events only and perhaps sources, thousands & thousands of them and import/merge
is NOT an option as stated in my opening question. The simplest thing would be
if I could keep events open in one screen while working on someone in the other
screen, so I can transcribe & check as I go. Legacy does not allow this however
access database (legacy's engine) does, so I'm trying to find a way to make it
work in legacy too. Simple as that.
Being able to template events across different databases would be good (albeit
problematic under windows) as would running simultaneous versions of legacy but
none of these work in legacy windows, although all can be done in varying
degrees, in the access engine that is Legacy's heart.
I've tried it on a unix machine and all can be done there easily using
emulators too BUT my laptop does not run unix. I could do screen captures and
keep that open in one screen but it will nearly triple the time involved.
At this point the most helpful ideas are finding another program that can read
legacy files directly, accurately & completely so i can open that in one
screen/monitor while working legacy on the other, building a legacy compatible
reader (groan), accessing the legacy database tables directly (double groan) or
finding a way to shell legacy to run a second copy without installing a new
operating system. The last is looking as the most promising right now.
Regards
Ian
BTW Like your site by the way.
-----Original Message-----
From: JLB [mailto:[email protected]]
Sent: Monday, 25 June 2012 1:56 PM
To: [email protected]
Subject: Re: [LegacyUG] Legacy split screen view on 2 monitors
Ok, I've read it (for the fourth time) - Stop trying to copy and paste.
Go to Family View on both screens. Drag and drop 'John Smith' on the right to
'John Smith' on the left.
Proceed through the screens:
Just The Individual Above, and anything else on the screen you're interested in.
Click Start Copy
Do what you want on next screens til you get to Merge.
Then keep all information on the left, as you want it, go to the Events tab and
send the Events on the right to the left side.
---
JL Beeken
JLog - simple computer technology for genealogists http://www.jgen.ws/jlog/
On 6/24/2012 8:37 PM, JLB wrote:
> If I could find you in the thread I would. I only see your name in it
> once and I could swear you've been talking on this subject practically
> forever. If you'd like some help, kindly humour me and tell me your
> problem.
>
> JL Beeken
> JLog - simple computer technology for genealogists
> http://www.jgen.ws/jlog/
>
> On 6/24/2012 8:29 PM, Ian GARDENER wrote:
>> Several things, please read the thread.
>>
>> cheers
>>
>> -----Original Message-----
>> From: JLB [mailto:[email protected]]
>> Sent: Monday, 25 June 2012 1:28 PM
>> To: [email protected]
>> Subject: Re: [LegacyUG] Legacy split screen view on 2 monitors
>>
>> I don't know what you mean about database locking. As I understand it you're
>> trying to get Events from one family file into another. What's stopping you?
>>
>> JL Beeken
>> JLog - simple computer technology for genealogists
>> http://www.jgen.ws/jlog/
>>
>> On 6/24/2012 8:18 PM, Ian GARDENER wrote:
>>> I've explained it several times. Are you saying you can get around database
>>> locking?
>>>
>>> Cheers
>>>
>>> Ian
>>>
>>> -----Original Message-----
>>> From: JLB [mailto:[email protected]]
>>> Sent: Monday, 25 June 2012 12:39 PM
>>> To: [email protected]
>>> Subject: Re: [LegacyUG] Legacy split screen view on 2 monitors
>>>
>>> I run two Legacy files in split-screen and I don't understand your problem.
>>>
>>> JL Beeken
>>> JLog - simple computer technology for genealogists
>>> http://www.jgen.ws/jlog/
>>>
>>> On 6/24/2012 7:14 PM, Ian GARDENER wrote:
>>>> No I’ve made it clear a few
>>>> times that the issue is running different legacy files in each screen.
>>>>
>>>> Cheers
>>>>
>>>> Ian
>>>>
>>>> *From:*Ron Ferguson [mailto:[email protected]]
>>>> *Sent:* Monday, 25 June 2012 9:57 AM
>>>> *To:* [email protected]
>>>> *Subject:* Re: [LegacyUG] Legacy split screen view on 2 monitors
>>>>
>>>> Ian,
>>>>
>>>> I think we must be talking at cross purposes here, I was under the
>>>> impression that you wanted the same DB opened twice. Using the
>>>> split screen you can copy/paste across. You can only do it one field at a
>>>> time.
>>>>
>>>> Ron Ferguson
>>>>
>>>> http://www.fergys.co.uk/
>>>>
>>>> *From:*Ian GARDENER<mailto:[email protected]>
>>>>
>>>> *Sent:*Monday, June 25, 2012 12:22 AM
>>>>
>>>> *To:*[email protected]
>>>> <mailto:[email protected]>
>>>>
>>>> *Subject:*RE: [LegacyUG] Legacy split screen view on 2 monitors
>>>>
>>>> Hi,
>>>>
>>>> Agreed.
>>>>
>>>> However I can run 2 instances of ms access simultaneously with
>>>> different databases/files no worries at all,
>>>> it’s a classic use of db. This is
>>>> blocked in the Legacy front end.
>>>>
>>>> Cheers
>>>>
>>>> Ian
>>>>
>>>> *From:*Ron Ferguson [mailto:[email protected]]
>>>> *Sent:* Sunday, 24 June 2012 10:06 PM
>>>> *To:* [email protected]
>>>> <mailto:[email protected]>
>>>> *Subject:* Re: [LegacyUG] Legacy split screen view on 2 monitors
>>>>
>>>> Ian,
>>>>
>>>> Legacy does not use the windows clipboard, but its own, which is
>>>> why you can only copy/paste into the same database.
>>>>
>>>> Yes Legacy is Access based.
>>>>
>>>> Actually in this respect, it does not matter that Legacy is Access
>>>> based as the restrictions are the same for all well constructed databases.
>>>> They are there to stop the users corrupting their own files, and
>>>> should be welcomed.
>>>>
>>>> Ron Ferguson
>>>>
>>>> http://www.fergys.co.uk/
>>>>
>>>> *From:*Ian GARDENER<mailto:[email protected]>
>>>>
>>>> *Sent:*Sunday, June 24, 2012 12:34 PM
>>>>
>>>> *To:*[email protected]
>>>> <mailto:[email protected]>
>>>>
>>>> *Subject:*RE: [LegacyUG] Legacy split screen view on 2 monitors
>>>>
>>>> Hi,
>>>>
>>>> No matter what i do, I cannot cut and paste from one file to another.
>>>> I can copy/paste within the same file but not using two different files.
>>>
>>>> Specifically:
>>>>
>>>> On the let screen/split I have myself open in the new database, on
>>>> the right screen I have myself open in the old database.
>>>>
>>>> In the right screen I open up details, open an event, then copy it
>>>> to the clipboard. I then close that screen (have to to proceed),
>>>> click on the left database and the clipboard in now empty. It
>>>> doesn’t matter wether I save
>>>> or cancel in the old database, the result applies,
>>>> “THE EVENT CLIPBOARD IS
>>>> EMPTYâ€ÂÂÂ.
>>>>
>>>> So I set up two new databases in split screen and tried the same
>>>> thing, same result. The clipboard does not hold data once I click
>>>> on the different file in the other screen. Someone mentioned access
>>>> (is Legacy accessdb based?). So in access database I tried
>>>> essentially the same thing and same result.
>>>>
>>>> Ian G
>>>>
>>>> *From:*Carl Cox [mailto:[email protected]]
>>>> *Sent:* Sunday, 24 June 2012 10:36 AM
>>>> *To:* [email protected]
>>>> <mailto:[email protected]>
>>>> *Subject:* RE: [LegacyUG] Legacy split screen view on 2 monitors
>>>>
>>>> <<This works if both splits are open to the same file (regardless
>>>> of
>>>> individual) but I cannot get it to work when each split is open to
>>>> a different file L
>>>>
>>>> Ian>>
>>>>
>>>> We must be talking past each other, because I often use this method
>>>> within a single file and between different files in a split screen.
>>>> The only requirement is that you "save" the individual information
>>>> as it currently is, regardless of when it was entered. That saved
>>>> information becomes a template from which you can use any piece of
>>>> information you wish, in any database. I don't know if Legacy
>>>> remembers the last one saved when it is closed - it very well could.
>>>> I have 2 files that I record current happenings in, identically in
>>>> both, and I call up split screen, enter the personal information in
>>>> one database, save it, then go to the other database and copy each
>>>> newly entered information by clicking on the field name. Is that how you
>>>> are trying to use this method?
>>>>
>>>> Carl
>>>>
>>>>
>>>>
>>>>
>>>> Legacy User Group guidelines:
>>>> http://www.LegacyFamilyTree.com/Etiquette.asp
>>>> Archived messages after Nov. 21 2009:
>>>> http://www.mail-archive.com/[email protected]/
>>>> Archived messages from old mail server - before Nov. 21 2009:
>>>> http://www.mail-archive.com/[email protected]/
>>>> Online technical support: http://www.LegacyFamilyTree.com/Help.asp
>>>> 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
>>>>
>>>> No virus found in this message.
>>>> Checked by AVG - www.avg.com<http://www.avg.com>
>>>> Version: 2012.0.2178 / Virus Database: 2437/5091 - Release Date:
>>>> 06/24/12
>>>>
>>>>
>>>>
>>>> Legacy User Group guidelines:
>>>> http://www.LegacyFamilyTree.com/Etiquette.asp
>>>> Archived messages after Nov. 21 2009:
>>>> http://www.mail-archive.com/[email protected]/
>>>> Archived messages from old mail server - before Nov. 21 2009:
>>>> http://www.mail-archive.com/[email protected]/
>>>> Online technical support: http://www.LegacyFamilyTree.com/Help.asp
>>>> 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/[email protected]/
>>> Archived messages from old mail server - before Nov. 21 2009:
>>> http://www.mail-archive.com/[email protected]/
>>> Online technical support: http://www.LegacyFamilyTree.com/Help.asp
>>> 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/[email protected]/
>>> Archived messages from old mail server - before Nov. 21 2009:
>>> http://www.mail-archive.com/[email protected]/
>>> Online technical support: http://www.LegacyFamilyTree.com/Help.asp
>>> 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
>>>
>>>
>>>
>>>
>>> -----
>>> No virus found in this message.
>>> Checked by AVG - www.avg.com
>>> Version: 2012.0.2178 / Virus Database: 2437/5091 - Release Date:
>>> 06/24/12
>>>
>>>
>>>
>>
>>
>>
>> Legacy User Group guidelines:
>> http://www.LegacyFamilyTree.com/Etiquette.asp
>> Archived messages after Nov. 21 2009:
>> http://www.mail-archive.com/[email protected]/
>> Archived messages from old mail server - before Nov. 21 2009:
>> http://www.mail-archive.com/[email protected]/
>> Online technical support: http://www.LegacyFamilyTree.com/Help.asp
>> 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/[email protected]/
>> Archived messages from old mail server - before Nov. 21 2009:
>> http://www.mail-archive.com/[email protected]/
>> Online technical support: http://www.LegacyFamilyTree.com/Help.asp
>> 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
>>
>>
>>
>>
>> -----
>> No virus found in this message.
>> Checked by AVG - www.avg.com
>> Version: 2012.0.2178 / Virus Database: 2437/5091 - Release Date:
>> 06/24/12
>>
>>
>>
>
>
>
> Legacy User Group guidelines:
> http://www.LegacyFamilyTree.com/Etiquette.asp
> Archived messages after Nov. 21 2009:
> http://www.mail-archive.com/[email protected]/
> Archived messages from old mail server - before Nov. 21 2009:
> http://www.mail-archive.com/[email protected]/
> Online technical support: http://www.LegacyFamilyTree.com/Help.asp
> 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
>
>
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2012.0.2178 / Virus Database: 2437/5091 - Release Date:
> 06/24/12
>
>
>
Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages after Nov. 21 2009:
http://www.mail-archive.com/[email protected]/
Archived messages from old mail server - before Nov. 21 2009:
http://www.mail-archive.com/[email protected]/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
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/[email protected]/
Archived messages from old mail server - before Nov. 21 2009:
http://www.mail-archive.com/[email protected]/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
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
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2180 / Virus Database: 2437/5091 - Release Date: 06/24/12
Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages after Nov. 21 2009:
http://www.mail-archive.com/[email protected]/
Archived messages from old mail server - before Nov. 21 2009:
http://www.mail-archive.com/[email protected]/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
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/[email protected]/
Archived messages from old mail server - before Nov. 21 2009:
http://www.mail-archive.com/[email protected]/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
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/[email protected]/
Archived messages from old mail server - before Nov. 21 2009:
http://www.mail-archive.com/[email protected]/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
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
