Drop down box to auto populate fields

[sarah.s]

Hi!



I am a novice at best with Access and I'm having a few issues.

I am trying to create a form to find, then amend a record in my assessment table. There are numerous assessments listed for each employee so I need to be able to find a record by selecting the employee and the assessment, then have the rest of the fields auto populate based on these 2 stipulates.

When I go to create a drop box using the 'Find a record on my form based on the value I selected in my combo box' function, I select both the employee and assessment fields to be included. When the combo box is created it just lists numbers instead of their name and assessments.

I have tried many different ways to try and create this form but nothing seems to be working! Please help!

Thanks!

[ssanfu]

See http://www.baldyweb.com/Autofill.htm


Automatically fill in Access text boxes based on a combo box selection
http://www.techrepublic.com/blog/mic...box-selection/


or YouTube https://www.youtube.com/watch?v=rSPS24EfijI

[sarah.s]

Neither of these are working. I've checked the column widths, the bound columns, the number of columns etc all is as it should be. I think nits because there are multiples of the same name and assessments. So there are 10 records that begin John Doe and several assessment ones recorded but there will not be more than one John Doe - Assessment one

[sarah.s]

Am I making sense?

[aytee111]

Not really! This should be a simple scenario - select employee from combobox, requery assessment combobox based on employee, select assessment, filter and requery the form based on these two entries. Both of these comboboxes should be unbound fields.

If the problem is the display of the values in combobox, show us your row source and column count/widths.

[ssanfu]

You could post your dB for analysis......

[Missinglinq]

...When the combo box is created it just lists numbers instead of their name and assessments...

This makes me wonder if these Fields are defined as Lookup Fields at the Table level! If so, have a look at

The Evils of Lookup Fields in Tables

Linq ;0)>