Re: Not keying physical files

[rob@xxxxxxxxx]

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
How many have seen the problem where the PF access path problem occurred
but had no problems with files with only LF access paths?
  (little to no show of hands)

How many people have had duplicate records because their PF had no keys,
(like our BPCS item master)?
  (large show of hands)

How many people have had their efforts to implement Referential Integrity
thwarted because the PF's had no keys?
  (indeterminate number of hands)

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin




"Fisher, Don" <Dfisher@roomstoreeast.com>
Sent by: midrange-l-admin@midrange.com
04/24/2002 08:59 AM
Please respond to midrange-l


        To:     "'midrange-l@midrange.com'" <midrange-l@midrange.com>
        cc:
        Fax to:
        Subject:        Not keying physical files


As it was explained to me, a keyed physical file would cause all access
paths built over the file to be rebuilt in the event of a hard system
crash
or other damage to the physical file's access path.

Therefore we have a policy of only keying physical files that will have
low
record counts.

Anyone know if this is correct?

Donald R. Fisher, III
Project Manager
The Roomstore Furniture Company
(804) 784-7600 extension 2124
DFisher@roomstoreeast.com

<clip>
I could never figure out why Sears so heavily promoted NOT having your
PF's
keyed and depending on the LF's for
your keys...back in the old days...:)
<clip>
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.