Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Modules / DAO / VBA / April 2008

Tip: Looking for answers? Try searching our database.

IN predicate limit?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
backToASP - 09 Apr 2008 15:33 GMT
I have an application that is Access as a Reporting frontend for an old
FoxPro system - has been running successfully for a couple of years.  There
is a multi select list box with 100+ reps listed (details from linked foxpro
data) - the user is selecting about 35 reps, a date range, and various other
filtering options.  She is getting 'SQL Expression' error - my guess is the
IN predicate string is too long.  The code builds an IN() predicate statement
based on the rep selection.  Is there a limit to the number of items in the
IN statement?

TIA
Stuart McCall - 09 Apr 2008 20:45 GMT
>I have an application that is Access as a Reporting frontend for an old
> FoxPro system - has been running successfully for a couple of years.
[quoted text clipped - 12 lines]
>
> TIA

That depends on the length of each item inbetween the parens. In the past
I've built In()'s with 1000 or so autonumber primary keys, none of which
exceeded 5 chars in length. To pack more in, use a comma as the separator,
not comma space. I've never seen any docs that give the actual limit,
though.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.