By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,158 Members | 917 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,158 IT Pros & Developers. It's quick & easy.

Freaky combo box

P: 64
I am using access 2003 and I thought that I was very familiar with combo boxes, both created from scratch and with the combo box wiizrd. I am putting the finishing touches on a project today and a combo box goes stupid on me.

Its very simple. the box is supposed to show an employee id number and his name. It now shows the employee id number and a blank column where the name is supposed to be. I checked the properties of the query to show all columns and no unique records. below is the query...what am i missing. One noet, i just migrated to 2003 from 2000.

SELECT tblEmplist.EntryCode, tblEmplist.EMPID, tblEmplist.NAME, * FROM tblEmplist;

Thanks from "I thought I was finished."
Dec 20 '07 #1
Share this Question
Share on Google+
3 Replies


Nathan H
100+
P: 104
I am using access 2003 and I thought that I was very familiar with combo boxes, both created from scratch and with the combo box wiizrd. I am putting the finishing touches on a project today and a combo box goes stupid on me.

Its very simple. the box is supposed to show an employee id number and his name. It now shows the employee id number and a blank column where the name is supposed to be. I checked the properties of the query to show all columns and no unique records. below is the query...what am i missing. One noet, i just migrated to 2003 from 2000.

SELECT tblEmplist.EntryCode, tblEmplist.EMPID, tblEmplist.NAME, * FROM tblEmplist;

Thanks from "I thought I was finished."
Did you check all the formatting properties for the combo box? Like Columns, column width, list width, etc....
Dec 20 '07 #2

missinglinq
Expert 2.5K+
P: 3,532
Sounds like you got the SP3 Blues! If you just moved up to ACC2003, you probably have the latest "upgrade" to this version, SP3, on board. I use the term "upgrade" guardedly, because it's buggier than the Great Dismal Swamp! One of the most common bugs 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. Remove any formatting from the fields and things should work.

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

http://allenbrowne.com/tips.html

Linq ;0)>
Dec 20 '07 #3

P: 64
Sounds like you got the SP3 Blues! If you just moved up to ACC2003, you probably have the latest "upgrade" to this version, SP3, on board. I use the term "upgrade" guardedly, because it's buggier than the Great Dismal Swamp! One of the most common bugs 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. Remove any formatting from the fields and things should work.

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

http://allenbrowne.com/tips.html

Linq ;0)>
You know what...I just did SP3 and guess what, that was the bug. problem sloved. Where do you find all the time to stay up an all this?

Thanks

-Tom
Dec 20 '07 #4

Post your reply

Sign in to post your reply or Sign up for a free account.