[AccessD] Strange limit

Actually there is, when I carved it up into two pieces I placed the second piece into the wrong field.

That said, the query originally was just one big list of 22 values which ran but limited the results 
to 17 values.

John W. Colby
Colby Consulting

Reality is what refuses to go away
when you do not believe in it

On 11/15/2012 2:15 PM, RANDALL R ANTHONY wrote:
> John,
> There's got to be something with your OR clause, as the 17 is the number in the first part of your WHERE clause.  I've got some queries with 20-30 values in an IN clause, work no prob...
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
> Sent: Thursday, November 15, 2012 2:06 PM
> To: Access Developers discussion and problem solving; Sqlserver-Dba
> Subject: [AccessD] Strange limit
>
> I am running the folliowing query:
>
> SELECT     Column_Number, Column_Name
> FROM         _DataDB101.dbo.DB101_ConsumerLayout
> WHERE     (Column_Number IN ('241', '54', '64', '132', '191', '186', '133', '63', '139', '185',
> '129', '151', '201', '147', '127', '113', '261')) OR
>                         (Column_Name IN ('145', '141', '187', '52', '122'))
>
> Notice that I am asking for about 22 values in an In() clause.  SQL Server is cutting it off after
> the 17th value returned.
>
> I never knew there was such a limit though of course there would be some limit.  17 is rather small.
>