ComboBox text blank unless you click on it question?

[d9pierce1]

New Profile.zip



Hi all,
I attached a sample db, opens to Company Form (frmCompany),

I just need someone to explain to me about a combo box on my sub form. Subform (sfrmEnity) and is a continous form, has two combos in it and some txt boxes.

What I dont understand is why when i select from the first combo in subform, it stays put so to speak, and when i select from the second combo, and go to next,
it disappears until i click on it again. I know i can put a txt box over it but i just want to understand why I have to do that. The value is stored in table as a separate record
so i just dont understand why it doesnt stay visible after adding a new record/

Can someone please explain this to me or let me know what i am doing wrong with it. I can use the txtbox thing which i would not perfer but i need to understand why
this happens to begin with.

Thanks
Dave

[ranman256]

Check your BOUND COLUMN & column widths

example:
if combo has 2 columns: key, Name
and the combo is bound on col1 ,key
then picking "bob" may not show an answer since its looking for 321 (key)

normally there's no problem with a combo with 1 column.

I just saw your example. The table you are storing data may be keyed to prevent other entries.

[d9pierce1]

greetings,
It picks just fine and if i keep the same selection in the first column it shows them all, if i change the first column to a different selection, then they disapear. the values will only stay visible with the same select in first col

[Micron]

Can't say I've ever seen this before, but here's what doesn't look right:
Your combo rowsource is

SELECT ExtHelperValueID, ExtHelperID, ExtHelperValue FROM tblExtHelperValue WHERE ExtHelperID = cboExtHelper ORDER BY ExtHelperValue;

If the PK for the combo field is ExtHelperID then when I look at your table, that field has 7 values all the same (1). That doesn't seem right. A combo value (when the bound column is the first column) should be going in to the PK field of the related record. I suppose that Access will store the value in the table field for you, but when it's bound column has 7 values, it doesn't know which one to show you. If that's not it, I am stumped for the moment. Regardless, I will offer that it's unusual to bind a combo to a field that can contain multiple values that are the same. In fact, it's not something I'd think to do.

[Micron]

It could also be your combo requery on the GotFocus event. If you must requery because of added values, then GotFocus is not the place to do it. Things seem to work better when your requery is reinstated on the afterUpdate event and disabled on GotFocus, but still not the right place to requery the combo, assuming it ever needs to be done. I still think you have an issue by your combo not being bound to a unique index.

[June7]

cboExtHelperValue is a cascading combobox - its list is dependent on selection in cboExtHelper. It is well-known issue that cascading combobox using alias (displayed info is not value saved) does not work nice on continuous or datasheet form. When the list is filtered, alias data is not available for display on records that contain the filtered ID's. Common topic.

Workaround is to include lookup table in form RecordSource, bind textbox (Locked Yes and TabStop No) to the descriptive text field or use DLookup() expression in textbox to retrieve the descriptive info. Sit textbox on top of combobox.