Character length limit on TSQLQuery:cSelect?

Mahanimann · Mensaje por **Mahanimann** » Vie Nov 30, 2007 12:54 am

I get the following error when compiling with a TSQLQuery:cSelect which is
2360 characters long:
frm_Kunder.xfm (23) Error E0030 Syntax error: "parse error at 'OUTER'"
Line #23 is where the WITH oDataSet .... :cSelect is initiated in the .XFM
file.
The "'OUTER'" word changes when I change the SQL statement. The common
thing is that the word ALLWAYS is around character number 2050. To me this
indicates a read length limit when parsing the :cSelect property. Is it so?
If so, why and/or what can we do about it? If not so, any suggestions on
how to deal with this?
There are no spaces or non-english letters, and therefore no quotemarks
around field- and tablenames, i.e. the query is very plain even if it has
some length. It runs fine in all other SQL editors I have installed (and
that is quite a few). I do use underscore as the first letter in field
aliases (example: CONCAT(t.Number,' ',t.Name) AS _Number_Name), but this
works fine in other shorter SQL statements (in Xailer).
I use v1.66, TMySQLDataSet and TSQLQuery.
Regards,
Paal

YouTube · Mensaje por **ignacio** » Vie Nov 30, 2007 9:26 am

Paal,
Please can you try to set the value of cSelect by code and not in the object
inspector and tell us your results.
Thanks
--
Ignacio Ortiz de Zúñiga
http://www.xailer.com
"Mahanimann" <paaldalen@gmail.com> escribió en el mensaje
news:[email=474f5119@ozsrv2.ozlan.local...]474f5119@ozsrv2.ozlan.local...[/email]
>I get the following error when compiling with a TSQLQuery:cSelect which is
>2360 characters long:
>
> frm_Kunder.xfm (23) Error E0030 Syntax error: "parse error at 'OUTER'"
>
> Line #23 is where the WITH oDataSet .... :cSelect is initiated in the .XFM
> file.
>
> The "'OUTER'" word changes when I change the SQL statement. The common
> thing is that the word ALLWAYS is around character number 2050. To me
> this indicates a read length limit when parsing the :cSelect property. Is
> it so? If so, why and/or what can we do about it? If not so, any
> suggestions on how to deal with this?
>
> There are no spaces or non-english letters, and therefore no quotemarks
> around field- and tablenames, i.e. the query is very plain even if it has
> some length. It runs fine in all other SQL editors I have installed (and
> that is quite a few). I do use underscore as the first letter in field
> aliases (example: CONCAT(t.Number,' ',t.Name) AS _Number_Name), but this
> works fine in other shorter SQL statements (in Xailer).
>
> I use v1.66, TMySQLDataSet and TSQLQuery.
>
> Regards,
> Paal
>

NoName · Mensaje por **NoName** » Vie Nov 30, 2007 9:26 am

Paal,
Please can you try to set the value of cSelect by code and not in the object
inspector and tell us your results.
Thanks
--
Ignacio Ortiz de Zúñiga
http://www.xailer.com
"Mahanimann" <paaldalen@gmail.com> escribió en el mensaje
news:[email=474f5119@ozsrv2.ozlan.local...]474f5119@ozsrv2.ozlan.local...[/email]
>I get the following error when compiling with a TSQLQuery:cSelect which is
>2360 characters long:
>
> frm_Kunder.xfm (23) Error E0030 Syntax error: "parse error at 'OUTER'"
>
> Line #23 is where the WITH oDataSet .... :cSelect is initiated in the .XFM
> file.
>
> The "'OUTER'" word changes when I change the SQL statement. The common
> thing is that the word ALLWAYS is around character number 2050. To me
> this indicates a read length limit when parsing the :cSelect property. Is
> it so? If so, why and/or what can we do about it? If not so, any
> suggestions on how to deal with this?
>
> There are no spaces or non-english letters, and therefore no quotemarks
> around field- and tablenames, i.e. the query is very plain even if it has
> some length. It runs fine in all other SQL editors I have installed (and
> that is quite a few). I do use underscore as the first letter in field
> aliases (example: CONCAT(t.Number,' ',t.Name) AS _Number_Name), but this
> works fine in other shorter SQL statements (in Xailer).
>
> I use v1.66, TMySQLDataSet and TSQLQuery.
>
> Regards,
> Paal
>

Mahanimann · Mensaje por **Mahanimann** » Mar Dic 04, 2007 7:33 pm

Sorry for not responding earlier, I've been out travelling.
> Please can you try to set the value of cSelect by code and not in the
> object inspector and tell us your results.
I added this to frm_Kunder.prg....
METHOD FormInitialize( oSender ) CLASS frm_Kunder
::oDataSet:cSelect := "SELECT ...."
::oDataSet:lOpen := .T.
RETURN Nil
.....and the same kind of error came up. I then did this....
METHOD FormInitialize( oSender ) CLASS frm_Kunder
local cSelect
cSelect := "SELECT .... "
::oDataSet:cSelect := cSelect
::oDataSet:lOpen := .T.
RETURN Nil
.....and the same kind of error came up. I then did this....
METHOD FormInitialize( oSender ) CLASS frm_Kunder
local cSelect
cSelect := "SELECT .... <up to approx 1500 characters>"
cSelect +=" <the rest of the statement, approx. 800 characters>"
::oDataSet:cSelect := cSelect
::oDataSet:lOpen := .T.
RETURN Nil
.....and everything went fine! No errors! So it's the string length itself
that is the problem, not the receiving property/variable?
Paal

Mahanimann · Mensaje por **Mahanimann** » Mar Dic 04, 2007 7:33 pm

Sorry for not responding earlier, I've been out travelling.
> Please can you try to set the value of cSelect by code and not in the
> object inspector and tell us your results.
I added this to frm_Kunder.prg....
METHOD FormInitialize( oSender ) CLASS frm_Kunder
::oDataSet:cSelect := "SELECT ...."
::oDataSet:lOpen := .T.
RETURN Nil
.....and the same kind of error came up. I then did this....
METHOD FormInitialize( oSender ) CLASS frm_Kunder
local cSelect
cSelect := "SELECT .... "
::oDataSet:cSelect := cSelect
::oDataSet:lOpen := .T.
RETURN Nil
.....and the same kind of error came up. I then did this....
METHOD FormInitialize( oSender ) CLASS frm_Kunder
local cSelect
cSelect := "SELECT .... <up to approx 1500 characters>"
cSelect +=" <the rest of the statement, approx. 800 characters>"
::oDataSet:cSelect := cSelect
::oDataSet:lOpen := .T.
RETURN Nil
.....and everything went fine! No errors! So it's the string length itself
that is the problem, not the receiving property/variable?
Paal

Mahanimann · Mensaje por **Mahanimann** » Mar Dic 04, 2007 8:06 pm

Here's a picture of the error.

Attached files

Mahanimann · Mensaje por **Mahanimann** » Mar Dic 04, 2007 8:06 pm

Here's a picture of the error.

Attached files

Mahanimann · Mensaje por **Mahanimann** » Mar Dic 04, 2007 8:44 pm

Ignacio,
The string length problem has disappeared in version 1.8!
After installing v1.8 I cleaned the project, commented out the "set the
value of cSelect by code and not in the
object inspector" and put the SQL statement back into the project
inspector, recompiled and everything worked as it should.
So it is not neccessary to follow this thread anymore.
Regards,
Paal

Mahanimann · Mensaje por **Mahanimann** » Mar Dic 04, 2007 8:44 pm

Ignacio,
The string length problem has disappeared in version 1.8!
After installing v1.8 I cleaned the project, commented out the "set the
value of cSelect by code and not in the
object inspector" and put the SQL statement back into the project
inspector, recompiled and everything worked as it should.
So it is not neccessary to follow this thread anymore.
Regards,
Paal

YouTube · Mensaje por **ignacio** » Mié Dic 05, 2007 9:18 am

Paal,
Great news.
Regards
--
Ignacio Ortiz de Zúñiga
http://www.xailer.com
"Mahanimann" <paaldalen@gmail.com> escribió en el mensaje
news:4755ae2b$[email=1@ozsrv2.ozlan.local...]1@ozsrv2.ozlan.local...[/email]
> Ignacio,
>
> The string length problem has disappeared in version 1.8!
>
> After installing v1.8 I cleaned the project, commented out the "set the
> value of cSelect by code and not in the
> object inspector" and put the SQL statement back into the project
> inspector, recompiled and everything worked as it should.
>
> So it is not neccessary to follow this thread anymore.
>
> Regards,
> Paal
>

NoName · Mensaje por **NoName** » Mié Dic 05, 2007 9:18 am

Paal,
Great news.
Regards
--
Ignacio Ortiz de Zúñiga
http://www.xailer.com
"Mahanimann" <paaldalen@gmail.com> escribió en el mensaje
news:4755ae2b$[email=1@ozsrv2.ozlan.local...]1@ozsrv2.ozlan.local...[/email]
> Ignacio,
>
> The string length problem has disappeared in version 1.8!
>
> After installing v1.8 I cleaned the project, commented out the "set the
> value of cSelect by code and not in the
> object inspector" and put the SQL statement back into the project
> inspector, recompiled and everything worked as it should.
>
> So it is not neccessary to follow this thread anymore.
>
> Regards,
> Paal
>

Stephan Hennekens · Mié Dic 05, 2007 9:20 am

Paal,
are you sure you have version 1.8??
I still have 1.76 and there are no updates available.
Regards,
Stephan
"Mahanimann" <paaldalen@gmail.com> wrote in message
news:4755ae2b$[email=1@ozsrv2.ozlan.local...]1@ozsrv2.ozlan.local...[/email]
> Ignacio,
>
> The string length problem has disappeared in version 1.8!
>
> After installing v1.8 I cleaned the project, commented out the "set the
> value of cSelect by code and not in the
> object inspector" and put the SQL statement back into the project
> inspector, recompiled and everything worked as it should.
>
> So it is not neccessary to follow this thread anymore.
>
> Regards,
> Paal
>

Stephan Hennekens · Mié Dic 05, 2007 9:20 am

Paal,
are you sure you have version 1.8??
I still have 1.76 and there are no updates available.
Regards,
Stephan
"Mahanimann" <paaldalen@gmail.com> wrote in message
news:4755ae2b$[email=1@ozsrv2.ozlan.local...]1@ozsrv2.ozlan.local...[/email]
> Ignacio,
>
> The string length problem has disappeared in version 1.8!
>
> After installing v1.8 I cleaned the project, commented out the "set the
> value of cSelect by code and not in the
> object inspector" and put the SQL statement back into the project
> inspector, recompiled and everything worked as it should.
>
> So it is not neccessary to follow this thread anymore.
>
> Regards,
> Paal
>

Stephan Hennekens · Mié Dic 05, 2007 9:23 am

Oke, I found news in other forum.
Regards,
Stephan
"Stephan Hennekens" <stephan.hennekens@wur.nl> wrote in message
news:47565f47$[email=1@ozsrv2.ozlan.local...]1@ozsrv2.ozlan.local...[/email]
> Paal,
>
> are you sure you have version 1.8??
> I still have 1.76 and there are no updates available.
>
> Regards,
> Stephan
>
> "Mahanimann" <paaldalen@gmail.com> wrote in message
> news:4755ae2b$[email=1@ozsrv2.ozlan.local...]1@ozsrv2.ozlan.local...[/email]
>> Ignacio,
>>
>> The string length problem has disappeared in version 1.8!
>>
>> After installing v1.8 I cleaned the project, commented out the "set the
>> value of cSelect by code and not in the
>> object inspector" and put the SQL statement back into the project
>> inspector, recompiled and everything worked as it should.
>>
>> So it is not neccessary to follow this thread anymore.
>>
>> Regards,
>> Paal
>>
>
>

Stephan Hennekens · Mié Dic 05, 2007 9:23 am

Oke, I found news in other forum.
Regards,
Stephan
"Stephan Hennekens" <stephan.hennekens@wur.nl> wrote in message
news:47565f47$[email=1@ozsrv2.ozlan.local...]1@ozsrv2.ozlan.local...[/email]
> Paal,
>
> are you sure you have version 1.8??
> I still have 1.76 and there are no updates available.
>
> Regards,
> Stephan
>
> "Mahanimann" <paaldalen@gmail.com> wrote in message
> news:4755ae2b$[email=1@ozsrv2.ozlan.local...]1@ozsrv2.ozlan.local...[/email]
>> Ignacio,
>>
>> The string length problem has disappeared in version 1.8!
>>
>> After installing v1.8 I cleaned the project, commented out the "set the
>> value of cSelect by code and not in the
>> object inspector" and put the SQL statement back into the project
>> inspector, recompiled and everything worked as it should.
>>
>> So it is not neccessary to follow this thread anymore.
>>
>> Regards,
>> Paal
>>
>
>