Blank Combo Box

[sdawson]

There must be a simple explaination to this.
I have a Combo Box based on a query which is blank. The query when run displays the correct data but as the Row Source for the Combo Box, nothing.
Attached is a sample from the db.
Please, someone put me out of my misery.

Ta

 

[GaryPanic]

you have not tied it to the field to store the value

 

[GaryPanic]

ok you need 2 tables one lists your towns
the other table holds the info you want - you have only 1 table holding the info ..

 

[sdawson]

Got it.
It's been a long day and sometimes you can't see the wood for the trees.
I can sleep sound now.
Cheets mate.

 

[GaryPanic]

look at the attached -

1 table holds your towns (and your qry works off that) , the form needs to be tied to a table that will store this value

set this up right in the first place and the wizard actual asks you what do you want to do with the info you have selected ...

 

[missinglinq]

The problem has nothing to do with the OP not having "tied it to a field to store it" nor does it have anything to do with the OP needing a "second table." Gary has ignored the fact that the combobox shows nothing, which is the OP's complaint, and gone off on a tangent that is irrelevent to the problem at hand. You can't make a selection if the combobox shows nothing!

In point of fact, the OP's original database runs just fine for me, as is, which makes me think something else is going! I'm just guessing here, but I suspect that the OP is running v2003 with the infamous SP3 installed. SP3 is buggier than the Great Dismal Swamp! One of the most common bug reported involves comboboxes with disappearing data! The field(s) in the cbo, in the underlying table, have some kind of formatting in place. This is often the simple > used to force UpperCase, which is the case here! Remove any formatting from the fields and things should work short term, but the definitive solution is to install the hotfix for SP3.

Here's a link to Allen Browne's site where you can find the latest news about these bugs, as well a link to the Hotfix:

http://allenbrowne.com/bug-Access2003SP3.html

 

[GaryPanic]

perhaps - but i thought it was a A2000 d/b ?
anway problem solved

 

[missinglinq]

Just because the db is in 2000 file format doesn't mean the OP is running Access 2000, and there's absolutely nothing that you've suggested that will cause a combobox that is showing no data to suddenly start showing data!

 

[sdawson]

Installed the hotfix.
Everything OK now.

Thanx.

 

[missinglinq]

Glad you got ti working!

 

[THANOS]

The field(s) in the cbo, in the underlying table, have some kind of formatting in place. This is often the simple > used to force UpperCase, which is the case here! http://allenbrowne.com/bug-Access2003SP3.html

I had the same issue a couple of weeks before and I didn't realise that is a bug. I thought that it was something I did by mistake. In my case the formatting sign was a "@". I never understood how this ever applied in my table. I got crazy trying to find out why my combo did not show any data. Never happened to me before. Well, now it's all clear thanks to you

P.S. As I noticed there is not such an issue with A2007.

 

[missinglinq]

Version 2007 has enough problems, so the Access Gods decided to spare them this one!