Re: Designing and Access Questions

I will answer what I can in line:

"Emine" <Emine@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A2F9437F-16F3-490F-9B30-E3681ED0609C@xxxxxxxxxxxxxxxx
I was always confused on the following and I hope that someone can actually
answer a couple of these questions for me. BTW all you Gurus on this
forum
are absolutely fantastic! You guys are great! I've learned so much from
all
your expertise advise. Anyways here are my questions:

1. How do I set-up relationships and what is considered a primary table?

I am not familiar with the term primary table. Do you mean Parent table?
In a one to many relationship, the Parent table is on the One side of the
relationship and the Child table is on the many side. For example, One
Library has Many Books. You set up relationships in the relationship
window. You get to it from the Tools menu.

2. How are the relationships in a table joined and what is the best way to
join tables? I know about the primary key, but for some reason, sometimes
my
relationships do not work.

What do you mean by relationships do not work?
When joining two tables in a one to many relationship, you don't usually
join the primary key fields of both tables. It is usually the primary key
field of the Parent table and another field in the Child table. The field
you join in the Child table has to have the value of it's parent's primary
key field.

3. What is front end and back end?

An Access application should always be split using the database splitter.
The Front end is the application. It will contain forms, modules, macros,
queries, and reports. The backend is the actual "database" part. It
contains the tables, indexes, and relationships. The front end links to
tables in the backend to access the data. When multiple users will be
sharing the database, the back end should be in a shared network folder
where all users have read, write, delete privledges. Each user should have
a copy of the front end on their own computer. It should not be shared.

4. How do you setup a database so that others can use it simultaneously?

This is partially answered in #3, but additionally, when you set your
application options, (Tools, Options, Advanced tab) set the following:
Default open mode - Shared
Default record locking No locks
Check Open databases using record-level locking

5. When Excel spreadsheets are updated (ones that I will be using for
importing) what is the best way to automatically import the updated
information into the database?

Use the TransferSpread*** method or action. You can find details on it in
VBA Help. It is a method when used in VBA and an Action when used in a
macro. The advantage of using VBA is you are able to make it more flexible.
For example, allowing the user to select an Excel file to import at run time
more easily.


If someone can provide these answers for me OMG I would truly appreciate
it.
I am in the processing of actually designing one, have not started, but
will
be tasked to start one.


.