Re: [LegacyUG] A question about FAG numbers {user ID]

2024-02-07 Thread Ian Macaulay 
Duplicates within FAG should be reported to FAG and will have no bearing on
the Legacy data.  I mark both numbers in my Lagacy file as well as
reporting the change in FAg.
Also If the Find a grave numbers were unique in Legacy, then you would not
be using Check/repair to find duplicates , you would be notified
immediately upon your entry attempt.

Ian

On Tue, Feb 6, 2024 at 10:27 PM  wrote:

> Ian
>
> I think this would be nice… however even though on Find A Grave each
> memorial IS a unique number …
>
> There are still issues that can’t be corrected by making the field in
> “Legacy” unique
>
>
>
> One being duplicate memorials created within Find A Grave and lastly when
> a memorial gets merged… That way it still has to be fixed in Legacy after
> it is located.
>
> So, in one way the portion of check/repair that locates there error drives
> us (the user) to investigate.
>
>
>
> In my case I find the duplicate numbers I get in Legacy are from me having
> duplicate individuals which I need to merge (here again I find that the
> check/routine that catches these duplicates VERY beneficial.
>
>
>
> So I guess what I am saying is that I can see advantages to both sides of
> the argument.
>
>
>
> Kind Regards
>
> Henry
>
>
>
>
>
> *From:* LegacyUserGroup  *On
> Behalf Of *Ian Macaulay
> *Sent:* Tuesday, February 6, 2024 6:04 PM
> *To:* Legacy User Group 
> *Subject:* Re: [LegacyUG] A question about FAG numbers {user ID]
>
>
>
> This is not the same as the FAG number as the Fag number is a direct link
> to Find a Grave whereas the user ID is connected to naught.
>
>
>
> Ian
>
>
>
> On Tue, Feb 6, 2024 at 1:50 PM Ms Mary K. Lund via LegacyUserGroup <
> legacyusergroup@legacyusers.com> wrote:
>
> To answer the question of "to RIN' or not to "RIN": Copied from Legacy
> file Help
>
>
>
> *User ID*
>
> This field is for any reference number you want to record for this
> individual.  You can use any combination of letters, numbers and
> punctuation marks.  There is a tool on the *Options > Customize > Other *tab
> where you can automatically fill the *User ID* fields for all individuals
> with the RIN numbers and optional text.  (See Customize - Other for more
> information.)
>
> Mary K. Lund
>
>
>
> On Friday, February 2, 2024 at 05:24:08 AM CST, Jenny M Benson <
> ge...@cedarbank.me.uk> wrote:
>
>
>
>
>
> On 02/02/2024 01:12, Ian Macaulay wrote:
> > Do any of you see why Find a grave numbers should not be made a unique
> > field.
> > In order to not allow a duplicate entry.  I have for a second time
> > requested this feature and am hoping that there is not a problem
> > somewhere else that I have not considered.
> >
> > My  program crashes often  and always has a duplicate or two in the
> > error report.
> > It is the only reason I can find for these crashes.  It takes three runs
> > at  File maintenance to get up and running again.
> >
> > If you have an objection to making this field unique please post it/
> > If not and you agree with my poorly stated state of affairs, send a
> > request for feature to Legacy via the  request feature in the "Help/
> > request featurte"  drop down.
>
> Seems a good idea so I have submitted a request.
>
> --
> Jenny M Benson
> Wrexham, UK
>
>
>
>
> --
>
> 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/
>
>
>
> --
>
>   ICMac Sales: Hobby consultant (1986r.)
>
> Office hours:   10:00 Am - 5:00 PM  most days
>
>   Macaulay Genealogy
>  Family Matters
>   Ian Macaulayof Carp, Ontario
> --
>
> 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/
>


-- 
  ICMac Sales: Hobby consultant (1986r.)
Office hours:   10:00 Am - 5:00 PM  most days
  Macaulay Genealogy
 Family Matters
  Ian Macaulayof Carp, Ontario
-- 

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] A question about FAG numbers {user ID]

2024-02-06 Thread hpeterjr47 
Ian

I think this would be nice… however even though on Find A Grave each memorial 
IS a unique number …

There are still issues that can’t be corrected by making the field in “Legacy” 
unique

 

One being duplicate memorials created within Find A Grave and lastly when a 
memorial gets merged… That way it still has to be fixed in Legacy after it is 
located.

So, in one way the portion of check/repair that locates there error drives us 
(the user) to investigate.

 

In my case I find the duplicate numbers I get in Legacy are from me having 
duplicate individuals which I need to merge (here again I find that the 
check/routine that catches these duplicates VERY beneficial.

 

So I guess what I am saying is that I can see advantages to both sides of the 
argument.

 

Kind Regards

Henry

 

 

From: LegacyUserGroup  On Behalf Of 
Ian Macaulay
Sent: Tuesday, February 6, 2024 6:04 PM
To: Legacy User Group 
Subject: Re: [LegacyUG] A question about FAG numbers {user ID]

 

This is not the same as the FAG number as the Fag number is a direct link to 
Find a Grave whereas the user ID is connected to naught.

 

Ian

 

On Tue, Feb 6, 2024 at 1:50 PM Ms Mary K. Lund via LegacyUserGroup 
mailto:legacyusergroup@legacyusers.com> > 
wrote:

To answer the question of "to RIN' or not to "RIN": Copied from Legacy file Help

 

User ID

This field is for any reference number you want to record for this individual.  
You can use any combination of letters, numbers and punctuation marks.  There 
is a tool on the Options > Customize > Other tab where you can automatically 
fill the User ID fields for all individuals with the RIN numbers and optional 
text.  (See Customize - Other for more information.)

Mary K. Lund

 

On Friday, February 2, 2024 at 05:24:08 AM CST, Jenny M Benson 
mailto:ge...@cedarbank.me.uk> > wrote: 

 

 

On 02/02/2024 01:12, Ian Macaulay wrote:
> Do any of you see why Find a grave numbers should not be made a unique 
> field.
> In order to not allow a duplicate entry.  I have for a second time 
> requested this feature and am hoping that there is not a problem 
> somewhere else that I have not considered.
> 
> My  program crashes often  and always has a duplicate or two in the 
> error report.
> It is the only reason I can find for these crashes.  It takes three runs 
> at  File maintenance to get up and running again.
> 
> If you have an objection to making this field unique please post it/
> If not and you agree with my poorly stated state of affairs, send a 
> request for feature to Legacy via the  request feature in the "Help/ 
> request featurte"  drop down.

Seems a good idea so I have submitted a request.

-- 
Jenny M Benson
Wrexham, UK




-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com <mailto: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 <mailto: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/



-- 

  ICMac Sales: Hobby consultant (1986r.)

Office hours:   10:00 Am - 5:00 PM  most days

  Macaulay Genealogy
 Family Matters
  Ian Macaulayof Carp, Ontario

-- 

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] A question about FAG numbers {user ID]

2024-02-06 Thread Ian Macaulay 
This is not the same as the FAG number as the Fag number is a direct link
to Find a Grave whereas the user ID is connected to naught.

Ian

On Tue, Feb 6, 2024 at 1:50 PM Ms Mary K. Lund via LegacyUserGroup <
legacyusergroup@legacyusers.com> wrote:

> To answer the question of "to RIN' or not to "RIN": Copied from Legacy
> file Help
>
> *User ID*
>
> This field is for any reference number you want to record for this
> individual.  You can use any combination of letters, numbers and
> punctuation marks.  There is a tool on the *Options > Customize > Other *tab
> where you can automatically fill the *User ID* fields for all individuals
> with the RIN numbers and optional text.  (See Customize - Other for more
> information.)
> Mary K. Lund
>
> On Friday, February 2, 2024 at 05:24:08 AM CST, Jenny M Benson <
> ge...@cedarbank.me.uk> wrote:
>
>
> On 02/02/2024 01:12, Ian Macaulay wrote:
> > Do any of you see why Find a grave numbers should not be made a unique
> > field.
> > In order to not allow a duplicate entry.  I have for a second time
> > requested this feature and am hoping that there is not a problem
> > somewhere else that I have not considered.
> >
> > My  program crashes often  and always has a duplicate or two in the
> > error report.
> > It is the only reason I can find for these crashes.  It takes three runs
> > at  File maintenance to get up and running again.
> >
> > If you have an objection to making this field unique please post it/
> > If not and you agree with my poorly stated state of affairs, send a
> > request for feature to Legacy via the  request feature in the "Help/
> > request featurte"  drop down.
>
> Seems a good idea so I have submitted a request.
>
> --
> Jenny M Benson
> Wrexham, UK
>
>
>
> --
>
> 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/
>


-- 
  ICMac Sales: Hobby consultant (1986r.)
Office hours:   10:00 Am - 5:00 PM  most days
  Macaulay Genealogy
 Family Matters
  Ian Macaulayof Carp, Ontario
-- 

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] A question about FAG numbers {user ID]

2024-02-06 Thread Ms Mary K. Lund via LegacyUserGroup 
 To answer the question of "to RIN' or not to "RIN": Copied from Legacy file 
Help

User ID

This field is for any reference number you want to record for this individual.  
You can use any combination of letters, numbers and punctuation marks.  There 
is a tool on the Options > Customize > Other tab where you can automatically 
fill the User ID fields for all individuals with the RIN numbers and optional 
text.  (See Customize - Other for more information.)
Mary K. Lund
On Friday, February 2, 2024 at 05:24:08 AM CST, Jenny M Benson 
 wrote:  
 
 On 02/02/2024 01:12, Ian Macaulay wrote:
> Do any of you see why Find a grave numbers should not be made a unique 
> field.
> In order to not allow a duplicate entry.  I have for a second time 
> requested this feature and am hoping that there is not a problem 
> somewhere else that I have not considered.
> 
> My  program crashes often  and always has a duplicate or two in the 
> error report.
> It is the only reason I can find for these crashes.  It takes three runs 
> at  File maintenance to get up and running again.
> 
> If you have an objection to making this field unique please post it/
> If not and you agree with my poorly stated state of affairs, send a 
> request for feature to Legacy via the  request feature in the "Help/ 
> request featurte"  drop down.

Seems a good idea so I have submitted a request.

-- 
Jenny M Benson
Wrexham, UK


-- 

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] A question about FAG numbers

2024-02-03 Thread Ian Macaulay 
Check repair fails to run when the system has crashed.  It first stops at
the indexing and then second round at check 46.
then the third time round it completes and pops out the error report.

FAG numbers are unique in FAG,  They do not repeat nor reuse the numbers.
I can see no reason that Legacy cannot "unique" the field.

As for the Find a grave dual burials, One should be marked as a Cenotaph,
These duplicate entries for single people are usually war graves.

Ian

On Fri, Feb 2, 2024 at 11:31 PM Cathy Pinner  wrote:

> Dave,
> Don't you use File > File Maintenance > Check/Repair regularly to keep
> your database healthy? All databases need maintenance just like cars need
> servicing.
> Isn't it picking up your 0's as duplicates?
> It's highly unlikely that Legacy will add code to check whether you are
> entering a duplicate number when saving a new number since it has this
> check in Check/Repair.
>
> Cathy
>
> Dave Naylor 
> Saturday, 3 February 2024 4:17 AM
> Hello fellow Leggers,
>
> I have been placing a zero in the FAG field when I know there's a grave
> but don't know the cemetery.  So YES I have duplicates but they haven't
> been any problem to me or to running Legacy.
>
> If the FAG field is made unique I will come up with some other method to
> suit my needs.
>
> Cheers! -- Dave N.
>
>
> On 2024-02-01 8:12 p.m., Ian Macaulay wrote:
>
>
> Ian Macaulay 
> Friday, 2 February 2024 9:12 AM
> Do any of you see why Find a grave numbers should not be made a unique
> field.
> In order to not allow a duplicate entry.  I have for a second time
> requested this feature and am hoping that there is not a problem somewhere
> else that I have not considered.
>
> My  program crashes often  and always has a duplicate or two in the error
> report.
> It is the only reason I can find for these crashes.  It takes three runs
> at  File maintenance to get up and running again.
>
> If you have an objection to making this field unique please post it/
> If not and you agree with my poorly stated state of affairs, send a
> request for feature to Legacy via the  request feature in the "Help/
> request featurte"  drop down.
>
> Ian
>
> --
>   ICMac Sales: Hobby consultant (1986r.)
> Office hours:   10:00 Am - 5:00 PM  most days
>   Macaulay Genealogy
>  Family Matters
>   Ian Macaulayof Carp, Ontario
>
>
>
> --
>
> 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/
>


-- 
  ICMac Sales: Hobby consultant (1986r.)
Office hours:   10:00 Am - 5:00 PM  most days
  Macaulay Genealogy
 Family Matters
  Ian Macaulayof Carp, Ontario
-- 

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] A question about FAG numbers

2024-02-02 Thread Cathy Pinner 

Dave,
Don't you use File > File Maintenance > Check/Repair regularly to keep 
your database healthy? All databases need maintenance just like cars 
need servicing.

Isn't it picking up your 0's as duplicates?
It's highly unlikely that Legacy will add code to check whether you are 
entering a duplicate number when saving a new number since it has this 
check in Check/Repair.


Cathy


Dave Naylor 
Saturday, 3 February 2024 4:17 AM
Hello fellow Leggers,

I have been placing a zero in the FAG field when I know there's a 
grave but don't know the cemetery.  So YES I have duplicates but they 
haven't been any problem to me or to running Legacy.


If the FAG field is made unique I will come up with some other method 
to suit my needs.


Cheers! -- Dave N.


On 2024-02-01 8:12 p.m., Ian Macaulay wrote:


Ian Macaulay 
Friday, 2 February 2024 9:12 AM
Do any of you see why Find a grave numbers should not be made a unique 
field.
In order to not allow a duplicate entry. I have for a second time 
requested this feature and am hoping that there is not a problem 
somewhere else that I have not considered.


My program crashes often  and always has a duplicate or two in the 
error report.
It is the only reason I can find for these crashes. It takes three 
runs at  File maintenance to get up and running again.


If you have an objection to making this field unique please post it/
If not and you agree with my poorly stated state of affairs, send a 
request for feature to Legacy via the  request feature in the "Help/ 
request featurte"  drop down.


Ian

--
  ICMac Sales:     Hobby consultant (1986r.)
Office hours:   10:00 Am - 5:00 PM  most days
              Macaulay Genealogy
 Family Matters
      Ian Macaulay    of Carp, Ontario




-- 

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] A question about FAG numbers

2024-02-02 Thread jclinx 
I’ve always used the FAG field number for an individual to go directly to that 
person in FAG when I’m working with the family. If there’s a duplicate number, 
shouldn’t that be either the Genealogist’s or FAG’s error?

 

Jane in Phoenix

 

From: LegacyUserGroup  On Behalf Of 
Ian Macaulay
Sent: Friday, February 2, 2024 5:19 PM
To: Legacy User Group 
Subject: Re: [LegacyUG] A question about FAG numbers

 

The FAG number actually can link to FAG. It is an important part of my 
research.  The problem is when Ruth white who married Joe blow is registered as 
Ruth Blowin one set and Ruth  White in another and they both have the same FAG 
ID.  within a few searches the system crashes.  If Legact reported a duplicate 
in the FAG field this would not happen.  Making the number unique would solve 
the issue with the least amount of code.

 

On Fri, Feb 2, 2024 at 1:40 PM TheyBrokeTheMold mailto:theybrokethem...@gmail.com> > wrote:

I design databases, and you can never satisfy everyone.  So, in my designs, I 
usually provide a few "User Defined" fields for Text/Number/Date/Binary options.

 

That would be my suggestion.  That way, you can use a field for FAG, and 
someone else can use the same field for some DNA reference, or anything else 
important to them.  This fields would have no specific name other than User1, 
User2, User3, etc.  But you would know what each of those fields are used for.

 

I don't recall seeing any User Defined fields, but it is possible they already 
exist?

 

Hope this was helpful.

 

 

 Original message 

From: Jenny M Benson mailto:ge...@cedarbank.me.uk> > 

Date: 2/2/24 6:24 AM (GMT-05:00) 

To: legacyusergroup@legacyusers.com <mailto:legacyusergroup@legacyusers.com>  

Subject: Re: [LegacyUG] A question about FAG numbers 

 

On 02/02/2024 01:12, Ian Macaulay wrote:
> Do any of you see why Find a grave numbers should not be made a unique 
> field.
> In order to not allow a duplicate entry.  I have for a second time 
> requested this feature and am hoping that there is not a problem 
> somewhere else that I have not considered.
> 
> My  program crashes often  and always has a duplicate or two in the 
> error report.
> It is the only reason I can find for these crashes.  It takes three runs 
> at  File maintenance to get up and running again.
> 
> If you have an objection to making this field unique please post it/
> If not and you agree with my poorly stated state of affairs, send a 
> request for feature to Legacy via the  request feature in the "Help/ 
> request featurte"  drop down.

Seems a good idea so I have submitted a request.

-- 
Jenny M Benson
Wrexham, UK


-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com <mailto: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 <mailto: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/



-- 

  ICMac Sales: Hobby consultant (1986r.)

Office hours:   10:00 Am - 5:00 PM  most days

  Macaulay Genealogy
 Family Matters
  Ian Macaulayof Carp, Ontario

-- 

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] A question about FAG numbers

2024-02-02 Thread Ian Macaulay 
The FAG number actually can link to FAG. It is an important part of my
research.  The problem is when Ruth white who married Joe blow is
registered as Ruth Blowin one set and Ruth  White in another and they both
have the same FAG ID.  within a few searches the system crashes.  If Legact
reported a duplicate in the FAG field this would not happen.  Making the
number unique would solve the issue with the least amount of code.

On Fri, Feb 2, 2024 at 1:40 PM TheyBrokeTheMold 
wrote:

> I design databases, and you can never satisfy everyone.  So, in my
> designs, I usually provide a few "User Defined" fields for
> Text/Number/Date/Binary options.
>
> That would be my suggestion.  That way, you can use a field for FAG, and
> someone else can use the same field for some DNA reference, or anything
> else important to them.  This fields would have no specific name other than
> User1, User2, User3, etc.  But you would know what each of those fields are
> used for.
>
> I don't recall seeing any User Defined fields, but it is possible they
> already exist?
>
> Hope this was helpful.
>
>
>  Original message 
> From: Jenny M Benson 
> Date: 2/2/24 6:24 AM (GMT-05:00)
> To: legacyusergroup@legacyusers.com
> Subject: Re: [LegacyUG] A question about FAG numbers
>
> On 02/02/2024 01:12, Ian Macaulay wrote:
> > Do any of you see why Find a grave numbers should not be made a unique
> > field.
> > In order to not allow a duplicate entry.  I have for a second time
> > requested this feature and am hoping that there is not a problem
> > somewhere else that I have not considered.
> >
> > My  program crashes often  and always has a duplicate or two in the
> > error report.
> > It is the only reason I can find for these crashes.  It takes three runs
> > at  File maintenance to get up and running again.
> >
> > If you have an objection to making this field unique please post it/
> > If not and you agree with my poorly stated state of affairs, send a
> > request for feature to Legacy via the  request feature in the "Help/
> > request featurte"  drop down.
>
> Seems a good idea so I have submitted a request.
>
> --
> Jenny M Benson
> Wrexham, UK
>
>
> --
>
> 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/
>


-- 
  ICMac Sales: Hobby consultant (1986r.)
Office hours:   10:00 Am - 5:00 PM  most days
  Macaulay Genealogy
 Family Matters
  Ian Macaulayof Carp, Ontario
-- 

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] A question about FAG numbers

2024-02-02 Thread hpeterjr 
NOT a good idea…

It would not be a standard so how would that export in a way to become standard 
according to GEDCOM rules…

Ann vice versa how could that information be imported into something other than 
…. “Legacy”?

 

And as Legacy stands now we can pretty much create any kind of event we want…. 
And even those Non-standard events create problems when trying to export … as 
mentioned above..

See an example below:



Regards

Henry

p.s. *Note: not all elements are used some have no dates or some of the fields 
may be used in different ways..

 

From: LegacyUserGroup  On Behalf Of 
TheyBrokeTheMold
Sent: Friday, February 2, 2024 12:40 PM
To: Legacy User Group 
Subject: Re: [LegacyUG] A question about FAG numbers

 

I design databases, and you can never satisfy everyone.  So, in my designs, I 
usually provide a few "User Defined" fields for Text/Number/Date/Binary options.

 

That would be my suggestion.  That way, you can use a field for FAG, and 
someone else can use the same field for some DNA reference, or anything else 
important to them.  This fields would have no specific name other than User1, 
User2, User3, etc.  But you would know what each of those fields are used for.

 

I don't recall seeing any User Defined fields, but it is possible they already 
exist?

 

Hope this was helpful.

 

 

 Original message 

From: Jenny M Benson mailto:ge...@cedarbank.me.uk> > 

Date: 2/2/24 6:24 AM (GMT-05:00) 

To: legacyusergroup@legacyusers.com <mailto:legacyusergroup@legacyusers.com>  

Subject: Re: [LegacyUG] A question about FAG numbers 

 

On 02/02/2024 01:12, Ian Macaulay wrote:
> Do any of you see why Find a grave numbers should not be made a unique 
> field.
> In order to not allow a duplicate entry.  I have for a second time 
> requested this feature and am hoping that there is not a problem 
> somewhere else that I have not considered.
> 
> My  program crashes often  and always has a duplicate or two in the 
> error report.
> It is the only reason I can find for these crashes.  It takes three runs 
> at  File maintenance to get up and running again.
> 
> If you have an objection to making this field unique please post it/
> If not and you agree with my poorly stated state of affairs, send a 
> request for feature to Legacy via the  request feature in the "Help/ 
> request featurte"  drop down.

Seems a good idea so I have submitted a request.

-- 
Jenny M Benson
Wrexham, UK


-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com <mailto: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] A question about FAG numbers

2024-02-02 Thread Dave Naylor 

Hello fellow Leggers,

I have been placing a zero in the FAG field when I know there's a grave 
but don't know the cemetery.  So YES I have duplicates but they haven't 
been any problem to me or to running Legacy.


If the FAG field is made unique I will come up with some other method to 
suit my needs.


Cheers! -- Dave N.


On 2024-02-01 8:12 p.m., Ian Macaulay wrote:
Do any of you see why Find a grave numbers should not be made a unique 
field.
In order to not allow a duplicate entry.  I have for a second time 
requested this feature and am hoping that there is not a problem 
somewhere else that I have not considered.


My  program crashes often  and always has a duplicate or two in the 
error report.
It is the only reason I can find for these crashes.  It takes three 
runs at  File maintenance to get up and running again.


If you have an objection to making this field unique please post it/
If not and you agree with my poorly stated state of affairs, send a 
request for feature to Legacy via the  request feature in the "Help/ 
request featurte"  drop down.


Ian

--
  ICMac Sales:     Hobby consultant (1986r.)
Office hours:   10:00 Am - 5:00 PM  most days
              Macaulay Genealogy
                 Family Matters
      Ian Macaulay    of Carp, Ontario


--
David Naylor
Hamilton, Ontario, Canada
< https://hotrum.ca/naylor/ >
- 

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] A question about FAG numbers

2024-02-02 Thread Ms Mary K. Lund via LegacyUserGroup 
 At some point I think there was a "Reference" field that could be 
user-defined. 
Mary K. Lund
On Friday, February 2, 2024 at 12:41:07 PM CST, TheyBrokeTheMold 
 wrote:  
 
 I design databases, and you can never satisfy everyone.  So, in my designs, I 
usually provide a few "User Defined" fields for Text/Number/Date/Binary options.
That would be my suggestion.  That way, you can use a field for FAG, and 
someone else can use the same field for some DNA reference, or anything else 
important to them.  This fields would have no specific name other than User1, 
User2, User3, etc.  But you would know what each of those fields are used for.
I don't recall seeing any User Defined fields, but it is possible they already 
exist?
Hope this was helpful.

 Original message From: Jenny M Benson  
Date: 2/2/24 6:24 AM (GMT-05:00) To: legacyusergroup@legacyusers.com Subject: 
Re: [LegacyUG] A question about FAG numbers 
On 02/02/2024 01:12, Ian Macaulay wrote:
> Do any of you see why Find a grave numbers should not be made a unique 
> field.
> In order to not allow a duplicate entry.  I have for a second time 
> requested this feature and am hoping that there is not a problem 
> somewhere else that I have not considered.
> 
> My  program crashes often  and always has a duplicate or two in the 
> error report.
> It is the only reason I can find for these crashes.  It takes three runs 
> at  File maintenance to get up and running again.
> 
> If you have an objection to making this field unique please post it/
> If not and you agree with my poorly stated state of affairs, send a 
> request for feature to Legacy via the  request feature in the "Help/ 
> request featurte"  drop down.

Seems a good idea so I have submitted a request.

-- 
Jenny M Benson
Wrexham, UK


-- 

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/
  -- 

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] A question about FAG numbers

2024-02-02 Thread TheyBrokeTheMold 
I design databases, and you can never satisfy everyone.  So, in my designs, I 
usually provide a few "User Defined" fields for Text/Number/Date/Binary 
options.That would be my suggestion.  That way, you can use a field for FAG, 
and someone else can use the same field for some DNA reference, or anything 
else important to them.  This fields would have no specific name other than 
User1, User2, User3, etc.  But you would know what each of those fields are 
used for.I don't recall seeing any User Defined fields, but it is possible they 
already exist?Hope this was helpful.
 Original message From: Jenny M Benson  
Date: 2/2/24  6:24 AM  (GMT-05:00) To: legacyusergroup@legacyusers.com Subject: 
Re: [LegacyUG] A question about FAG numbers On 02/02/2024 01:12, Ian Macaulay 
wrote:> Do any of you see why Find a grave numbers should not be made a unique 
> field.> In order to not allow a duplicate entry.  I have for a second time > 
requested this feature and am hoping that there is not a problem > somewhere 
else that I have not considered.> > My  program crashes often  and always has a 
duplicate or two in the > error report.> It is the only reason I can find for 
these crashes.  It takes three runs > at  File maintenance to get up and 
running again.> > If you have an objection to making this field unique please 
post it/> If not and you agree with my poorly stated state of affairs, send a > 
request for feature to Legacy via the  request feature in the "Help/ > request 
featurte"  drop down.Seems a good idea so I have submitted a request.-- Jenny M 
BensonWrexham, UK-- LegacyUserGroup mailing 
listLegacyUserGroup@legacyusers.comTo manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.comArchives 
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] A question about FAG numbers

2024-02-02 Thread Jenny M Benson 

On 02/02/2024 01:12, Ian Macaulay wrote:
Do any of you see why Find a grave numbers should not be made a unique 
field.
In order to not allow a duplicate entry.  I have for a second time 
requested this feature and am hoping that there is not a problem 
somewhere else that I have not considered.


My  program crashes often  and always has a duplicate or two in the 
error report.
It is the only reason I can find for these crashes.  It takes three runs 
at  File maintenance to get up and running again.


If you have an objection to making this field unique please post it/
If not and you agree with my poorly stated state of affairs, send a 
request for feature to Legacy via the  request feature in the "Help/ 
request featurte"  drop down.


Seems a good idea so I have submitted a request.

--
Jenny M Benson
Wrexham, UK


--

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] A question about FAG numbers

2024-02-01 Thread Robin McCarthy 
Crystal,
 
Ian is requesting that the Find-a-Grave number entered in the field you mention 
be unique, meaning that it cannot be used again in another person's 
Find-a-Grave ID field.
 
Robin
 

> On 02/01/2024 6:01 PM PST Crystal Emory  wrote:
>  
>  
> Hi Ian, I'm a little confused. There is a Findagrave ID Field under the 
> events at the bottom of the screen. I just recently found that you can go 
> into the options/customize and turn the option to put the ID number after the 
> name so it shows up on the main screen.  Where would you like to see the 
> Findagrave ID as opposed to what I am seeing? I am always up for supporting a 
> good suggestion and maybe this is why i am having Runtime Failures, but the 
> feature does find duplicate Findagrave ID's for me which I have no issues 
> once they are corrected. I hope I make sense. 
>  
> Crystal 
> 
> On Thu, Feb 1, 2024 at 8:14 PM Ian Macaulay  mailto:macau...@icmac.ca> wrote:
> 
> > Do any of you see why Find a grave numbers should not be made a unique 
> > field.
> > In order to not allow a duplicate entry.  I have for a second time 
> > requested this feature and am hoping that there is not a problem somewhere 
> > else that I have not considered.
> >  
> > My  program crashes often  and always has a duplicate or two in the error 
> > report.
> > It is the only reason I can find for these crashes.  It takes three runs at 
> >  File maintenance to get up and running again.
> >  
> > If you have an objection to making this field unique please post it/
> > If not and you agree with my poorly stated state of affairs, send a request 
> > for feature to Legacy via the  request feature in the "Help/ request 
> > featurte"  drop down.
> >  
> > Ian
> > 
> > --
> >   ICMac Sales: Hobby consultant (1986r.)
> > Office hours:   10:00 Am - 5:00 PM  most days
> >   Macaulay Genealogy
> >  Family Matters
> >   Ian Macaulayof Carp, Ontario
> >  
> > --
> > 
> > LegacyUserGroup mailing list
> > LegacyUserGroup@legacyusers.com mailto: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/
> 
-- 

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] A question about FAG numbers

2024-02-01 Thread Crystal Emory 
Hi Ian, I'm a little confused. There is a Findagrave ID Field under the
events at the bottom of the screen. I just recently found that you can go
into the options/customize and turn the option to put the ID number after
the name so it shows up on the main screen.  Where would you like to see
the Findagrave ID as opposed to what I am seeing? I am always up for
supporting a good suggestion and maybe this is why i am having Runtime
Failures, but the feature does find duplicate Findagrave ID's for me which
I have no issues once they are corrected. I hope I make sense.

Crystal

On Thu, Feb 1, 2024 at 8:14 PM Ian Macaulay  wrote:

> Do any of you see why Find a grave numbers should not be made a unique
> field.
> In order to not allow a duplicate entry.  I have for a second time
> requested this feature and am hoping that there is not a problem somewhere
> else that I have not considered.
>
> My  program crashes often  and always has a duplicate or two in the error
> report.
> It is the only reason I can find for these crashes.  It takes three runs
> at  File maintenance to get up and running again.
>
> If you have an objection to making this field unique please post it/
> If not and you agree with my poorly stated state of affairs, send a
> request for feature to Legacy via the  request feature in the "Help/
> request featurte"  drop down.
>
> Ian
>
> --
>   ICMac Sales: Hobby consultant (1986r.)
> Office hours:   10:00 Am - 5:00 PM  most days
>   Macaulay Genealogy
>  Family Matters
>   Ian Macaulayof Carp, Ontario
> --
>
> 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/

[LegacyUG] A question about FAG numbers

2024-02-01 Thread Ian Macaulay 
Do any of you see why Find a grave numbers should not be made a unique
field.
In order to not allow a duplicate entry.  I have for a second time
requested this feature and am hoping that there is not a problem somewhere
else that I have not considered.

My  program crashes often  and always has a duplicate or two in the error
report.
It is the only reason I can find for these crashes.  It takes three runs
at  File maintenance to get up and running again.

If you have an objection to making this field unique please post it/
If not and you agree with my poorly stated state of affairs, send a request
for feature to Legacy via the  request feature in the "Help/ request
featurte"  drop down.

Ian

-- 
  ICMac Sales: Hobby consultant (1986r.)
Office hours:   10:00 Am - 5:00 PM  most days
  Macaulay Genealogy
 Family Matters
  Ian Macaulayof Carp, Ontario
-- 

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/