Sorry. I thought you were just trying to get Events (and accompanying sources) from one file to another. I obviously don't understand the complexity of what you're dealing with.
I hope you understand that the fields you can import through Merge are optional. It can be just Events. JL Beeken JLog - simple computer technology for genealogists http://www.jgen.ws/jlog/ On 6/24/2012 10:04 PM, Ian GARDENER wrote: > 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.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
