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 <[email protected]>
Date: 2/2/24 6:24 AM (GMT-05:00) To: [email protected] 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
[email protected] manage your subscription and unsubscribe
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.comArchives
at:http://www.mail-archive.com/[email protected]/
--
LegacyUserGroup mailing list
[email protected]
To manage your subscription and unsubscribe
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/[email protected]/
