View Single Post
  #2  
Old April 26th, 2010, 01:43 AM posted to microsoft.public.access.tablesdbdesign
Steve[_77_]
external usenet poster
 
Posts: 1,017
Default Help... .. Deciding one to many or many to many.. Type..

Hello Ahmed,

It won't hurt a thing to create a junction table now. In fact it is
recommended that you do. If there is the remotest possibility that an item
will belong to more than one category, you have a one-to-many relationship
and need the junction table. Your tables should look like:

TblItem
ItemID
ItemName
other item fields as needed

TblCategory
CategoryID
Category

TblItemCategory
ItemCategoryID
ItemID
CategoryID

You can use a form/subform to enter/edit/delete data. Base the main form on
TblItem and base the subform on TblItemCategory. Set the Link Master and
Link Child properties to ItemID. Use a combobox to enter CategoryID in the
subform. Set the rowsource of the combobox to TblCategory. Set the Bound
Column property to 1, Column Count to 2 and Column Width to 0;2.

If you need one-to-one help, I can help you for a small fee. Contact me.

Steve



"Ahmed" wrote in message
...
Hi,
I am learning in Access 2007.... Through John and Jeff Book......Have
two tables.... e.g. 1. AllItems 2. ItemsCategories
Both has Primary keys .... If Items would be in one of categories..
ItemsCategories Key Would GO in
AllItems as Fk... But.. in Future... if Some items belong to more than one
category then
it would rewuire a Juctional table (e.g. ItemsNCategories)...
Should I make Juctional Table (for unknown Future addition convinience) or
Just use one to many
Relationship... Will it hurt to make juctional Table and Procede.. ?

Second question is.. Should Catagories be added .. Through form Direstly
binding table or Should
Create Query of Table categories and Bind Query to Form..

Many thanks In Advance.. Though very basic question .. will appreciate..
help.

Thanks. Ahmed