Automatic copy of data from one table to another?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am relatively inexperienced with using Access. I do
not know if it is possible to do this, but here is what I
would like to do:
I have two tables, one named Vendors and one named
Vouchers. Vendors contains names of stores and suppliers
as well as addresses and other contact information and
even payment terms. Vouchers will contain mostly Purchase
information, dates and amounts, that will be keyed in by
the user on a case by case basis. However, the Voucher
table also needs several pieces of information contained
in the Vendor table, which would not be practical for the
user to key in every time a voucher had to be made.
I have been able to use a query to display Vendor Names
and City.(City is important because purchases are made
from suppliers with the same name in different Cities)
Once the user selects a Vendor name, the Vendor name from
the Vendor table is copied to the Voucher table, but I
need this one selction to cause several other pieces of
information to be copied to other fields automaticly.
Is this possible? If so, How? Thanks. (e-mail address removed)
 
If I understand what you want, and I may not, then you are exactly where
you want to be. You DON'T want to copy data from one table to another when
you can use that data right where it is. Having the same data in two or
more tables is not just bad design slowing down the database and making it
larger than needed, but it almost guarantees that when there is a change,
say a new telephone number, you will only get one changed and the other will
still be wrong.

Joining the two tables so you can use the information in both at the
same time is the way to go.
 
I am relatively inexperienced with using Access. I do
not know if it is possible to do this, but here is what I
would like to do:
I have two tables, one named Vendors and one named
Vouchers. Vendors contains names of stores and suppliers
as well as addresses and other contact information and
even payment terms. Vouchers will contain mostly Purchase
information, dates and amounts, that will be keyed in by
the user on a case by case basis. However, the Voucher
table also needs several pieces of information contained
in the Vendor table, which would not be practical for the
user to key in every time a voucher had to be made.
Click to expand...

But you're using a relational database. Use it relationally!

It is NOT necessary nor desirable to store the Vendor information in
the voucher table AT ALL. It would be redundant; you can simply create
a Query joining the two tables, if the Voucher table contains the
VendorID. You can also display the vendor information on a Form or
Report without having it stored in the voucher table!
 
Back
Top