Stuart McLachlan
stuart at lexacorp.com.pg
Fri May 27 17:45:15 CDT 2011
There's nothing wrong with using a batch number or other Intelligent Key in your table. Just don't use is as a Primary/Foreign Key for relationships between other tables. :-) -- Stuart On 27 May 2011 at 12:09, Arthur Fuller wrote: > But that said, I am not a big fan of IKs. Like most of us on this > forum, I tend to favour AutoNumber out of force of habit rather than > rational analysis. I have read numerous things by Joe Celko and Chis > Date which refute the use of AutoNumber|Idnentity Keys, and I accept > them halfway. I don't give a fork from which a given tire was hatched, > unless and until several of these instances have caused highway > fatalities. Therefore, I need build this (batch) into the design, so > that I can report to all owners of said tires a warning that there are > potential issues. > > This is going to be extremely problematic to solve with the AutoNumber > scenario. An intelligent key could make the query dramatically > simpler. > > That's all I'm saying. I typically use AutoNumbers in almost every app > I write, but the more crucial and life-threatening the app, the more > likely I shall use IKs. > > A. > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >