You sure you don't have code anywhere that resets the RowSource for the
combo, or that the RowSource doesn't have a reference to some control that
limits what's returned?

Signature
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
> Hi Folks - this is weird - heard about others having refresh problems with
> a combo but never experienced this until now.
[quoted text clipped - 13 lines]
>
> Any suggestions gratefully received!
Kahuna - 17 Jul 2007 21:14 GMT
> You sure you don't have code anywhere that resets the RowSource for the
> combo, or that the RowSource doesn't have a reference to some control that
> limits what's returned?
Yep definately sure Douglas, any suggestions?

Signature
Kahuna
------------
>> Hi Folks - this is weird - heard about others having refresh problems
>> with a combo but never experienced this until now.
[quoted text clipped - 13 lines]
>>
>> Any suggestions gratefully received!
>Hi Folks - this is weird - heard about others having refresh problems with a
>combo but never experienced this until now.
[quoted text clipped - 10 lines]
>The scroll bar then appears to have scrolled through the entire table but
>its hasn't!!
Is it possible that the list has not completely loaded yet?
Try adding:
x = Me.combobox.ListCount
to the form's Load event procedure.

Signature
Marsh
MVP [MS Access]
Kahuna - 17 Jul 2007 22:12 GMT
I do believe you fixed it Marshall - Many thanks!

Signature
Kahuna
------------
>
>>Hi Folks - this is weird - heard about others having refresh problems with
[quoted text clipped - 20 lines]
> x = Me.combobox.ListCount
> to the form's Load event procedure.
Kahuna - 17 Jul 2007 22:30 GMT
Ahh - thanks for help guys but it seems there is another part to my
challenge.
I have the combo loading successfully now (thanks all), but I am loading
other text box's based on the other columns in the rowsorce for the combo -
so eg:
=[cboMatTypeDesc].[Column](5) loads the text field with data from column 5
of the combo (or 6 in fact as its 0 based) rowsource (or should).
However this is working sporadically. I have 35 or so fields being populated
in this way and many of them are simply not being read / populated from the
look-up table.
Is there a limit on how many columns there can be in the rowsource for the
combo (I am only displaying 10 - though not consecutively listed).
Is there a more elegant way to do this - I suspect DLookup would be clumsy
and time consuming during run??

Signature
Kahuna
------------
>I do believe you fixed it Marshall - Many thanks!
>
[quoted text clipped - 23 lines]
>> x = Me.combobox.ListCount
>> to the form's Load event procedure.