Re: Associating records in same table.

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

TryIt,

Yes that is what we both are suggesting BUT now the concern is the size of
your database. Have you run compact and repair? How big is your database?

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

"tryit" <tryit.ca@xxxxxxxxx> wrote in message
news:a1edec10-37f8-44fe-934a-3d5c8d525e40@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Jul 27, 11:08 am, KARL DEWEY <KARLDE...@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:
You need the ID_Record to be primary key. Use a matching field for your
'See_Also' field (PK - Autonumber, FK - number long integer).

Open the Relationship window, put the table twice in the window (Access
adds
a sufix of '_1' to the second instance). Click on the primay key field of
the first instance and drag to the 'See_Also' field of the second
instance.
Select Referential Integerity and Cascade Update.
Use a form/subform to display Item/See_Also's. When you select a record
using a combo box to the subform it will automatically insert the Item's
ID
to the See_Also record.
An item can have multiple See_Also but a record can only be 'seen' by one
item. If you need more than one then that is where you would need a
junction
table.

Hi Karl.

It sounds like both you and Gina are suggesting that, if I want to
have an association between one record and multiple records in the
same table, that I would need to set up a junction table between two
instances of the same table in the Relationships window. Is that the
way it would work?

Unfortunately, I don't think I can modify the primary key at this
point. I have tried that before and I get a warning saying access
will not allow that since the db is too big. Is that really
necessary?

Thanks,
TI



.

Relevant Pages

  • Re: Relationships. Does anyone use them?
    ... You have the niftiest tools on your Web site! ... See http://www.QBuilt.com for all your database needs. ... I recreated the view in the Relationship window within a PDF ...
    (comp.databases.ms-access)
  • Re: Double Data Entry
    ... > Are you suggesting that I have two tables in the database for each table?. ... >> matching and you can put them into the transaction table. ...
    (microsoft.public.sqlserver.programming)
  • Re: Relationships. Does anyone use them?
    ... If I have EmpId in Employees, and EmpID in table Orders, if I add ... Relationship window and set relationships? ... Sounds like you've never done any formal database design? ...
    (comp.databases.ms-access)
  • Re: Relationships. Does anyone use them?
    ... If I have EmpId in Employees, and EmpID in table Orders, if I add ... Relationship window and set relationships? ... Sounds like you've never done any formal database design? ...
    (comp.databases.ms-access)
  • Re: Relationships. Does anyone use them?
    ... why do I need to add 2 tables in the Relationship window and set relationships? ... If you do not care to "go in into the relationships window to set the relationship" you are, quite simply, going to fail badly any relational database course. ... When a database application gets large and widely used, the following is an example of what happens that simply screams for the lowest level constraints to be used. ... You really need to go over this in detail, because right now I can tell you, no offence intended and with the greatest of respect, that you are NOT DOING RELATIONAL DATABASE DESIGN WORK at present. ...
    (comp.databases.ms-access)