After conversion, filter forms will not populate

[Brigitte P]

I successfully (with the help of experts from another newsgroup) converted
some of my databases from A97 to A2002 in a Windows 2000 environment. All
seems to work well after installing the DAO 3.6 library, and compiling my
code in the A2002 version. However, when my users use filter by form
functions (in a form or query), some fields populate with the existing
values when the lookup button is activated, but other will not. It worked
fine in A97.
The only real change in the converted database is that I split the database
in FE and BE, but this shouldn't be the cause. Users now have to type in the
values in some fields while in other fields in the same form or query they
can select. What's going on? Any ideas are appreciated.
Brigitte P.

 

[Brigitte P]

Just a clarification. The "problem" fields populate with 1st row Is Null,
second row IsNotNull but not with the available true values. Maybe this
helps to clarify what the problem is.
Brigitte P

 

[Brigitte P]

I resolved the issue on the filter forms by
selecting "Always" in the Filter Lookup Property of the
field. But how would I do this in a query. Wonder if I
need to go to the Query group.
Brigitte

 

[Joan Wild]

Tools, Options, Edit/Find Tab. The value in the 'Don't display lists with
more than this number of records read:' is affecting this.

If your field contains more than whatever your setting is, then filter by
form will display only is null and is not null.

 

[Brigitte P]

Thanks, I found this in Help, set it to 20000 which is way above what is
possibly in this dbase, but it didn't help. I also read about the index
issue for this, and indexing some fields helped. However, it didn't do
anything to some other fields even though I indexed them in the underlying
tables. This is a query, based on about 5 tables. As I said in my previous
email, I could fix it in the form by changing the filter property of the
field. Maybe I need to rebuild the query, based on one or two subqueries
vs.a query populated by so many tables. What puzzles me is that it worked
fine in A97. It must be a conversion issue - well, maybe.
Any other ideas are appreciated. I also addressed the issue in the query
group.
Brigitte P.