Referential integrity. AutoNumber.
in [Forms]
|
From: Arvin Meyer [MVP] on 19 Jan 2010 08:41 Yes in: Table: B. Field: A (Number) the number is a long integer and you should have Referential Integrity. If you can't force RI, you probably have some bad data in Table B. -- Arvin Meyer, MCP, MVP http://www.datastrat.com http://www.mvps.org/access http://www.accessmvp.com "Peter" <Peter(a)discussions.microsoft.com> wrote in message news:5023B8FA-6191-44EA-AF25-82A41C4D9B40(a)microsoft.com... > Hi all..I want to create a one-to-many relation between: > > Table: A. Field : A (AutoNumber) (Primary Key) > > One to many relation > > Table: B. Field: A (Number) > > Am I thinking wrong here? If I cant Enforce Referential Integrity in this > case should I still create a relation, but without RI? > > Thanks! >
From: Stuart McCall on 19 Jan 2010 08:47 "Peter" <Peter(a)discussions.microsoft.com> wrote in message news:5023B8FA-6191-44EA-AF25-82A41C4D9B40(a)microsoft.com... > Hi all..I want to create a one-to-many relation between: > > Table: A. Field : A (AutoNumber) (Primary Key) > > One to many relation > > Table: B. Field: A (Number) > > Am I thinking wrong here? If I cant Enforce Referential Integrity in this > case should I still create a relation, but without RI? > > Thanks! Yes, that looks correct, so long as Table B has its own primary key field as well as Field A (which is a Foreign key). Also Field A should be of type Long to match the Autonumber in Table A. Given the above, I can't see a reason why you won't be able to establish the relation you want, and be able to enforce RI.
|
Pages: 1 Prev: Referential integrity. AutoNumber… Next: Referential integrity. AutoNumbe r… |