I want to design a data base which will allow me to imput information and
instead of my having to input the same information a thousand different times
for the same product. I want to be able to track and update dates for some
tables and again, instead of having to go back into every table or form, the
information changes throughout the entire data base for the product i referr
to. If for what ever reason i want to extract 1 or 100 bits of information
from the data base from different tables, i can do so, withouth having, again
to enter the information into one thousand different tables. I also need to
make some comparisons and calculations for prices of product as well. Is it
possible through access? If so how?
--
Just trying to learn.

Access will do that but it sounds like you need to work with someone familiar
in good design to set this up right. Get an Access person to do this for you
in a a few hours, and then you can add to the new structure what you need
beyond that.

Destin Richter
(E-Mail Removed)

"Therapist" wrote:

> I want to design a data base which will allow me to imput information and
> instead of my having to input the same information a thousand different times
> for the same product. I want to be able to track and update dates for some
> tables and again, instead of having to go back into every table or form, the
> information changes throughout the entire data base for the product i referr
> to. If for what ever reason i want to extract 1 or 100 bits of information
> from the data base from different tables, i can do so, withouth having, again
> to enter the information into one thousand different tables. I also need to
> make some comparisons and calculations for prices of product as well. Is it
> possible through access? If so how?
> --
> Just trying to learn.

Umm, you really couldn't have described Access better than your questions
did. This is one of the main reasons Access exists. So we (users) don't
have to continuosly re-enter information.

From your post, however, it seems you are extremely new to Access. And
while Access is easy to learn, I would also suggest you find an Access
professional, in your area, to assist you. You could be looking at a good
length of time before your knowledge catches up to the type of db you are
looking to create.

Good luck.

Sharkbyte



"Therapist" wrote:

> I want to design a data base which will allow me to imput information and
> instead of my having to input the same information a thousand different times
> for the same product. I want to be able to track and update dates for some
> tables and again, instead of having to go back into every table or form, the
> information changes throughout the entire data base for the product i referr
> to. If for what ever reason i want to extract 1 or 100 bits of information
> from the data base from different tables, i can do so, withouth having, again
> to enter the information into one thousand different tables. I also need to
> make some comparisons and calculations for prices of product as well. Is it
> possible through access? If so how?
> --
> Just trying to learn.

On Sat, 11 Jun 2005 16:36:01 -0700, Therapist
<(E-Mail Removed)> wrote:

>I want to design a data base which will allow me to imput information and
>instead of my having to input the same information a thousand different times
>for the same product. I want to be able to track and update dates for some
>tables and again, instead of having to go back into every table or form, the
>information changes throughout the entire data base for the product i referr
>to. If for what ever reason i want to extract 1 or 100 bits of information
>from the data base from different tables, i can do so, withouth having, again
>to enter the information into one thousand different tables. I also need to
>make some comparisons and calculations for prices of product as well. Is it
>possible through access? If so how?

Access is DESIGNED to do exactly what you request.

In a properly normalized set of tables, each table contains
information about one particular type of "entity" - real-life person,
thing or event. Ideally, you would enter information once and once
only, and it would be stored only once in its appropriate table; when
you need that information in the future, you would use a Query linking
that table to some other table containing other related data.

If you are routinely reentering data that you have already entered -
it is very likely that your basic table structures need to be
reexamined!

Care to describe the nature of your data, and the table structure that
you are using for it?

John W. Vinson[MVP]