Relationship question

I have a database that we use to track circuit status, to
this point we have been using it as a one to one
relationship. Now we need to track what are
called "lowers" a circuit can have as many as 24 lower
circuits. The lowers are already in the maindata table
as single ciruits.
My question is there a way to have a record related to
another record within the same table? Or what would be
the best way to handle this?

Create the second table and include all the fields it needs. Then also
include a field that is of the same format type as the primary key field in
the first table. This field will hold the same value for each record as the
primary key field in the first table for the "parent" record, and will serve
as the link between the two tables.

--

Ken Snell
MS ACCESS MVP

"Lou" wrote in message
...
I have a database that we use to track circuit status, to
this point we have been using it as a one to one
relationship. Now we need to track what are
called "lowers" a circuit can have as many as 24 lower
circuits. The lowers are already in the maindata table
as single ciruits.
My question is there a way to have a record related to
another record within the same table? Or what would be
the best way to handle this?

Ken,
Thank you.
-----Original Message-----
Create the second table and include all the fields it
needs. Then also
include a field that is of the same format type as the
primary key field in
the first table. This field will hold the same value for
each record as the
primary key field in the first table for the "parent"
record, and will serve
as the link between the two tables.

--

Ken Snell
MS ACCESS MVP

"Lou" wrote in
message
...
I have a database that we use to track circuit status,
to
this point we have been using it as a one to one
relationship. Now we need to track what are
called "lowers" a circuit can have as many as 24 lower
circuits. The lowers are already in the maindata table
as single ciruits.
My question is there a way to have a record related to
another record within the same table? Or what would be
the best way to handle this?



.