|
That brought back some really bad memories Vern. Long weekends trying--
to fix that kind of issue in a manufacturing system.
Things have definitely improved so, so much over the years.
Cheers,
Karl.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Vern Hamberg via MIDRANGE-L
Sent: Friday, February 4, 2022 9:37 AM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Cc: Vern Hamberg <vhamberg@xxxxxxxxxxxxxxx>
Subject: Re: Does an Relative Record number ever change
There was a day when things like MAPICS used RRN to connect items in a
bill of materials. A reorganization could mess that up, IIRC, and
probably reusing deleted records, too.
Gone be the good old days, eh?
Cheers
Vern
On 2/4/2022 2:26 AM, Niels Liisberg wrote:
The problem can be if you reorganize using at index (LF) .. thatwrote:
will change the physical order and there by the rrn. So I would
never use the rrn as the primary key if you look for robust solution.
On Wed, Feb 2, 2022 at 6:36 PM Ken Meade <kmeade@xxxxxxxxxxxxxxxxx>
to it.
All,
We are using an audit tool that pulls from our journal and then
outputs to a file. Usually we are good to go, but this time I see
that we don't have this file keyed in a way that we can easily tie
out
deleted records?We can build a view use the RRN as that is captured in the file and
tying out to the RRN in the primary file and capture a key
field(s), but the question came up as to would the RRN in the
primary file ever change if we did a Reorg on the file or if the
file is set up to reuse
Thanks,
Ken M.
Ken Meade | Director of Information Technology
[ mailto:kmeade@xxxxxxxxxxxxxxxxx | kmeade@xxxxxxxxxxxxxxxxx ] |
(603)
444-3570
Littleton Coin Company, Inc.
1309 Mt Eustis Rd, Littleton NH 03561
[ http://www.littletoncoin.com/ | www.littletoncoin.com ]
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.
Help support midrange.com by shopping at amazon.com with our
affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.