Combobox record source query results not visible in form

[Guest]

The least complex table in the db Backend is suddenly not "viewable" in
Combobox results of multiple Frontends & forms.
The recordsource queries are always visible in all FE form properties.
"Visible" property is YES throughout every Properties (2 wekks pouring over
code).
No module in BE exists nor FE exists or, should relate to the table or
related controls in the various FEs.

Table comprises: ID(autonumber), Text, the ID again as an appended text
string.

Constantly tweaking the FEs but the disappearance of the query result in the
forms was sudden & universal, unrelated to any changes made in some (because
tweaks were not made in all); each has independent forms/controls affected in
addition to some shared/linked.
I've checked the table in BE, of course. Again, no module at all except
Gobal (IsLoaded); it remains unchanged since BE created 2 years ago. Table
Properties unchanged since creation, as best I can tell.

Worst case: is the a utility that will show when & where changes were made
in code &/or macros? I'll go fish, db-by-db, if needed.
Thanks,

 

[George Nicholson]

You don't say what version of Access you are using. I am going to guess that
its 2003 and that the problems started as soon as SP3 was applied.

What you are seeing is *one* of the known bugs caused by SP3. (Sure explains
sudden and universal, huh?)
http://allenbrowne.com/tips.html

Not 100% sure, but I believe the fix is to open the backend and remove any
formatting applied to the field that displays in the combo. You might check
other posts for something a bit more definitive on that score.

 

[Guest]

Thank you George! Yes, I'm using V. 2003.
I suspected as much re: updates &/or SP3 but thought... well, you
know.[Accustomed to OTHER vendors' apps failing after updates, et al.]

The only formatting in the BE field was "!" as Left Align.
Removal, save, close & reopen (BE & FEs alike) has not produced a working
Combobox in the various FEs. Please keep this thread open & alive pending a
fix of some sort.
I'll respond if reboots are involved in a fix by format - or lack thereof.
Thanks again, very much.

 

[John Spencer]

Another thing to check is to make sure the underlying query has as many
columns showing as the number of columns specified in the combobox
control. The two should agree.


'====================================================
John Spencer
Access MVP 2002-2005, 2007
Center for Health Program Development and Management
University of Maryland Baltimore County
'====================================================

 

[Guest]

John,
Thanks for the check but still, not a fix for this particular snafu. Both
underlying query & combobox have the same column count. Bound column is also
the one I wish I could see on the form.

I've also changed the combobox, related properties & under-query to only the
1 visually-required field/column. Still, nothing visible in the drop-down.
BUT, with original properties returned, if an entry is keyed to match the
Bound Column text string, the After Update event correctly populates a text
box in the form with the second Column(1) of the combobox!
--
CT3or4

Another thing to check is to make sure the underlying query has as many
columns showing as the number of columns specified in the combobox
control. The two should agree.


'====================================================
John Spencer
Access MVP 2002-2005, 2007
Center for Health Program Development and Management
University of Maryland Baltimore County
'====================================================

Thank you George! Yes, I'm using V. 2003.
I suspected as much re: updates &/or SP3 but thought... well, you
know.[Accustomed to OTHER vendors' apps failing after updates, et al.]

The only formatting in the BE field was "!" as Left Align.
Removal, save, close & reopen (BE & FEs alike) has not produced a working
Combobox in the various FEs. Please keep this thread open & alive pending a
fix of some sort.
I'll respond if reboots are involved in a fix by format - or lack thereof.
Thanks again, very much.

 

[Guest]

I don't know if uninstalling Office 2003 and reinstalling (and updatinging
only SP2) is the only fix but it was the one available.

All db Frontends now have working comboboxes.
Thanks again George & John.
And Allen Browne, too.
--
CT3or4

John,
Thanks for the check but still, not a fix for this particular snafu. Both
underlying query & combobox have the same column count. Bound column is also
the one I wish I could see on the form.

I've also changed the combobox, related properties & under-query to only the
1 visually-required field/column. Still, nothing visible in the drop-down.
BUT, with original properties returned, if an entry is keyed to match the
Bound Column text string, the After Update event correctly populates a text
box in the form with the second Column(1) of the combobox!
--
CT3or4

Another thing to check is to make sure the underlying query has as many
columns showing as the number of columns specified in the combobox
control. The two should agree.


'====================================================
John Spencer
Access MVP 2002-2005, 2007
Center for Health Program Development and Management
University of Maryland Baltimore County
'====================================================

Thank you George! Yes, I'm using V. 2003.
I suspected as much re: updates &/or SP3 but thought... well, you
know.[Accustomed to OTHER vendors' apps failing after updates, et al.]

The only formatting in the BE field was "!" as Left Align.
Removal, save, close & reopen (BE & FEs alike) has not produced a working
Combobox in the various FEs. Please keep this thread open & alive pending a
fix of some sort.
I'll respond if reboots are involved in a fix by format - or lack thereof.
Thanks again, very much.