cannot get bound combo to work
- Thread starter qwertyjjj
- Start date
boblarson
Smeghead
- Local time
- Yesterday, 21:33
- Joined
- Jan 12, 2001
- Messages
- 32,040
Okay 3 things:
1. You didn't include the table so the combo is pretty much useless in the sample.
2. In the combo in the sample you set the recordsource to this:
=dbo_ContactType!ContactDescription
which is wrong. It cannot be that. To be a bound combo you need to have the form to have the applicable fields in its recordsource and then you can just bind the combo by having ContactDescription selected (if that field is in the form's recordsource).
Setting a recordsource for any control with an = sign makes it unbound as it can only display the value associated with whatever follows but it cannot write to anything.
3. The number of columns property needs to be 3 in this case because your ROW source has 3 columns. Then you set the column WIDTHS to be like 1";0";0" which is not normal, but in your case it is because the ID field you have in the rowsource is the second field and usually you set the ID field as the first column. In that case it would be 0";1";0". Also, the BOUND column property should be, IN THIS INSTANCE, 2 instead of 1 because of the same ID location issue.
1. You didn't include the table so the combo is pretty much useless in the sample.
2. In the combo in the sample you set the recordsource to this:
=dbo_ContactType!ContactDescription
which is wrong. It cannot be that. To be a bound combo you need to have the form to have the applicable fields in its recordsource and then you can just bind the combo by having ContactDescription selected (if that field is in the form's recordsource).
Setting a recordsource for any control with an = sign makes it unbound as it can only display the value associated with whatever follows but it cannot write to anything.
3. The number of columns property needs to be 3 in this case because your ROW source has 3 columns. Then you set the column WIDTHS to be like 1";0";0" which is not normal, but in your case it is because the ID field you have in the rowsource is the second field and usually you set the ID field as the first column. In that case it would be 0";1";0". Also, the BOUND column property should be, IN THIS INSTANCE, 2 instead of 1 because of the same ID location issue.
Similar threads
