S
Sally Green
Hi. I came across this problem for the first time over a year ago. And
thought then it had to do with some system configuration at the organisation
that was using a database I had developed.
It has now come up again with a different database, different organisation.
Works ok on my laptop (running XP and Office 2003 SP3) but doesn't work on
the clients laptop (running XP and Office 2003 SP3).
The Problem:
All my combo boxes are Table/Query type, all have several fields in the row
source, and the bound column is always column 1. For the combo boxes that
display just 1 column (column two of the row source, with column one hidden -
width of zero) - these works. However, the combo boxes that display 2
columns (column one and column two of the row source), when the list is
dropped-down the first column (the bound column) is blank. The second column
shows values but you can't select anything in the combo box.
Could you please tell me if this is a known problem and if so whether it is
fixed in Access 2007. Or whether there is a fix or work around available in
Access 2003.
Many thanks
thought then it had to do with some system configuration at the organisation
that was using a database I had developed.
It has now come up again with a different database, different organisation.
Works ok on my laptop (running XP and Office 2003 SP3) but doesn't work on
the clients laptop (running XP and Office 2003 SP3).
The Problem:
All my combo boxes are Table/Query type, all have several fields in the row
source, and the bound column is always column 1. For the combo boxes that
display just 1 column (column two of the row source, with column one hidden -
width of zero) - these works. However, the combo boxes that display 2
columns (column one and column two of the row source), when the list is
dropped-down the first column (the bound column) is blank. The second column
shows values but you can't select anything in the combo box.
Could you please tell me if this is a known problem and if so whether it is
fixed in Access 2007. Or whether there is a fix or work around available in
Access 2003.
Many thanks