× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



General rule is the surrogate primary keys, ie. auto-identity, should never
been seen by the users.

So while Customer# is basically a surrogate key anyway, since you'd put it
on invoices, statements, ect. It becomes a "business" data field and thus
you want another field to use as a primary key.

Charles

On Mon, Aug 28, 2017 at 11:17 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

The 666 is a good example. Considering that the honeymoon from my first
marriage was in room 1313 of the Sheraton in Ocho Rios Jamaica. I didn't
even think hotels had a 13th floor.
I can see that...


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Buck Calabro <kc2hiz@xxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx
Date: 08/28/2017 01:11 PM
Subject: Re: Database design question
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



On 8/28/2017 12:49 PM, Rob Berendt wrote:
Trying to see what business reason there would be to changing the
customer
number.

Instead of 'customer number' think 'telephone number'.

From the 'Believe it or Not' files comes this one: a new customer signs
on to a business, and is aghast to discover that the computer has
assigned them a customer number with 666 in it. Customer insisted on a
new assignment, and got it.

It seems to me that anything facing the customer is subject to change.

--
--buck

Try wiki.midrange.com!

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.