I have already received some excellent advice from this group regarding my
attempts to understand relational database design so I hope you don't mind
if I seek your help once more.
Briefly, I am trying to build a database in MS Access to track my online
auction activities. Data entry for each item sold takes place over a period
of time: a) the initial placement, b) details of the winning bid, c)Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/information-technology/13766-to-use-relational-not-use-relational.html
despatch data, and so on. Therefore, I need to create forms to handle each
of these procedures with, of course, everything tied into an auction number
and an item name.
I have tried creating several tables with fields pertaining to each section
and using related links back to the auction number/item fields in the firstReference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=13766
table - but with little success.
It came to me, however, that I am doing too much work. Surely creating one
table with all the fields required for all sections and then creating forms
from that would work. Do I really need to bother with related fields and
multiple tables? Surely having one table will enable me to pull the auction
number/iten name fields into each form I create without the hassle of using
My question - finally - is does this sound reasonable or am I missing
something blindingly obvious?
I can see the use of relational databases when dealing with otherwise
'standalone' items like stock lists, customer contacts, etc., but where
tracking something as integral as an auction item is concerened do I need a
You advice, as always, would be very welcome.