Adding data to child DB

  • Thread starter Thread starter Jason
  • Start date Start date
J

Jason

I am going to create a database to create custom quotes
for customers. I am going to link it to a products
database so that I dont have to reenter the same product
information for each quote I do. I know that I can link
it to the products database and have it pull the
information related to that product....desc, price,
vendor...etc thru the lookup/child database. When I enter
a product ID thats not in the linked database nothing
gets filled in. If I continue thru the form and enter
this data in manually will it add this data to the child
database for future use automatically or do I have to
write some code to have it add this data in so that in
its in the products database. Did I explain this right ??

Jason
 
I am going to create a database to create custom quotes
for customers. I am going to link it to a products
database so that I dont have to reenter the same product
information for each quote I do.
Click to expand...

Jargon alert: A "Database" in Access is the .mdb file, a container for
multiple Tables, Forms, Reports, and other objects. I suspect you are
referring to a quotes Table, and a products Table. If not, please
explain what you are in fact doing - two databases with linked tables,
or what?
I know that I can link
it to the products database and have it pull the
information related to that product....desc, price,
vendor...etc thru the lookup/child database. When I enter
a product ID thats not in the linked database nothing
gets filled in. If I continue thru the form and enter
this data in manually will it add this data to the child
database for future use automatically or do I have to
write some code to have it add this data in so that in
its in the products database. Did I explain this right ??
Click to expand...

If you are storing the product information in the quotes table, as it
appears that you are, YOU ARE ON THE WRONG TRACK.

The Product information should exist in only *one* place: the Product
table. It *should not exist* in the quotes database.

Typically one would have a Combo Box or other such selection tool
bound to the ProductID in the form being used to update the QUotes
table. Typically, if you try to enter a nonexistant Product, you would
use VBA code in the combo box's NotInList event to open a Products
form to enter it.
 
Please excuss my ignorance of database terminology. I
have not played with databases since Alpha 4 for DOS. As
a matter of fact, thats what I am still using and I will
be upgrading to Access 2003.

Anyways, thats what I am talking about is tables not
databases. I have a main quote table. I will link that to
a customer table and a products table. I am not storing
all of the information in the quotes table, just the
product ID that would link it to the products table and
the desc. I am also including the desc in the quotes
table because sometimes I like to override the default
desc and add information about a produt there. In my
current application, I can enter a product id and if its
not in the products table, I can tab over to the fields
that did not get filled in because of the lack of an
entry in the products table, fill in those fields and
when I move off the line that data gets entered into the
products table. I had to write some script to accomplish
this and it I remember is was a pain in the butt. I am
assuming that I can do the same with Access 2003. I could
also use your suggestion of pulling up a form from the
products table if it does not find a match and then I
could enter the information there. I am sure I will find
a way as I always do.

Thanks for your reply and making me use the correct
terminology. If I want to discuss things with others, I
should at least learn the language.

Jason
 
Back
Top