Sytze, Sys(3055) is what you need I think. "....If you receive the error Insufficient stack space (Error 1308) or SQL: Statement too long (Error 1812), you can increase the FOR and WHERE clause complexity to help prevent the error.
For example, calling TABLEUPDATE( ) for a local table or view that doesn't use key fields generates a long WHERE clause to find the update row. The default number of fields supported in the WHERE clause is 40. If you receive the error SQL: Statement too long (Error 1812), you should either use a key field for the update or increase the complexity of the WHERE clause with SYS(3055). If you use SYS(3055), increase its value to 8 times the number of fields in the table:...." -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sytze de Boer Sent: 22 May 2007 00:30 To: profox@leafe.com Subject: VFP9-SQL Hi folk I have (IMHO) a neat search facility but a puzzling little problem. Very basically, it comes up with a message SQL: statement too long It's ok if the sql string is around 700, but not at 900 Does anyone know what the max is for myfields It goes like; select * from (malias) where at(mysearch,&myfields)>0 Sytze [excessive quoting removed by server] _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
