Thank you for your time, attention, and info!

I appreciated examples of reasoning process applied to creating a "books and
book passage notes" database. Thanks for the good wishes on my Access study
pursuits.

Best to you.
--
2nd_Stage_User


"Allen Browne" wrote:

Many aspects.

One book can have multiple authors.
One author writes many books.
That needs a junction table to start with, so 3 tables so far:
Book,
Author, and
BookAuthor.

Presumably you make notes that refer to a book and page number. Strictly it
is to a publication an author, because one book may be published multiple
times with different page numbers (e.g. hardback and paperback), so you
have:
Publication
Note

A note is something written by one person on one date, so you may have a
Researcher table as well, if these notes are not just your own.

And so on.

Your other reply says you have just bought some good Access material. That
suggests you are serious about learning this stuff, so all the best as you
spend the next few months covering the basics, doing the practice exerices,
and grasping the design concepts that are the heart of databasing.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"2nd_Stage_User" wrote in message
...
Thank you for taking the time and attention to help me!

Would it be preferable to break the form down into separate interface
parts
instead of making one monster?

I have a database with 4 tables: Main, Details, Subject, and Author. It
is
for storing and retrieving "book and book passage notes" info. "Ideally",
I'd like to be able to input all "book and book passage notes" info, at
one
interface.

However, if the "ideal" is not really feasible, what would you recommend
as
the next best thing?
--
2nd_Stage_User