RE: Primary Keys & Duplicate Values

2002-10-08 Thread Bill Grover
From: Andy Ousterhout [mailto:[EMAIL PROTECTED]] > Sent: Monday, October 07, 2002 10:13 PM > To: CF-Talk > Subject: RE: Primary Keys & Duplicate Values > > > I have the same issue in that I have a web system that I am > integrating with > my Order Management/Mfg system.

RE: Primary Keys & Duplicate Values

2002-10-07 Thread Andy Ousterhout
PM To: CF-Talk Subject: Re: Primary Keys & Duplicate Values Thanks. Yes I understand. What I could do is to combine both modelno and the name of the manufacturer and use them in updates. That should prevent updating the wrong records should the model number not be unique. The problem with

Re: Primary Keys & Duplicate Values

2002-10-07 Thread Srimanta
: "Andy Ousterhout" <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Tuesday, October 08, 2002 8:34 AM Subject: RE: Primary Keys & Duplicate Values > I highly recommend that you don't make Model number your primary key. Add a > new field, n

RE: Primary Keys & Duplicate Values

2002-10-07 Thread Andy Ousterhout
as been an incredible and preventable pain in the back side. What does everyone else recommend? Andy -Original Message- From: Srimanta [mailto:[EMAIL PROTECTED]] Sent: Monday, October 07, 2002 1:48 PM To: CF-Talk Subject: Re: Primary Keys & Duplicate Values Thanks Field 1 represent

Re: Primary Keys & Duplicate Values

2002-10-07 Thread Srimanta
gt; To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Monday, October 07, 2002 10:52 PM Subject: RE: Primary Keys & Duplicate Values > Yep, your problem is that you have dupes in the column you want to tag as a > PK. is Field 1 the only field which is uses dupe values? are the reco

RE: Primary Keys & Duplicate Values

2002-10-07 Thread Subramanian, Samy
> 1) good luck -Original Message- From: Andy Ousterhout [mailto:[EMAIL PROTECTED]] Sent: Monday, October 07, 2002 10:24 AM To: CF-Talk Subject: RE: Primary Keys & Duplicate Values If all of your current fields have meaning, I recommend that you add a new field that is a meaningl

RE: Primary Keys & Duplicate Values

2002-10-07 Thread Andy Ousterhout
If all of your current fields have meaning, I recommend that you add a new field that is a meaningless number that you use as your key field. I've found that if I use a field with meaning as my key that I end up wanting to change that value. Exceptions might be code tables like ZIP Code and Stat

RE: Primary Keys & Duplicate Values

2002-10-07 Thread Robertson-Ravo, Neil (REC)
Yep, your problem is that you have dupes in the column you want to tag as a PK. is Field 1 the only field which is uses dupe values? are the records technically unique or can you safely delete them? -Original Message- From: Srimanta [mailto:[EMAIL PROTECTED]] Sent: 07 October 2002 10