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

3rd try: COMBOBOX not displaying all rows

P: n/a
Sorry..I keep hitting the wrong key and sending the post too soon...

The problem: COMBOBOX not displaying all possible rows.

The RecordSource (generated by SQL view of the Query Builder) is:
SELECT tblTPSTeam.empID, [fname] & " " & [lname] AS ReqAnalyst
FROM tblTPSTeam
ORDER BY tblTPSTeam.lname;

I have gone to Form Design and displayed the RecordSource of the
combobox and then gone to the Build Query Screen and run the query. I
get 35 rows. Then when the application is run and the form is opened
and I try to select a row in the drop-down portion of the combobox, only
around 8 to 10 rows are shown.

Funny thing is ... this used to work. I don't know what has changed.
This is a working database. Please send help quick. Thanks.
Regards,
SueB

*** Sent via Developersdex http://www.developersdex.com ***
Nov 13 '05 #1
Share this Question
Share on Google+
7 Replies


P: n/a
Some more information..

1. Acc 2K
2. I meant RowSource, not RecordSource

Regards,
SueB

*** Sent via Developersdex http://www.developersdex.com ***
Nov 13 '05 #2

P: n/a
If you are seeing only 10 rows out of 35, and the query itself returns the
correct values, you probably need to apply the JET 4 service pack.

You can download it from:
http://support.microsoft.com/gp/sp

If you do not have SP3 for Office 2000, you should apply that also.

It is just possible that you have a ridiculously low value set under:
Tools | Options | Edit/Find | Don't Display ...
but I suspect the JET SP is the real issue, and have seen those symptoms.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Susan Bricker" <sl*****@verizon.net> wrote in message
news:WI****************@news.uswest.net...
Some more information..

1. Acc 2K
2. I meant RowSource, not RecordSource

Nov 13 '05 #3

P: n/a
Allen,

Thank you for the information. Since I am at work I will probably have
to work with some support group here to get the service pack update.
Two more questions ...

1. How do I find out the latest service pack that is loaded on my
machine?
2. I just checked, and the value for the maximum number of rows in a
list to display is currently defined as 1000. For this particular
combobox that number should be sufficient. However, for other
applications, is it acceptable to bump that number up to a VERY LARGE
number? How large a number is acceptable and what are the constraints?

Thanks much.

Regards,
SueB

*** Sent via Developersdex http://www.developersdex.com ***
Nov 13 '05 #4

P: n/a
Susan Bricker <sl*****@verizon.net> wrote in
news:kD****************@news.uswest.net:
Sorry..I keep hitting the wrong key and sending the post too
soon...

The problem: COMBOBOX not displaying all possible rows.

The RecordSource (generated by SQL view of the Query Builder) is:
SELECT tblTPSTeam.empID, [fname] & " " & [lname] AS ReqAnalyst
FROM tblTPSTeam
ORDER BY tblTPSTeam.lname;

I have gone to Form Design and displayed the RecordSource of the
combobox and then gone to the Build Query Screen and run the
query. I get 35 rows. Then when the application is run and the
form is opened and I try to select a row in the drop-down portion
of the combobox, only around 8 to 10 rows are shown.

Funny thing is ... this used to work. I don't know what has
changed. This is a working database. Please send help quick.


Is there, perhaps, a mismatch between the number of columns defined
for the combo box and the number of columns returned by the SQL?

If, for instance, your combo box says there's two columns, but your
SQL returns only one, then you'll see half as many rows, since row
1's data will be in column 1 row 1, and row 2's data will be in 1:2,
etc.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
Nov 13 '05 #5

P: n/a
Locate the file msjet40.dll on your hard disk. There should be one copy
only, and it will typically be in windows\system32. Right-click it, and
choose Properties. On the Version tab, you should see:
4.08.xxx.0
The xxx numbers don't matter, but if you don't see the 8, get SP8 for JET 4.

Access works fine with hundreds of records in the RowSource of a combo, and
even into thousands. If you need to refer to tens of thousands, consider
delay-loading the combo, i.e. don't load the rowsource until the 3rd or 4th
keystroke, so only a few hundred records are actually loaded and it all
happens between keystrokes. There's an example of how to do that in:
Combos with Tens of Thousands of Records
at:
http://allenbrowne.com/ser-32.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Susan Bricker" <sl*****@verizon.net> wrote in message
news:s3****************@news.uswest.net...
Allen,

Thank you for the information. Since I am at work I will probably have
to work with some support group here to get the service pack update.
Two more questions ...

1. How do I find out the latest service pack that is loaded on my
machine?
2. I just checked, and the value for the maximum number of rows in a
list to display is currently defined as 1000. For this particular
combobox that number should be sufficient. However, for other
applications, is it acceptable to bump that number up to a VERY LARGE
number? How large a number is acceptable and what are the constraints?

Nov 13 '05 #6

P: n/a
Susan Bricker wrote:
I have gone to Form Design and displayed the RecordSource of the
combobox and then gone to the Build Query Screen and run the query. I
get 35 rows. Then when the application is run and the form is opened
and I try to select a row in the drop-down portion of the combobox, only
around 8 to 10 rows are shown.


First thought - have you accidentally changed the column count?
--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Whatcha doin?" - Ditto "TIM-MAY!!" - Me
Nov 13 '05 #7

P: n/a
Thank you ALL for the information. I believe that it was a column count
problem. I had an extra column in the column widths but in the query I
had a column with "show" not checked. I reduced the number of columns
and widths and the display works now. For the life of me, I would swear
that this used to work properly. Oh well, at least it works now.

And additional thanks to Allen for the info about displaying large
numbers of rows. I definitely will go look at your example.

Regards,
SueB

*** Sent via Developersdex http://www.developersdex.com ***
Nov 13 '05 #8

This discussion thread is closed

Replies have been disabled for this discussion.