Auto populate

Hello All,

The following fields in my database are linked to a combo box so that they
can auto populate:

Name
State
Review Date
Review Total

I now realized that auto populated data is not stored in the field names
above because they were unbound text boxes. So my question is when you are
doing auto populate is there a way to make the information save into he table
so that it can be viewed in my form?

Thank you in advance

On Thu, 29 Oct 2009 13:53:02 -0700, dcrqueens
wrote:


Hello All,

The following fields in my database are linked to a combo box so that they
can auto populate:

Name
State
Review Date
Review Total

I now realized that auto populated data is not stored in the field names
above because they were unbound text boxes. So my question is when you are
doing auto populate is there a way to make the information save into he table
so that it can be viewed in my form?

Thank you in advance

What is "autopopulating"? Where is it autopopulating FROM, and where are you
trying to store it? Are you perhaps trying to store data from one table,
redundantly into another table? If so... you probably shouldn't be doing so!

More details please!
--

John W. Vinson [MVP]

DLookUp("[Member #]","[Committee Report]","[Member Name] = " & [Member Name])

Hello John,

The fields that are auto populating are from a combo box named customer
number. Once the customer number is selected in the form then the Name,State
and Review dates automatically populate. For example for the State field I
use the following in the unbound textbox =Combo.Column(2). The form is based
on a Query with 2 tables joined by the member number:
Table 1 is named Member Report
Table 2 is named Delivery Tracking

At this time I am trying got create a report listing all of the information
that is in the Delivery Tracking table. I have been reading through other
posts on the site and I think I might need to use a DLookUp in the Query that
the report is based on. Do you think that is a better solution?

Thakn you for your help.
"John W. Vinson" wrote:

On Thu, 29 Oct 2009 13:53:02 -0700, dcrqueens
wrote:


Hello All,

The following fields in my database are linked to a combo box so that they
can auto populate:

Name
State
Review Date
Review Total

I now realized that auto populated data is not stored in the field names
above because they were unbound text boxes. So my question is when you are
doing auto populate is there a way to make the information save into he table
so that it can be viewed in my form?

Thank you in advance

What is "autopopulating"? Where is it autopopulating FROM, and where are you
trying to store it? Are you perhaps trying to store data from one table,
redundantly into another table? If so... you probably shouldn't be doing so!

More details please!
--

John W. Vinson [MVP]
.

On Fri, 30 Oct 2009 03:46:01 -0700, dcrqueens
wrote:

DLookUp("[Member #]","[Committee Report]","[Member Name] = " & [Member Name])

Hello John,

The fields that are auto populating are from a combo box named customer
number. Once the customer number is selected in the form then the Name,State
and Review dates automatically populate. For example for the State field I
use the following in the unbound textbox =Combo.Column(2). The form is based
on a Query with 2 tables joined by the member number:
Table 1 is named Member Report
Table 2 is named Delivery Tracking

The Delivery Tracking table should contain the customerID... and NOTHING ELSE
from the Customer table. You're using a relational database; *use it
relationally*!

Relational databases use the "Grandmother's Pantry Principle": "A place - ONE
place! - for everything, everything in its place". If a Review Date refers to
a customer, then that field should be in the customer table ONLY.


At this time I am trying got create a report listing all of the information
that is in the Delivery Tracking table. I have been reading through other
posts on the site and I think I might need to use a DLookUp in the Query that
the report is based on. Do you think that is a better solution?

Base the Report on a Query joining the Member Report table to the Delivery
Tracking table. Pick up the member information from the Member table, and pick
up the delivery tracking information from the Delivery Tracking table. It's
simply *wrong* to store the same information in both tables.
--

John W. Vinson [MVP]