random incomplete query results

  • Thread starter Thread starter FM
  • Start date Start date
F

FM

Hi to all,

on a form I'm filling a "box" (I don't know the english name, is like a
combo without the input selection row) from a table on the same database.
To do that, I'm using the property "RowSource", also to change the ordering
field.

The problem is that, when I'm using the database on a PC with Windows 2000
and Office 2000, "sometime" (exactly! not all the times!) the list on the
box is covering only a fraction of the entire table! After some trials I get
the full list...
The same database, on my PC (XP and Office 2003), is working always
correctly...

One of the sub showing this behaviour is the following:

********
Private Sub cmd_ord_cod_Click()
Elenco_scelta.RowSource = "SELECT Materiali_ele.Cod_CI,
Materiali_ele.........ecc. ecc. ..............."
Elenco_scelta.Requery
Me.Elenco_scelta.SetFocus
End Sub
********

I tried to insert some "DoEvents" without success...
Any thought? Is it a bug?

thanks

Fabio
 
Suggestions:

a) On the box that's giving the incomplete list, check the setting under:
Tools | Options | General.
Particularly, the number of items to include in the list (default=1000), and
the boxes for Show List.

b) If that is not the issue, what service pack is applied to your Office
2000? (In Access, go to Help | About.) You should have at least SP3. Check
that the Win2000 is up to date as well.

I did see this kind of issue several years ago on a very slow network (Win
NT 4 server.)
 
a) On the box that's giving the incomplete list, check the setting under:
Tools | Options | General.
Particularly, the number of items to include in the list (default=1000),
and the boxes for Show List.
Click to expand...

I checked it at it was OK
b) If that is not the issue, what service pack is applied to your Office
2000? (In Access, go to Help | About.) You should have at least SP3. Check
that the Win2000 is up to date as well.
Click to expand...

Is a version with no SP installed... I'll find and install it.
I did see this kind of issue several years ago on a very slow network (Win
NT 4 server.)
Click to expand...

This behaviour is happening also on the machine where the database is, could
it still be caused by a slow network?

Thanks a lot!

Fabio
 
Applying the SPs could fix the problem. A2000 was almost the buggiest
release ever (with the exception of A95.) SP1 fixed 300+ bugs in Access
alone. You *really* need the service pack; ideally, get up to SP3.

Available from:
http://support.microsoft.com/sp/
 
Back
Top