If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
"The setting for the ListRows property must be from 1 through 255"
Hi there
First question, so please be gentle. I have created a database in Access 2007, which all works really well. However, for some of my queries, when I run them, give me the error in the title. In some of my queries the error comes up once, other queries the error occurs up to seven times. I have deleted the fields one by one to see which fields cause the error (as there are some lookups in the tables) and the error can be caused by both the lookup fields, as well as other fields with no lookups. I have checked the ListRows property for all the Lookup fields in the query, and in all cases the setting is the default of 16. There are some queries with lookups which do not generate the error. The error is number 2144, but is not much discussed elsewhere on the web. Many thanks for your help. |
#2
|
|||
|
|||
"The setting for the ListRows property must be from 1 through 255"
I don't know if that is as 2007 bug or not because I haven't tried 2007 yet;
however, avoid the use of lookup tables in any version. -- Dave Hargis, Microsoft Access MVP "Nick Pullar" wrote: Hi there First question, so please be gentle. I have created a database in Access 2007, which all works really well. However, for some of my queries, when I run them, give me the error in the title. In some of my queries the error comes up once, other queries the error occurs up to seven times. I have deleted the fields one by one to see which fields cause the error (as there are some lookups in the tables) and the error can be caused by both the lookup fields, as well as other fields with no lookups. I have checked the ListRows property for all the Lookup fields in the query, and in all cases the setting is the default of 16. There are some queries with lookups which do not generate the error. The error is number 2144, but is not much discussed elsewhere on the web. Many thanks for your help. |
#3
|
|||
|
|||
"The setting for the ListRows property must be from 1 through
Hi Klatuu
There are reports of this in Access 2003 on the web, but no discussion of it. Perhaps your advice not to use lookups is wise, so I wonder if it's worth the day or so to rewrite the tables? Cheers Nick "Klatuu" wrote: I don't know if that is as 2007 bug or not because I haven't tried 2007 yet; however, avoid the use of lookup tables in any version. -- Dave Hargis, Microsoft Access MVP |
#4
|
|||
|
|||
"The setting for the ListRows property must be from 1 through 255"
Klatuu wrote:
I don't know if that is as 2007 bug or not because I haven't tried 2007 yet; however, avoid the use of lookup tables in any version. Assuming here that you meant "lookup fields IN tables". Lookup tables are found in just about every database of any complexity. -- Rick Brandt, Microsoft Access MVP Email (as appropriate) to... RBrandt at Hunter dot com |
#5
|
|||
|
|||
"The setting for the ListRows property must be from 1 through
Yes, I did mean lookup fields in tables. That is what the OP was asking
about. I believe it would be worth the time for the OP to remove the lookups from the fields and create stand alone lookup tables. -- Dave Hargis, Microsoft Access MVP "Rick Brandt" wrote: Klatuu wrote: I don't know if that is as 2007 bug or not because I haven't tried 2007 yet; however, avoid the use of lookup tables in any version. Assuming here that you meant "lookup fields IN tables". Lookup tables are found in just about every database of any complexity. -- Rick Brandt, Microsoft Access MVP Email (as appropriate) to... RBrandt at Hunter dot com |
Thread Tools | |
Display Modes | |
|
|