Hello there.



I have this situation we,re working with Powerbuilder 9.0 and SQL Server 7.0
with an original application developed in Powerbuilder 6.5, this mean that
we made the update to 9.0, well after that in some SQL that involve string
field like char or varchar the values were evaluated with double quoted like
this example type in "1","2".



Select * from clients

Where tipo in " 1","2"



Well this syntax generated error because dont recognize del double quote,
now the syntax must use single quoted '1', '2' like this



Select * from clients

Where tipo in '1', '2'.



We want to know what cause this behavior and how to fixed, because the
consequences of this bring to us an extra work to do.. change al the SQL
affected.



We appreciate some advices about this topic.



Thanks in advance.



Eduardo Primera

From Venezuela

Hi Eduardo,

How are you executing the SQL that generates this error? By setting up 
in a DW by using the Modify command or in an EXECUTE IMMEDIATE command? 
I had this problem before with the Modify and it happened because I used 
double quotes on the Modify and also inside the SQL (like 
Modify('Datawindow.Table.Select = "' + ls_sql_statement + '"')). Because 
I used both, SQL scramble the information and generates an error. To fix 
it, I changes the quotes (like Modify("Datawindow.Table.Select = '" + 
ls_sql_statement + "'"))

Thanks,
Mano Bill

eprimera wrote:
> Hello there.
> 
> 
> 
> I have this situation we,re working with Powerbuilder 9.0 and SQL Server 7.0
> with an original application developed in Powerbuilder 6.5, this mean that
> we made the update to 9.0, well after that in some SQL that involve string
> field like char or varchar the values were evaluated with double quoted like
> this example type in "1","2".
> 
> 
> 
> Select * from clients
> 
> Where tipo in " 1","2"
> 
> 
> 
> Well this syntax generated error because dont recognize del double quote,
> now the syntax must use single quoted '1', '2' like this
> 
> 
> 
> Select * from clients
> 
> Where tipo in '1', '2'.
> 
> 
> 
> We want to know what cause this behavior and how to fixed, because the
> consequences of this bring to us an extra work to do.. change al the SQL
> affected.
> 
> 
> 
> We appreciate some advices about this topic.
> 
> 
> 
> Thanks in advance.
> 
> 
> 
> Eduardo Primera
> 
> From Venezuela
> 
> 

Thanks for you reply.

Well this is the problem, the are some SQL in one application that we
recently migrate from Powerbuilder 6.5 to Powerbuilder 9.0 and those SQL
always used the double quoted operator,  just those one that compare string
values (char or varchar), after the migration the sentences that use double
quotes are usesless, this mean that right now the setences require sinlgle
quotes. For example if i create a new datawindows the setences put  the
comparative  values  between single quotes. If i use the ISQ session i get
thesame results.

I dont know exactly if this is a consecuence of the migration, or if in the
preview version of the aplication someone use some aditional setup
information over the conecction of the database.

Well in the aplication were are no using Modify commads or Execute
Immediate. I don,t if these explanation help you to see others point,
because i can't see the cause.. plese any help ,, mean a  lot.

Thanks again for you response..

Eduardo
from venezuela



"Mano Bill" <NO_SPAM_TO_ME_manobill_at_gmail_dot_com> escribi� en el mensaje
news:42ee2f3b@forums-2-dub...
> Hi Eduardo,
>
> How are you executing the SQL that generates this error? By setting up
> in a DW by using the Modify command or in an EXECUTE IMMEDIATE command?
> I had this problem before with the Modify and it happened because I used
> double quotes on the Modify and also inside the SQL (like
> Modify('Datawindow.Table.Select = "' + ls_sql_statement + '"')). Because
> I used both, SQL scramble the information and generates an error. To fix
> it, I changes the quotes (like Modify("Datawindow.Table.Select = '" +
> ls_sql_statement + "'"))
>
> Thanks,
> Mano Bill
>
> eprimera wrote:
> > Hello there.
> >
> >
> >
> > I have this situation we,re working with Powerbuilder 9.0 and SQL Server
7.0
> > with an original application developed in Powerbuilder 6.5, this mean
that
> > we made the update to 9.0, well after that in some SQL that involve
string
> > field like char or varchar the values were evaluated with double quoted
like
> > this example type in "1","2".
> >
> >
> >
> > Select * from clients
> >
> > Where tipo in " 1","2"
> >
> >
> >
> > Well this syntax generated error because dont recognize del double
quote,
> > now the syntax must use single quoted '1', '2' like this
> >
> >
> >
> > Select * from clients
> >
> > Where tipo in '1', '2'.
> >
> >
> >
> > We want to know what cause this behavior and how to fixed, because the
> > consequences of this bring to us an extra work to do.. change al the SQL
> > affected.
> >
> >
> >
> > We appreciate some advices about this topic.
> >
> >
> >
> > Thanks in advance.
> >
> >
> >
> > Eduardo Primera
> >
> > From Venezuela
> >
> >

Are those SQL statements placed inside a datawindow or you placed them 
inside the code?

eprimera wrote:
> Thanks for you reply.
> 
> Well this is the problem, the are some SQL in one application that we
> recently migrate from Powerbuilder 6.5 to Powerbuilder 9.0 and those SQL
> always used the double quoted operator,  just those one that compare string
> values (char or varchar), after the migration the sentences that use double
> quotes are usesless, this mean that right now the setences require sinlgle
> quotes. For example if i create a new datawindows the setences put  the
> comparative  values  between single quotes. If i use the ISQ session i get
> thesame results.
> 
> I dont know exactly if this is a consecuence of the migration, or if in the
> preview version of the aplication someone use some aditional setup
> information over the conecction of the database.
> 
> Well in the aplication were are no using Modify commads or Execute
> Immediate. I don,t if these explanation help you to see others point,
> because i can't see the cause.. plese any help ,, mean a  lot.
> 
> Thanks again for you response..
> 
> Eduardo
> from venezuela
> 
> 
> 
> "Mano Bill" <NO_SPAM_TO_ME_manobill_at_gmail_dot_com> escribi� en el mensaje
> news:42ee2f3b@forums-2-dub...
> 
>>Hi Eduardo,
>>
>>How are you executing the SQL that generates this error? By setting up
>>in a DW by using the Modify command or in an EXECUTE IMMEDIATE command?
>>I had this problem before with the Modify and it happened because I used
>>double quotes on the Modify and also inside the SQL (like
>>Modify('Datawindow.Table.Select = "' + ls_sql_statement + '"')). Because
>>I used both, SQL scramble the information and generates an error. To fix
>>it, I changes the quotes (like Modify("Datawindow.Table.Select = '" +
>>ls_sql_statement + "'"))
>>
>>Thanks,
>>Mano Bill
>>
>>eprimera wrote:
>>
>>>Hello there.
>>>
>>>
>>>
>>>I have this situation we,re working with Powerbuilder 9.0 and SQL Server
> 
> 7.0
> 
>>>with an original application developed in Powerbuilder 6.5, this mean
> 
> that
> 
>>>we made the update to 9.0, well after that in some SQL that involve
> 
> string
> 
>>>field like char or varchar the values were evaluated with double quoted
> 
> like
> 
>>>this example type in "1","2".
>>>
>>>
>>>
>>>Select * from clients
>>>
>>>Where tipo in " 1","2"
>>>
>>>
>>>
>>>Well this syntax generated error because dont recognize del double
> 
> quote,
> 
>>>now the syntax must use single quoted '1', '2' like this
>>>
>>>
>>>
>>>Select * from clients
>>>
>>>Where tipo in '1', '2'.
>>>
>>>
>>>
>>>We want to know what cause this behavior and how to fixed, because the
>>>consequences of this bring to us an extra work to do.. change al the SQL
>>>affected.
>>>
>>>
>>>
>>>We appreciate some advices about this topic.
>>>
>>>
>>>
>>>Thanks in advance.
>>>
>>>
>>>
>>>Eduardo Primera
>>>
>>>From Venezuela
>>>
>>>
> 
> 
> 

eprimera wrote:

> I have this situation we,re working with Powerbuilder 9.0 and SQL Server 7.0
> with an original application developed in Powerbuilder 6.5, this mean that
> we made the update to 9.0, well after that in some SQL that involve string
> field like char or varchar the values were evaluated with double quoted like
> this example type in "1","2".
> 
> 
> 
> Select * from clients
> 
> Where tipo in " 1","2"
> 
> 
> 
> Well this syntax generated error because dont recognize del double quote,
> now the syntax must use single quoted '1', '2' like this

Try SET QUOTED_IDENTIFIER OFF.

Dmitri.

well both case embeded sql in code and some datawindows...

thanks.

Eduardo
from venezuela


"Mano Bill" <NO_SPAM_TO_ME_manobill_at_gmail_dot_com> escribi� en el mensaje
news:42ee4c91@forums-2-dub...
> Are those SQL statements placed inside a datawindow or you placed them
> inside the code?
>
> eprimera wrote:
> > Thanks for you reply.
> >
> > Well this is the problem, the are some SQL in one application that we
> > recently migrate from Powerbuilder 6.5 to Powerbuilder 9.0 and those SQL
> > always used the double quoted operator,  just those one that compare
string
> > values (char or varchar), after the migration the sentences that use
double
> > quotes are usesless, this mean that right now the setences require
sinlgle
> > quotes. For example if i create a new datawindows the setences put  the
> > comparative  values  between single quotes. If i use the ISQ session i
get
> > thesame results.
> >
> > I dont know exactly if this is a consecuence of the migration, or if in
the
> > preview version of the aplication someone use some aditional setup
> > information over the conecction of the database.
> >
> > Well in the aplication were are no using Modify commads or Execute
> > Immediate. I don,t if these explanation help you to see others point,
> > because i can't see the cause.. plese any help ,, mean a  lot.
> >
> > Thanks again for you response..
> >
> > Eduardo
> > from venezuela
> >
> >
> >
> > "Mano Bill" <NO_SPAM_TO_ME_manobill_at_gmail_dot_com> escribi� en el
mensaje
> > news:42ee2f3b@forums-2-dub...
> >
> >>Hi Eduardo,
> >>
> >>How are you executing the SQL that generates this error? By setting up
> >>in a DW by using the Modify command or in an EXECUTE IMMEDIATE command?
> >>I had this problem before with the Modify and it happened because I used
> >>double quotes on the Modify and also inside the SQL (like
> >>Modify('Datawindow.Table.Select = "' + ls_sql_statement + '"')). Because
> >>I used both, SQL scramble the information and generates an error. To fix
> >>it, I changes the quotes (like Modify("Datawindow.Table.Select = '" +
> >>ls_sql_statement + "'"))
> >>
> >>Thanks,
> >>Mano Bill
> >>
> >>eprimera wrote:
> >>
> >>>Hello there.
> >>>
> >>>
> >>>
> >>>I have this situation we,re working with Powerbuilder 9.0 and SQL
Server
> >
> > 7.0
> >
> >>>with an original application developed in Powerbuilder 6.5, this mean
> >
> > that
> >
> >>>we made the update to 9.0, well after that in some SQL that involve
> >
> > string
> >
> >>>field like char or varchar the values were evaluated with double quoted
> >
> > like
> >
> >>>this example type in "1","2".
> >>>
> >>>
> >>>
> >>>Select * from clients
> >>>
> >>>Where tipo in " 1","2"
> >>>
> >>>
> >>>
> >>>Well this syntax generated error because dont recognize del double
> >
> > quote,
> >
> >>>now the syntax must use single quoted '1', '2' like this
> >>>
> >>>
> >>>
> >>>Select * from clients
> >>>
> >>>Where tipo in '1', '2'.
> >>>
> >>>
> >>>
> >>>We want to know what cause this behavior and how to fixed, because the
> >>>consequences of this bring to us an extra work to do.. change al the
SQL
> >>>affected.
> >>>
> >>>
> >>>
> >>>We appreciate some advices about this topic.
> >>>
> >>>
> >>>
> >>>Thanks in advance.
> >>>
> >>>
> >>>
> >>>Eduardo Primera
> >>>
> >>>From Venezuela
> >>>
> >>>
> >
> >
> >