[AccessD] Primary Key Best Practices

I have exposed an ANPK, in fact, the system I'm working on at the moment
exposes it for the main table.  It's a help desk system, and the Request
table ID field, "TicketNumber" is an AutoNumber, the primary key, and is
what the user sees as their 'ticket number'.  

As far as the concern of someone saying they have to be
sequential...they are sequential.  The interface provides NO way to
delete a request.  In fact, I find I build VERY few systems where I ever
delete data.  

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Bartow
Sent: Wednesday, July 25, 2007 11:11 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Primary Key Best Practices

LOL!

I actually have the same view on PK but have recently had to expose PKs
in
an application for a client. (Well, I suppose I could have told them NO
but
then I'd probably not still be working for them.)

They implemented a new functionality in their GIS system. Instead of
paying
me to implement it correctly, they tried to have "local" firm implement
the
GIS (spatial) portion and retain me to do the "tabular" portion. (The
whole
thing is ridiculous but when you do government work you come to expect
this.) Anyway, I had to expose the PK of certain tables in the interface
because the "local" firm apparently doesn't know how to connect to an
mdb in
order to pull up a combo box in for the staff to choose from. Hence the
staff is manually entering the PK to connect the spatial elements to the
tabular elements. Wrought with danger is all I can say. I don't think
the
local firm is working there anymore - so hopefully I get to fix this
mess
some day }:-p

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby

It comes from discussions here on this list where any time you expose
the PK
to view, some idiot wants to use it for some purpose that it is not
supposed
to be used for (like a "must be in order, with no values missing" number
in
an accounting system.  Obviously we can and do delete records all the
time
so using the PK for such a rule / purpose guarantees issues whenever the
idiot strikes, thus simply NEVER expose it to view.  

The PK's function (in real life) is exactly and only for use as a
pointer
from a child back to the parent.  

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
The information contained in this transmission is intended only for the person or entity to which it is addressed and may contain II-VI Proprietary and/or II-VI BusinessSensitve material. If you are not the intended recipient, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. You are notified that any review, retransmission, copying, disclosure, dissemination, or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited.