Just another system limit bump request:

I can have now much more complex queries in VFP9 (no more error 1845: SQL expression is too complex; and now I can use subqueries) but I still hit sometimes the 8192 characters per query limit (Error 18: Line is too long).
The actual solution is to break the query in more separate queries and join them with an additional SELECT statement. But if others also hit this limit and it is easy to enlarge it to say so 65536 characters, I think that we will see this error more rarely.


Now, it is an immediate necessity,
also why many developers will use ICASE(), easier than IIF(IIF(...).

The VFPT has removed the limit of the 64K of the prg and therefore if it does not increase
to 64K or 16M the limit of a SELECT will come stressed from many.

But I task that will not come elevated,
also why VFP does not have a Query parser with enormous abilities to find isomorphism forms,
invariant algebric set operations and equivalences (like SQL Server),
and therefore query too much complex could become slowest.


Note:
SQLServer has also this limit (8000 characters), but only when executing queries created dynamically (via EXECUTE) (because of the VARCHAR limit acctualy), but it can be circumvented by useing string concatenation like: EXEC('name_of_8000_char_string' + 'another_name_of_8000_char_string')


this is the string literal limit, it is 256 for VFP.

Fabio