I know sounds fanny, but i got problem with understanding Database design in
Access. I 've read ten times tutorials but nothing helps.
This is content of homework:
All students are enrolled on courses, each student on one course only.

I am not sure if when designing an Accounting Database should there be a
seperate table for Charges and Payments, or rather a single table called
Transactions.
Can anyone comment on Pros and Cons?

Imagine 3 tables: A, B, C, with many-to-many relationships among all pairs
(AB, AC, BC).  Three junction tables can be used to deal with the pairwise
relationships.  Question:  Would a single junction table work that has
primary keys from each of the 3 tables?

i have a template designed by a wizard for my firms library database.  the
name of the main switch board does not suit  me so i want to change the name
of the main switchboard template

Please,
Searching for a reference or help in using CODE to automatically changes the
source SQL database for all my linked tables.   I know how its done manually
but need to do it in the modules.

I am about to embark on writing a book and have an enormous amout of
reference material that I will need to put into a library system with the
ability to cross-reference information and search for key topics/ quotations/
etc as I go.  Has anybody got any good ideas/ solutions?

look for twister logo

I am trying to create a cross reference for my company that will allow my
customers to type in a competitors part number and cross reference it to
mine. I would also like to eventually like for it to link to a catalog page
on my web site. I am wanting to use Access.

I have designed a database with about 10 queries and about 15 reports
depending on one table...however, the twin towers of documentation and
user-friendliness demand I change the table name.
Is there a way I can do this at once and have the change propagate

I am putting together a database for employees.
There are three types E1, E2,E3(at the moment) and they all have huge
amounts of information to collect that's unique to each type.
I am thinking of creating a main table that would contain information common

My Main form is called Quotes and has a Quote ID as the pk.
I the following 4 field table that lists information regarding the quote:
Quote ID
Vehicle ID

I have seem in this list people saying to split the database and put the
back-end on the server and #a copy of the front-end to each one of the user's
stations#. Is that so?
I have my databases splitted and put both database on the server (but

I'm building a Quotation database and have the following question:
My Primary Key in the Quote Table is
"Quote ID"
I will have numerous other tables linked to the Quote ID so what ever I put

I want to require a secondary entry if certain input exists.  Is there a way
to require the user to enter more information if they select that input?

I have a table in access which stores my customer
information.  It allows the customer to enter in a
billing address and a shipping address (if different than
the billing address).  There is a check box which is