🚀 go-pugleaf

Primary key is always unique key - remove primary key definition from
TABLE2.NDX.

//------------------------------------------
Regards,
Viatcheslav V. Vassiliev
http://www.managed-vcl.com
http://www.oledbdirect.com



"Ted Byers" <r.ted.byers@sympatico.ca> �������/�������� � ��������
���������: news:3fa2c520$1@newsgroups.borland.com...
>
> > var conn = new ActiveXObject("ADODB.Connection");
> > conn.Open(connStr);
> > conn.Execute("CREATE TABLE JUNK (NDX COUNTER(1, 1) NOT NULL CONSTRAINT
> > PRIMKEY PRIMARY KEY, " +
> >  "NAMEVALUE VARCHAR(60) WITH COMPRESSION NOT NULL)");
> > conn.Execute("CREATE TABLE TABLE2 (NDX INTEGER NOT NULL CONSTRAINT
PRIMKEY
> > PRIMARY KEY, " +
> >  "COL2 VARCHAR(20) WITH COMPRESSION, CONSTRAINT FORKEY FOREIGN KEY (NDX)
> > REFERENCES JUNK(NDX) " +
> >  "ON UPDATE CASCADE ON DELETE SET NULL)");
> > conn = null;
> > //----------------------------
>
> Thanks loads.  I translated this, and as expected it works, but when I
> examined the resulting database using MS Access, I saw one problem.  In
the
> table TABLE2, NDX is shown as being indexed, as expected, but without
> duplicates.  This is inconsistent with what is shown in the relationships
> diagram, where the relationship is shown as being one (in table JUNK) to
> many (in table TABLE2).  How would I change the SQL you show to change NDX
> in TABLE2 to being indexed but with duplicates being allowed?
>
> Cheers,
>
> Ted
>
>