Autopopulate

[Guest]

When filling in one table with data that is associate with anothe table how
can I make the table that I am manually filling in fillin automatically with
related data? I have the relationships linked on the primarykey of employee
number in main roster and foriegn key in requalification table:2006. Is it
best to use a query and then assocate a form wiht that query and if so how?
I have tried to do that as wellas doing a form with a subform and to no avail
i am still not getting the autopopulate.

 

[Rick Brandt]

When filling in one table with data that is associate with anothe
table how can I make the table that I am manually filling in fillin
automatically with related data? I have the relationships linked on
the primarykey of employee number in main roster and foriegn key in
requalification table:2006. Is it best to use a query and then
assocate a form wiht that query and if so how? I have tried to do
that as wellas doing a form with a subform and to no avail i am still
not getting the autopopulate.

Are you trying to *link and display* related data or *copy* related data? The
latter is the incorrect way to do it most of the time. Unless the related data
is time-sensitive or is being used to provide default values that might be
over-ridden then you should not be copying it to other tables. You should just
use a query or other lookup mechanism to retrieve and display it on form and
reports.

 

[Guest]

I am not sure what you are talking about.

I have one table mainroster with EMPLNUMB, EMPNAME and another table with
the same but one more field, RADCONEXPIRESDATE. As I am filling in the data
for the employee number i want the rest of the employee name to fillin
automatically from the mainroster information, instead of having to type it
in or copy and paste it in. Then all i have to do is fill in the
RADCONEXPIRESDATE. Is this possible?

 

[Steve Schapel]

Judy,

There are a couple of points to make here.

First, the general wisdom of the sages is that the purpose of tables
should be regarded as data storage, and not for human consumption. Data
entry/editing/viewing should always be done via forms. I am not 100%
clear from your post, but if your meaning is that you are entering data
directly into a table, then I urge you to desist.

Second, the EmpName field should not be in more than one table. If you
know the EmplNumb, you automatically know the EmpName, and can always
easily retrieve it via a query whenever you need it. A valid relational
data design would only have the EmplNumb field in the second table, and
not the EmpName.

As regards being able to see the related EmplName when you are working
on your form with data in the second table, there are a number of
approaches that can be taken. Some of them are explained in this article...
http://accesstips.datamanagementsolutions.biz/lookup.htm