Need help with Control Source usage please...

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

Guest

Scenario... there are two fields on a form created from a
table. Both fields are combo boxes which show a unit
number and unit description (i.e P06|Pipe Fitting).
One field shows and uses the Unit number...the other
field shows the same info in reverse (Pipe Fitting|P06)
and uses the Unit Description when selected. Both fields
will auto fill the other field, so if you know the unit
number and enter that, the next field will auto fill with
the unit description and vice a versa. I did this by
designating one field the Control Source on the Data Tab
on the Properties sheet for both fields.

Here is the problem:

I enter data into the form, then I check the Data sheet
view and everything is fine, all fields are filling in
appropriately. HOWEVER...When I view the associated Table
the fields with the designated control source are empty!
Suppose the Unit Number field is the control source for
the Unit Number and the Unit Description field...on the
assicated table the entry for the Unit Number field is
displayed...but the data for the Unit Description field
is empty.

What I need:

Someone should be able to look up the appropriate Unit
Number, enter the number...then the Unit description
field should Auto fill. Both fields should show an entry
in the associated table.

This is a very important project I have undertaken for my
company. I sincerely appreciate any help you may have to
offer. Please feel free to email a responce to
(e-mail address removed) or to post it here so others may have
the benefit of your wisdom.

Regards, James
 
if you have a table, such as

tblUnits
UnitNum
UnitDesc

and you're using that table to offer data entry selections for a field in
another table, via a form, then your form setup sounds fine.
the "other" table should not have a separate unit description field, only a
unit number field. you've already got the description for any given unit
number - in tblUnits. storing the same data in two separate tables violates
table normalization rules and defeats the purpose of using a relational
database model.

hth
 
Back
Top