Adding a new value for this flag (N = Pseudo person) seemed like a good idea.  When I first attempted to edit the flag, the heading was 'Edit Standard Flag Value' and all boxes were inaccessible (greyed out).  But the next time I tried, it opened up with heading 'Edit Flag Value' and I was able to add 'N = Pseudo person' in the Description box.  I thought I also added N in the Values box, but it does not now appear. Now I've realised that, being a standard flag, Sex cannot be edited -- so I believe!  All my recent attempts to edit the flag result in the greyed out version of the Edit dialog box. Questions: 1. am I right in thinking that standard flags cannot be edited? 2. if yes, how come I managed, on one occasion, to edit the Sex flag descriptions? 3. if I cannot edit the flag, how do I remove the description that I added? Lindsay Graham Canberra, Australia

I think I may have made two mistakes at once. For a relative in my database I entered without thinking the DoB I found in the UK 1939 Registry: 29 Feb 1975 - which cannot be correct. So I have set to work to change it. I assume 01 Mar would be close for the time being, The Picklist and the Name field are the same, "J. F... T... (123) (<?>- )". The Birth field is OK, though with that impossible date. But I cannot get rid of that (<?>- ). I don't know where it came from, or how I can delete it. Glad of any help, please. Bruce Dodd Ottawa

<Sorry, no, that was misleading. The ID#s remain the same.< That was what I thought too!!. Very good to know. <So, instead of say 874000 people in the project, you now have say <871000 people? That seems to be a step in the right direction toward your <goal. Yes ,but so far ,I have only tried it out in the TEST project ,not in the Kladd project that I am going to do it in..... (It doesn`t do any harm if I should do any wrong in that TEST project!).

At 2/18/2019 18:04, Erik Hov wrote >How does this add up? Does this mean that by creating a new project from the >List of People-Create new project the new project gets new Idnumbers?? Sorry, no, that was misleading. The ID#s remain the same. ><The problem with moving persons to a different data set is that you are >still in the same project and still subject <to the 2GB limit. However, >this may or may not be an issue if you periodically run the Maintenance >routibe <especially the Optionze routine.< > >That was how I did the deleting of people when doing my first split. I did >optimize all the time after deleting about 3000 people at a time. I have to >do the same now ,optimizing al the time. So, instead of say 874000 people in the project, you now have say 871000 people? That seems to be a step in the right direction toward your goal. Lee

<Regardless of the Flag Setting, if a person connected to someone of the opposite setting is copies to a new project <then the connection is lost. Correct ,I found out when I tried to move people in the TEST project. By having to set flags manually because of the size ,I have also been able to set flags to the right people ,so that I can be quite confident that the AAS=N people are the ones that I shall keep plus also run several reports to find people I might have missed. <No, only the moved person(s) are moved. A moved son will lose his father unless the father is also moved.< That was what the move person feaure in the TEST project showed me. I selected 5 people ,and it was only 5 who was moved. I am now trying a larger groupt just to see how it seems... <For example, you have a project with ten people numbered #1 through #10. You create a new project based on <a Flag set to Y for the even numbered persons (the even numbered people are copied to the new project, The <new project will have the following: <Name Old# New# < A 2 1 < B 4 2 < C 6 3 < D 8 4 < E 10 5 How does this add up? Does this mean that by creating a new project from the List of People-Create new project ,the new project gets new Idnumbers?? <The problem with moving persons to a different data set is that you are still in the same project and still subject <to the 2GB limit. However, this may or may not be an issue if you periodically run the Maintenance routibe <especially the Optionze routine.< That was how I did the deleting of people when doing my first split. I did optimize all the time after deleting about 3000 people at a time. I have to do the same now ,optimizing al the time. I am very aware of the 2 GB limit ,and I should have split my project a long time ago. Playing around with the TEST project now to find out about things. <I assume that the TEST project is a copy of your original project. As I noted beforre, being so close to the 2GB limit of FoxPro can have a large impact on this.< Yes ,it is a copy of my original project. After moving about 2500 people from the TEST project to the other dataset within the project ,I deleted the dataset and I have just now started optimizing. It now has about 119800 AAS=Y people.

At 2/18/2019 15:46, Erik Hov wrote >>Note that if you attempt to delete a person with direct connections then >>TMG will notify you that there are <certain connection and dis-allow the >>deletion. Then, if you still want to delete that person, you will need to >><remove that connection (Tag) first. Then, try again. > >Yes ,but this is if you use the delete person feature on the edit menu >,right? ,and not the move people feature?. Or is it both? Yes, the warning is only when using the Edit=>Delete Person(s) feature. >>Finding persons with direct connection is fairly easy. No Relatioship Tags >>to parent, and no Marriage Group Tags will find the great majority. Other >>connections are less easy to identify via a filter. A thorough knowledge of >>the project will suggeswt other poaaible connections and ways to filter for >>them. Still other may need to be individually reviewed. > >I haven`t disconnected any of the AAS=Y to the AAS=N people. I marked the >AAS flags with Y when going through them manually ,and also set a lot of the >flag values back to N when going through them again to find out which people >I will keep in the project. Regardless of the Flag Setting, if a person connected to someone of the opposite setting is copies to a new project then the connection is lost. ><You have, so far, deci8ed that 121000 persons are not longer needed in your >project, The only way to remove them (other than one at a time) is via the >List of People=>Secondary Output=>Create New Project option. In this >method, there may be connections lost since the connected persons are not >copied to the new project. In my experience, those not copied would not be >that many.< > >Now ,I am confused on two things. >First I don't know if the move people feature actually also moves the parent >of the selected people to be deleted. No, only the moved person(s) are moved. A moved son will lose his father unless the father is also moved. >Second ,I thought you just said that the List of People.....create new >project option doesn`t delete any people? And then you say above that "The >only way to remove them (other than one at a time) is via the List of >People=>Secondary Output=>Create New Project option."....... No, the List of People=>Create new project does not delete anyone in the _original_ project. Only the persons copied to the new project will be in the new project -- effectively makeing the people from the old project that are NOT moved to appear as having been deleted from the new project when compared with the old project. For example, you have a project with ten people numbered #1 through #10. You create a new project based on a Flag set to Y for the even numbered persons (the even numbered people are copied to the new project, The new project will have the following: Name Old# New# A 2 1 B 4 2 C 6 3 D 8 4 E 10 5 >I did create a new project project from the main project and called it >"TEST" it has all of the AAS=Y and AAS=N people in it. I created a dataset >within that project and I am now trying the move people feature. When making >the new dataset I chose to have all the places and other features in the new >dataset as well. Then I tried to move one person to the other dataset to see >how it went. So far TMG seems to be at a standstill at 27% on the >placenamefile ,and being there for soon 10 minutes. I will try to create a >dataset without including any datatypes and see if that is any clue.... The problem with moving persons to a different data set is that you are still in the same project and still subject to the 2GB limit. However, this may or may not be an issue if you periodically run the Maintenance routibe especially the Optionze routine. Note that when a person(s) is/are moved to another data set (say from data set 1 to data set 2), while that effective removes (deletes) the person(s)from the original data set (#1), the physical deletion from data set @1 does not take place until the projecty is Optimized. Thus the project files will increase in size until the project is Optimized. So, starting with a project that has a size of 4096318 bytes and moving say ten persons, you will have a project size of say 4098525 bytes. If you then Optimize, the size of the project will again be 4096318 bytes (or within a few bytes of that as there may be some adminstrative data that is involved that hasn;t been taken into account. And at 2/18/2019 15:46, Erik Hov wrote > made a test with the TEST project moving people to another dataset within >the project. I tried on 5 people at first ,and after some time it worked. >I got them over in the other dataset ,but after deactivating the main TEST >dataset and just having up the other dataset ,it took a very long time >waiting for example the F2 picklist to appear. >Of those 5 people ,I had parents on 4 of them (and those parents wasn`t >moved). Only the 5 I chose to be moved was moved ,no one else...... I assume that the TEST project is a copy of your original project. As I noted beforre, being so close to the 2GB limit of FoxPro can have a large impact on this. That would be what I noted, that only the five people are moved. Keep in miond here what I said above that "moved persons" from data set #1 remain in data set #1 as well as being copied to data set #2 UNTIL you Optinmize the project. That is, the persons that were moved are MARKED as deleted and thus can't be seen anymore in TMG but are still in the files. Optimize actually removes records that are MARKED as deleted. Lee

I made a test with the TEST project moving people to another dataset within the project. I tried on 5 people at first ,and after some time it worked. I got them over in the other dataset ,but after deactivating the main TEST dataset and just having up the other dataset ,it took a very long time waiting for example the F2 picklist to appear. Of those 5 people ,I had parents on 4 of them (and those parents wasn`t moved). Only the 5 I chose to be moved was moved ,no one else......

<If your project is like mine, most people are connected in some way with the rest of the project. That connection <may be direct in the sense of parent/child through multiple generations including cousins and aunts/uncles. Or <the connection may be by marriage. The third type os connection is as a Witness - minister/best man.maid of <honor at a wedding, a business associate, or any other event in which multiple people are involved. Thus, trying <to identify persons that have no connection with others in the project is almost like hunting for the proverbial <needle.< Most of the connections are of the two first types. I don`t really know if I have any people entered as witnesses etc ,at least I haven`t entered any such witnesses as I can recall. In many cases, you almost need to review each candidate individually for removal from the project. If you are lucky, that person will have no connection and can easily be deleted or marked for deleted (Flag set). For many others, there will be a connection. In such cases, you need to decide whether they will be deleted/marked for deletion and, if so, the best option would then be to remove the connection first. This would then resolve any potential problem that might occur during the deletion. <Note that if you attempt to delete a person with direct connections then TMG will notify you that there are <certain connection and dis-allow the deletion. Then, if you still want to delete that person, you will need to <remove that connection (Tag) first. Then, try again.< Yes ,but this is if you use the delete person feature on the edit menu ,right? ,and not the move people feature?. Or is it both? <Finding persons with direct connection is fairly easy. No Relatioship Tags to parent, and no Marriage Group Tags <will find the great majority. Other connections are less easy to identify via a filter. A thorough knowledge of the <project will suggeswt other poaaible connections and ways to filter for them. Still other may need to be <individually reviewed.< I haven`t disconnected any of the AAS=Y to the AAS=N people. I marked the AAS flags with Y when going through them manually ,and also set a lot of the flag values back to N when going through them again to find out which people I will keep in the project. <You have, so far, deci8ed that 121000 persons are not longer needed in your project, The only way to remove <them (other than one at a time) is via the List of People=>Secondary Output=>Create New Project option. In this <method, there may be connections lost since the connected persons are not copied to the new project. In my <experience, those not copied would not be that many.< Now ,I am confused on two things. First I don't know if the move people feature actually also moves the parent of the selected people to be deleted. Second ,I thought you just said that the List of People.....create new project option doesn`t delete any people? And then you say above that "The only way to remove them (other than one at a time) is via the List of People=>Secondary Output=>Create New Project option."....... <In regard to your problem of getting errors running the List of People report =>Secondary Output option, let me <note what I recall of what you have had happen. < 1. Your main project is at or nearing the 2GB limit imposed by FoxPro (the underlying program that TMG uses). < 2. You have created one or more new projects from that "old" project, with the new project containing a <relatively small number each (three/four thousand people). There was <no problems doing this. < 3. You have tried creating a new project by copying the old project minus the 121000 people that you no longer <want in the project. This has failed. <Since #2 above worked bu #3 did not, it suggests to me that you are running up again the 2GB limit in #3. In such <a case, it appears to me that you will not be able to create a new project via the #3 method. Correct on all three!. At least I know that I can`t create any project of the 875000 I am going to keep. I am fully able to copy whole projects (File-Copy project) ,but not parts of projects on the List of People report. <This only other option (in my opinion) is the safest and best. But this is like saying that a dentist drilling on your <teeth without ansthesia is easily withstood. As I see it, your only real option is to individually delete each of the <121000 persons. As I said before, at some point in this process, the project (following Optomization) will be small <enough that you can continue the rest using the List of People report method.< I tend to agree with you that that is the safest way to be completely sure that nothing will be changed unless I know it. I did create a new project project from the main project and called it "TEST" it has all of the AAS=Y and AAS=N people in it. I created a dataset within that project and I am now trying the move people feature. When making the new dataset I chose to have all the places and other features in the new dataset as well. Then I tried to move one person to the other dataset to see how it went. So far TMG seems to be at a standstill at 27% on the placenamefile ,and being there for soon 10 minutes. I will try to create a dataset without including any datatypes and see if that is any clue.... _______________________________________________ Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/tmg@rootsweb.com Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community

At 2/18/2019 06:47, Erik Hov wrote >After doing that ,I am left with those beforementioned 121000 people that >doesn`t need to be in the main project. I guess most of these 121000 are >involved in more than one event on the ones I shall keep ,but since they are >only descended from or married to AAS=Y people/relatives ,I don`t need them >to be in the project anymore. If anything should go wrong. I have a backup >of the project ,and also have all of it in another project with a different >name in case the backup shouldn`t work. If your project is like mine, most people are connected in some way with the rest of the project. That connection may be direct in the sense of parent/child through multiple generations including cousins and aunts/uncles. Or the connection may be by marriage. The third type os connection is as a Witness - minister/best man.maid of honor at a wedding, a business associate, or any other event in which multiple people are involved. Thus, trying to identify persons that have no connection with others in the project is almost like hunting for the proverbial needle. In many cases, you almost need to review each candidate individually for removal from the project. If you are lucky, that person will have no connection and can easily be deleted or marked for deleted (Flag set). For many others, there will be a connection. In such cases, you need to decide whether they will be deleted/marked for deletion and, if so, the best option would then be to remove the connection first. This would then resolve any potential problem that might occur during the deletion. Note that if you attempt to delete a person with direct connections then TMG will notify you that there are certain connection and dis-allow the deletion. Then, if you still want to delete that person, you will need to remove that connection (Tag) first. Then, try again. During the creation of a new project via the Secondary Output of the List of People report, there is no such warning since you aren't really deleting anyone from the original project, but copying the persons to be retained to the new project. Finding persons with direct connection is fairly easy. No Relatioship Tags to parent, and no Marriage Group Tags will find the great majority. Other connections are less easy to identify via a filter. A thorough knowledge of the project will suggeswt other poaaible connections and ways to filter for them. Still other may need to be individually reviewed. You have, so far, deci8ed that 121000 persons are not longer needed in your project, The only way to remove them (other than one at a time) is via the List of People=>Secondary Output=>Create New Project option. In this method, there may be connections lost since the connected persons are not copied to the new project. In my experience, those not copied would not be that many. My guess would be that those mpt copied would not be more than a few hundred. In your case, it might be somewhat larger -- approaching a thousand. Many of these can be identified quickly and easily added to the new project. Still others might not be noticed for a long time. In regard to your problem of getting errors running the List of People report =>Secondary Output option, let me note what I recall of what you have had happen. 1. Your main project is at or nearing the 2GB limit imposed by FoxPro (the underlying program that TMG uses). 2. You have created one or more new projects from that "old" project, with the new project containing a relatively small number each (three/four thousand people). There was no problems doing this. 3. You have tried creating a new project by copying the old project minus the 121000 people that you no longer want in the project. This has failed. Since #2 above worked bu #3 did not, it suggests to me that you are running up again the 2GB limit in #3. In such a case, it appears to me that you will not be able to create a new project via the #3 method. Thus, you are limited in how you can reduce the size of your project to well below the 2GB limit. There is the possibility of someone very knowledgeable of the TMG file structure working with each project file (there are about fifty excluding the index files) and deleting the desired records. The problem with this method is that even a very knowledgeable person may miss deleting certain record or that too many records are deleted. The inter-relationship of the fifty files makes such work very hard. If everything gos as planned, it would work, but the odds are that something will go wrong. The only loss would be of the person's time as you would still have your original project. Note that the person doing the work here would have to know exactly who to delete and the work would probably be more extensive than the only other option. This only other option (in my opinion) is the safest and best. But this is like saying that a dentist drilling on your teeth without ansthesia is easily withstood. As I see it, your only real option is to individually delete each of the 121000 persons. As I said before, at some point in this process, the project (following Optomization) will be small enough that you can continue the rest using the List of People report method. This is not a happy solution, but I think it is what you will have to do. Lee

<As you have learnt there are a lot of questions about what should be kept for a person when you delete other persons. This is not an easy aspect to manage.< I have worked on this setting of flags in thinking that those I am setting flags to are those who will be deleted. I am pretty sure I have not forgotten anyone. I didn`t know that possibly ALSO the parent of any selected person will be deleted when using the move feature.....(will try later today). <A similar problem occurs when importing data, what is redundant and what is in conflict? Who judges that persons are the same?< When doing an import (at least a gedcom which I haven`t done for many years) you don`t get much choice of determining if persons are the same. Not with the import genBridge into TMG either. Guess you have to look for doublegangers within the TMG for that. <Designing software tools to make this process easier is not easy. My first rule would be to keep all persons who <are witnesses to a retention person's Event, even more strongly those persons that are involved more than one <event that involve your prime retention population (1 degree of separation) - but how do you automate that?< Hmmmm.....not sure whow to answer this! Originally I had about 183000 people with the AAS=Y flag that I was able to make a new project of from the List of People report. A Similar list from LoP with 874000 of the AAS=N didn`t work. Anyway ,of those 183000 I set many of the people back to AAS=N ,exactly because they were married to people or had children that was married to people not belonging to the AAS=N people in the project that I wanted to keep. After doing that ,I am left with those beforementioned 121000 people that doesn`t need to be in the main project. I guess most of these 121000 are involved in more than one event on the ones I shall keep ,but since they are only descended from or married to AAS=Y people/relatives ,I don`t need them to be in the project anymore. If anything should go wrong. I have a backup of the project ,and also have all of it in another project with a different name in case the backup shouldn`t work.

As you have learnt there are a lot of questions about what should be kept for a person when you delete other persons. This is not an easy aspect to manage.  A similar problem occurs when importing data, what is redundant and what is in conflict? Who judges that persons are the same? Designing software tools to make this process easier is not easy. My first rule would be to keep all persons who are witnesses to a retention person's Event, even more strongly those persons that are involved more than one event that involve your prime retention population (1 degree of separation) - but how do you automate that? RobinL On 18-Feb-19 02:31 PM, Richard Damon wrote: > On 2/17/19 10:52 PM, Erik Hov wrote: >> Thanks for all help I have gotten with how to delete people from my large >> project!. >> I have not actually tried to move people yet. >> I am a bit concerned if moving a person also removes the person`s >> parent/parents ,so I will try to move two or three people first to see if >> it`s really true that the selected person`s parents also automatically are >> being moved. If that happens ,I must reconsider what to do....even if I >> really don`t see any other option for deleting those 121000 people than >> using the move people feature...... >> Erik >> > The parents shouldn't be removed as people, but the parental > relationship (the relationship tag between them) will be removed. > -- Robin Lamacraft, Adelaide, Australia --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

<The parents shouldn't be removed as people, but the parental relationship (the relationship tag between them) will be removed.< OK ,so if I remove my grandfather ,my grandfather will be moved to the other dataset while my grandfather`s parents will remain in the old dataset but without my grandfather as their child? Lee wrote that "For example, if I select my granfather and all his descendants and move them to another data set, all of them plus my grandfather's parent will be move and my great-great grandparent will be missing a son. So, either you make the "disconnet" before the move or it will be made for you." OK that the greatgrandparents would be missing a son ,but not OK if my grandfather`s parent/s will also move automatically when using the move feature. If I have to disconnect all the relationships to the people with AAS=Y flag before using the move people feature ,that would be quite time consuming. Will try out the move people feature for two or three selcted people for a start to see if their parents really are included in the move......

On 2/17/19 10:52 PM, Erik Hov wrote: > Thanks for all help I have gotten with how to delete people from my large > project!. > I have not actually tried to move people yet. > I am a bit concerned if moving a person also removes the person`s > parent/parents ,so I will try to move two or three people first to see if > it`s really true that the selected person`s parents also automatically are > being moved. If that happens ,I must reconsider what to do....even if I > really don`t see any other option for deleting those 121000 people than > using the move people feature...... > Erik > The parents shouldn't be removed as people, but the parental relationship (the relationship tag between them) will be removed. -- Richard Damon

Thanks for all help I have gotten with how to delete people from my large project!. I have not actually tried to move people yet. I am a bit concerned if moving a person also removes the person`s parent/parents ,so I will try to move two or three people first to see if it`s really true that the selected person`s parents also automatically are being moved. If that happens ,I must reconsider what to do....even if I really don`t see any other option for deleting those 121000 people than using the move people feature...... Erik

Thanks for all the ideas.  I tried several of them, some I did not like, some did not give me the information I wanted.  I settled on a list of sources with columns of: Source #, Abbreviation, Subject - sorted by Abbreviation.  I have 511 sources for CA,   The obits leave an empty subject column and that seems to where many of the duplicates are. I can check them manually. This list is a godsend to get ideas of how to proceed next.Nancy

I took a lesson from a past/former/silent member who said she sorted her sources by the two letter postal abbreviation, then a description of the source.  Example: CA, 1910 Cen Lowrie, George P. Sr.I just merged two of those. Three Letters are used for other countries and there are several others where a place does not apply. I think it might be just as easy to go through the Master Source List as print out a list to go through. Today I have found 4 to be merged - but am working in California which probably has the most, maybe Connecticut will not be too far behind California.  These duplicates come from merging two data sets. I knew there were people who would be duplicates and took care of merging them but I forgot about the sources.  They are just beginning to plaque me now. Nancy On Sunday, February 17, 2019, 11:58:59 AM CST, Terry Reigel <terry@reigelridge.com> wrote: On 2/17/2019 12:09 PM, Nancy W. wrote: > I see in the Endnotes section of my journal report I have several duplicate sources.  I have merged some by going through the Master list of sources but there are still many more.  Is there a report I can print to help find these duplicate sources?  I have almost 3000 sources.  I am a splitter as opposed to a lumper. Nancy, What is it about a pair of Sourced that makes them duplicates? What specific element(s) in the Source Definition have to match to identify a duplicate? Knowing that we can suggest a report to find them. Terry Reigel _______________________________________________ Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/tmg@rootsweb.com Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community

Nancy W. asked: > I see in the Endnotes section of my journal report > I have several duplicate sources... > I have merged some by going through the Master list of sources... > Is there a report I can print to help find these duplicate sources? The quick answer is no. I know of no report which will only output source definitions which are duplicated. As Lee mentioned, there is the TMG List of Sources report. But even that list, appropriately sorted, would have to be visually reviewed to notice that two sources sorted together were duplicates. And as Lee mentioned there are only nine possible output columns, so you would have to be careful which fields you chose to be in the report. However, by sending it to a file, e.g. Word, you could go through the file on screen and delete lines of the report as you reviewed and finished with them. Michael

At 2/17/2019 12:09, Nancy W. wrote >I see in the Endnotes section of my journal >report I have several duplicate sources. I >have merged some by going through the Master >list of sources but there are still many >more. Is there a report I can print to help >find these duplicate sources? I have almost >3000 sources. I am a splitter as opposed to a lumper. As Terry says, we need more information to be able to give you speicifc help. But, there are a couple of things that you might look at. One is the List of Sources report. You would not want to print such a report for 3000 Sources, but you could generate the report to a file (word processor, spreadsheet, Rich Text Format, or even PDF) and review it on screen. There are a number of options for the report that you could select. You can select to have a columnar report in which case you select which Source Elements are included in the Output Columns. The problem I have with this is deciding shich Source Element to select as not all Sources have the same Source Elements and there is a limit of nine columns. But, depending on what I think I want, I can usually figure something out. You can also select an indented report. This option gives the Source ID# and either the Title or Abbreviation. You may also choose to print the report with the Source ID# and Bibliography. One or all of these indented lists may solve most of your problem or at least narrow down the work. Once you have the work reduced to the "hard to find", the columnar list may help. Another possibility is the List of Citations report. Again, there are a number of options available. Finally, there is John Cardinal's TMG Utility. It can generate a Source Page that can be viewed in your browser of your Sources. The page would include the Source #, Abbreviation, and Title. Some Sources here will also display an e-mail address or a URL. The page is sorted by the Source Title. The contents of the page could be copied to a spreadsheet and re-sorted as you wish. The advantage of this over the Lists generated by TMG is that this report include both the Abbreviation and the Title columns. Lee

Nancy, I'm not aware of a report to find duplicate sources. To be "duplicate" two sources would have to have exactly the same content for every source element, memo content and reminder content on the Supplemental tab, linked repositories, exhibits, etc. You could look for candidates by sorting the Master Source List by Title and scanning it (all 3000) then opening any with duplicated titles to see if they are truly duplicates. That said, duplicate endnotes don't necessarily mean duplicate sources. Multiple citations to the same source can produce identical endnotes depending on the use of the CM and CD fields, the Short Title field, as well as the content of the Full Footnote and Short Footnote templates. This can happen with and without the Unique Endnotes option selected. If you think your issue might be duplicate endnotes instead of duplicate sources you may find Michael Hannah's discussion helpful here: https://www.mjh-nm.net/SRCGUIDE.HTML#IbidUnique On 2/17/2019 9:09 AM, Nancy W. wrote: > I see in the Endnotes section of my journal report I have several duplicate sources.  I have merged some by going through the Master list of sources but there are still many more.  Is there a report I can print to help find these duplicate sources?  I have almost 3000 sources.  I am a splitter as opposed to a lumper. > Nancy >

That's correct, Nancy. You can update it as often as you want. > -----Original Message----- > From: Nancy W. <wright4766@bellsouth.net> > Sent: Sunday, February 17, 2019 11:04 AM > To: The Master Genealogist Rootsweb Email List <tmg@rootsweb.com> > Subject: [TMG] Re: Journal report, Index > > Thank you to all of you. I knew there was something more to preparing the > index but I didn't know what that was. And special thanks to Nancy because > after I sent the request for help I realized I have altered the journal report. I > expected to have to prepare the index by hand, but she tells me I can update > it. > > Nancy