I want to create the dbase with cross ref lists

[Guest]

I have a dbase with Case, Citation, Court, Summary, and some other fields. I
also have a table of topics (categories for cross references). I want to be
able to select any, and all, categories that may apply to a particular case.
For instance, Alexander v. F.B.I. can fall into discoverability,
admissibility, deleted files, and several other categories How can I set up
the table so that I can choose those categories that I want for a particular
case. I tried the junction table but that didn't work. Each case can have
several cross references, and the cross reference can pertain to many cases.
But I want to choose which cross references go with which case.

 

[Duane Hookom]

What didn't work with a junction table? What were the significant fields in
the tables?

 

[Guest]

I used a Case ID and a Topic ID in the junction table. But I couldn't see
the case or the category, only the ID numbers. It also didn't allow me to
choose more than one Cateogory it was either all or none.

 

[Duane Hookom]

Each combination of Case and Topic should create a new record in the
junction table. You should be using forms with combo boxes so you should
never view the ID numbers. If you review the Orders form in the
Northwind.mdb, the order details is like a junction table of OrderID and
ProductID. The subform of the OrderDetails doesn't display the ProductID, it
shows the Product Name.

 

[John Vinson]

I used a Case ID and a Topic ID in the junction table. But I couldn't see
the case or the category, only the ID numbers. It also didn't allow me to
choose more than one Cateogory it was either all or none.

Your problem appears to be that you're trying to use the table
datasheets to view and edit the data. Table datasheets are not
designed for that purpose - they are VERY limited, and best used just
for debugging.

Try using a Form to view and edit your data instead. If you base a
Form on the Cases table, and a Subform on the junction table, you can
put a combo box on the (continuous) Subform; this would be bound to
the TopicID but would display the text topic. This will let you create
(and see simultaneously) multiple topics for a given case, one on each
row of the subform.

The table structure is correct - it appears that you're just not using
all of the Access tools that you need to make use of that correct
structure!

John W. Vinson[MVP]