but it's you who wrote the code to generate filter string, right? So, you can change your code and generate few strings instead of one. One more consideration: generally, there is no necessity to join every table which data should appear on report. Many lookup tables can be represented in REPORT FORM by UDF which will SEEK and RETURN values.

>The filter string can contain any number of individual strings connected with each other using AND conjunction. Considering the maximum possibility, the individual string can be a combination of fields used in all the tables. In that case, I would need to define JOINs between all these tables to implement that filter.
>
>This is for a report.
>
>
>>What prevents you from splitting filter string itself? BTW, what is the purpose of this SELECT, report or grid?
>>
>>>Hi Edward,
>>>
>>>Splitting the SQL will not achieve the purpose as the filter string that can be passed to the SQL, may contain combinations of more than 11 different tables.
>>>
>>>Is there a limitation in VFP, for the number of JOINs one can use?
>>>
>>>Thanks,
>>>Hardik
>>>
>>>>>Hi,
>>>>>
>>>>>I am trying to use several JOINs in a SELECT-SQL, but if I specify more than 9 joins, then VFP gives an error while executing the query. The error (#1805) is as follows:
>>>>>
>>>>>SQL:Too many subqueries.
>>>>>
>>>>>And to top that, I am not using any subqueries at all.
>>>>>
>>>>>Any idea?
>>>>>
>>>>>TIA,
>>>>>Hardik
>>>>
>>>>You can always split you big SELECT to chain of smaller ones, and it will work faster. Start the chain with SELECT which will return smaller recordset.