Ltools has a routine under Run Raw SQL to tag all marriages as follows:
UPDATE tblMR SET tblMR.Tag{TagNumber} = 1
That same script could untag all marriages by changing it to
UPDATE tblMR SET tblMR.Tag{TagNumber} = 0
I added a custom SQL to untag only tagged marriages as follows:
UPDATE tblMR SET tblMR.Tag{TagNumber} = 0 WHERE ((tblMR.IDMR <> 0) AND
(tblMR.Tag{TagNumber} <> 0))
More functionality might be added as required. One routine that I use
frequently is called "Tag Unknown Spouses w/o Children". It helps to find and
tag marriages with spouse RIN = 0 or the blank spouse marriages with no
offspring. These often occur in Legacy when a child is displayed in the parent
position without a spouse and someone clicks on the spouse but then does not
actually add a spouse. That creates an empty marriage record with a blank
spouse. It show most obviously when you have a young child with a marriage
record indicator and you are certain the child never married.
One more script that I use is the following which shows all marriages that have
any of the 9 tags set. I use it to determine if any marriage tags need to be
cleared.
SELECT
tblMR.IDMR,tblMR.Tag1,tblMR.Tag2,tblMR.Tag3,tblMR.Tag4,tblMR.Tag5,tblMR.Tag6,tblMR.Tag7,tblMR.Tag8,tblMR.Tag9
FROM tblMR WHERE ((tblMR.IDMR <> 0) AND ((tblMR.Tag1 <> 0) OR (tblMR.Tag2 <>
0) OR (tblMR.Tag3 <> 0) OR (tblMR.Tag4 <> 0) OR (tblMR.Tag5 <> 0) OR
(tblMR.Tag6 <> 0) OR (tblMR.Tag7 <> 0) OR (tblMR.Tag8 <> 0) OR (tblMR.Tag9 <>
0))) ORDER BY tblMR.IDMR
Hope this give you some ideas about marriage record tagging. Of course the SQL
scripts could be used in MS Access as well.
Ron Taylor
On Saturday, October 26, 2013 3:31 PM, Laura Johnson
<rngad...@madisontelco.com> wrote:
I would gladly use LTools IF it was able to do this. But all of the
features listed on both the regular and deluxe versions do not mention
anything about tagging marriages. If Dennis can confirm that it will do
this, I would gladly purchase it just to save me the time
On 10/26/2013 1:56 PM, Howard Cady wrote:
> Laura, if you are slightly able to deal with databases and their
> structures, then I would suggest considering the Legacy add-on "LTOOLS" for
> major clean-up, and special tagging (marriages can have up to three tags).
> Dennis Kowallek, the LTOOLS programmer, has helped others with similar
> problems. It may be possible to fix all FTM to Legacy conversions that have
> been messed up by the standard export-import process for all of your 54,000
> individuals and 17,000 marriages by direct manipulation of a copy of the
> Legacy database because you are dealing with only one version of FTM and
> only one version of Legacy. NEVER work on your original family file with
> LTOOLS - only use a copy of your original file.
> Howard Cady
>
> ----- Original Message -----
> From: "Laura Johnson" <rngad...@madisontelco.com>
> To: <LegacyUserGroup@LegacyUsers.com>
> Sent: Saturday, October 26, 2013 7:52 AM
> Subject: Re: [LegacyUG] Tagging Marriages
>
>
> This would have been a great idea EXCEPT that once you get the list, you
> are NOT getting the marriages to tag. You still get a list of
> individuals to tag. I already have tagged all individuals in the
> database and have been working my way through cleaning those up.
>
> There are 54,833 individuals and 17090 marriages. The results of the
> trial run for this created a list of 52,601. But if you look at the
> list, I would be re-tagging several thousand people that I had already
> cleared the tag on as my search list for the tag I was doing shows that
> I still have 49,654 still to go from my original tagging.
>
> First, let me tell you what I have been doing. I have been entering all
> of the births, marriages and deaths from 1820 through 1910 from the
> microfilmed records from a town in Sicily. I also have an online
> database for this town as well that is fully searchable. I had been a
> loyal user of FTM from the early 1990's and had beta tested for them for
> years. After beta testing their 2008 and 2009 versions, it was evident
> that Ver 16 was going to be the last version I would use due to the
> changes they had made to the program. The newer versions cannot handle
> my file and scramble the details on sources when they are imported via
> gedcom from Ver 16 to FTM 2008, etc.
>
> I switched to Legacy on the advise of a friend who had been using it for
> years. It was far superior to what FTM had in any version that I had
> used. So I bought the deluxe version and have been using it ever since.
>
> But in bringing my files over to Legacy, I noticed that I needed to do
> cleanup on the way I had been doing things before I started using Legacy
> and even after I first started using Legacy because I found other
> options or ways of doing things that were far superior in Legacy and I
> need to cleanup and redo things that were not done that way in the past.
>
> About a year ago, I tagged all individuals in the database with Tag #5.
> The description for this tag is: FTM Cleanup Needed. I also have tag 2
> and tag 3. These tags designate my paternal great-grandfather's family
> (#2) and my maternal great-grandmother's family (#3). This way I can
> easily see if a person is included in my ancestral lines or is just
> someone from the town.
>
> I have been working my way through the tag #5 as I enter more data in
> the file and cleaning them up as I go. But it would be easier if I
> could see that the marriage tag was cleared because then I would know
> that I had already changed or fixed any problems with the children and
> descendants of that line. I wouldn't need to choose each of the
> children one by one to confirm whether they were done or not.
>
> My thoughts were originally to use the marriage list to tag so that I
> could work through all of the marriage list. I would select the first
> marriage on the search list, correct both the wife and husband and any
> children they had and remove the tag numbers for both the marriages and
> the individuals as I went for that marriage. Then once I had worked
> through all of the marriages, I could then do a final search to find any
> unlinked individuals
>
>
>
>
>
> Legacy User Group guidelines:
> http://www.LegacyFamilyTree.com/Etiquette.asp
> Archived messages after Nov. 21 2009:
> http://www.mail-archive.com/legacyusergroup@legacyusers.com/
> Archived messages from old mail server - before Nov. 21 2009:
> http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
> 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/legacyusergroup@legacyusers.com/
Archived messages from old mail server - before Nov. 21 2009:
http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
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/legacyusergroup@legacyusers.com/
Archived messages from old mail server - before Nov. 21 2009:
http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
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
