Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

deprecated tsql outer joins Any clues on how to convert dw?

5 posts in DataWindow Last posting was on 2008-04-10 16:26:33.0Z
dw migrate Posted on 2008-04-09 20:02:12.0Z
Sender: 490c.47fd1f7a.1804289383@sybase.com
From: dw migrate
Newsgroups: sybase.public.powerbuilder.datawindow
Subject: deprecated tsql outer joins Any clues on how to convert dw?
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <47fd20c4.4921.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 9 Apr 2008 13:02:12 -0700
X-Trace: forums-1-dub 1207771332 10.22.241.41 (9 Apr 2008 13:02:12 -0700)
X-Original-Trace: 9 Apr 2008 13:02:12 -0700, 10.22.241.41
Lines: 7
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.datawindow:86622
Article PK: 415884

MSSQL 2005 HAS deprecated TSQL outer joins.
We don't want to run in a prior version compatibility mode
because we are using TSQL outer joins in MS SQL 2005 in the
datawindows. IS there anyway we can automatically change
the sql in the dw without going to each one? Note this sql
is not in graphic mode, and it has *= or =* joins which do
not work in 2005.


M. Searer Posted on 2008-04-09 20:21:01.0Z
From: "M. Searer" <nospam@nospam.com>
Newsgroups: sybase.public.powerbuilder.datawindow
References: <47fd20c4.4921.1681692777@sybase.com>
Subject: Re: deprecated tsql outer joins Any clues on how to convert dw?
Lines: 15
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <47fd252d$1@forums-1-dub>
Date: 9 Apr 2008 13:21:01 -0700
X-Trace: forums-1-dub 1207772461 10.22.241.152 (9 Apr 2008 13:21:01 -0700)
X-Original-Trace: 9 Apr 2008 13:21:01 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.datawindow:86623
Article PK: 415882

not if you are using syntax mode.

You will need to rewrite the syntax with ansi left outer join syntax

<dw migrate> wrote in message news:47fd20c4.4921.1681692777@sybase.com...
> MSSQL 2005 HAS deprecated TSQL outer joins.
> We don't want to run in a prior version compatibility mode
> because we are using TSQL outer joins in MS SQL 2005 in the
> datawindows. IS there anyway we can automatically change
> the sql in the dw without going to each one? Note this sql
> is not in graphic mode, and it has *= or =* joins which do
> not work in 2005.


Jason 'Bug' Fenter [TeamSybase] Posted on 2008-04-09 21:11:05.0Z
From: "Jason 'Bug' Fenter [TeamSybase]" <jason.fenter@teamsybase.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
Newsgroups: sybase.public.powerbuilder.datawindow
Subject: Re: deprecated tsql outer joins Any clues on how to convert dw?
References: <47fd20c4.4921.1681692777@sybase.com>
In-Reply-To: <47fd20c4.4921.1681692777@sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <47fd30e9$1@forums-1-dub>
Date: 9 Apr 2008 14:11:05 -0700
X-Trace: forums-1-dub 1207775465 10.22.241.152 (9 Apr 2008 14:11:05 -0700)
X-Original-Trace: 9 Apr 2008 14:11:05 -0700, vip152.sybase.com
Lines: 14
X-Authenticated-User: teamsybase
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.datawindow:86624
Article PK: 415883


dw migrate wrote:
> MSSQL 2005 HAS deprecated TSQL outer joins.
> We don't want to run in a prior version compatibility mode
> because we are using TSQL outer joins in MS SQL 2005 in the
> datawindows. IS there anyway we can automatically change
> the sql in the dw without going to each one? Note this sql
> is not in graphic mode, and it has *= or =* joins which do
> not work in 2005.

Without updating your datawindows, the only thing I can think of is
putting code in the SQLPreview event to parse and reconstruct the SQL as
needed. Hopefully, you can do that in a common ancestor for your
datawindow controls and datastore objects.


"Paul Horan[TeamSybase]" Posted on 2008-04-10 15:47:55.0Z
From: "Paul Horan[TeamSybase]" <phoran AT sybase DOT com>
Newsgroups: sybase.public.powerbuilder.datawindow
References: <47fd20c4.4921.1681692777@sybase.com> <47fd30e9$1@forums-1-dub>
Subject: Re: deprecated tsql outer joins Any clues on how to convert dw?
Lines: 24
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <47fe36ab$1@forums-1-dub>
Date: 10 Apr 2008 08:47:55 -0700
X-Trace: forums-1-dub 1207842475 10.22.241.152 (10 Apr 2008 08:47:55 -0700)
X-Original-Trace: 10 Apr 2008 08:47:55 -0700, vip152.sybase.com
X-Authenticated-User: teamsybase
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.datawindow:86627
Article PK: 415887

The OP stated that his DWs were in graphic format... Isn't there a system
setting that says OuterJoinSyntax='ANSI' or something? I can't recall
exactly off the top of my head....

Paul Horan[TeamSybase]

"Jason 'Bug' Fenter [TeamSybase]" <jason.fenter@teamsybase.com> wrote in
message news:47fd30e9$1@forums-1-dub...
> dw migrate wrote:
>> MSSQL 2005 HAS deprecated TSQL outer joins.
>> We don't want to run in a prior version compatibility mode
>> because we are using TSQL outer joins in MS SQL 2005 in the
>> datawindows. IS there anyway we can automatically change
>> the sql in the dw without going to each one? Note this sql
>> is not in graphic mode, and it has *= or =* joins which do
>> not work in 2005.
>
>
> Without updating your datawindows, the only thing I can think of is
> putting code in the SQLPreview event to parse and reconstruct the SQL as
> needed. Hopefully, you can do that in a common ancestor for your
> datawindow controls and datastore objects.


Jason 'Bug' Fenter [TeamSybase] Posted on 2008-04-10 16:26:33.0Z
From: "Jason 'Bug' Fenter [TeamSybase]" <jason.fenter@teamsybase.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
Newsgroups: sybase.public.powerbuilder.datawindow
Subject: Re: deprecated tsql outer joins Any clues on how to convert dw?
References: <47fd20c4.4921.1681692777@sybase.com> <47fd30e9$1@forums-1-dub> <47fe36ab$1@forums-1-dub>
In-Reply-To: <47fe36ab$1@forums-1-dub>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <47fe3fb9$1@forums-1-dub>
Date: 10 Apr 2008 09:26:33 -0700
X-Trace: forums-1-dub 1207844793 10.22.241.152 (10 Apr 2008 09:26:33 -0700)
X-Original-Trace: 10 Apr 2008 09:26:33 -0700, vip152.sybase.com
Lines: 32
X-Authenticated-User: teamsybase
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.datawindow:86628
Article PK: 415888

"Note this sql is not in graphic mode"

I made that same mistake today in an email. If it *were* in graphic
mode, the setting is on the database profile... Syntax tab. It's
something you'd add to your SQLCA.DBParm property before connecting.

Paul Horan[TeamSybase] wrote:
> The OP stated that his DWs were in graphic format... Isn't there a system
> setting that says OuterJoinSyntax='ANSI' or something? I can't recall
> exactly off the top of my head....
>
> Paul Horan[TeamSybase]
>
> "Jason 'Bug' Fenter [TeamSybase]" <jason.fenter@teamsybase.com> wrote in
> message news:47fd30e9$1@forums-1-dub...
>> dw migrate wrote:
>>> MSSQL 2005 HAS deprecated TSQL outer joins.
>>> We don't want to run in a prior version compatibility mode
>>> because we are using TSQL outer joins in MS SQL 2005 in the
>>> datawindows. IS there anyway we can automatically change
>>> the sql in the dw without going to each one? Note this sql
>>> is not in graphic mode, and it has *= or =* joins which do
>>> not work in 2005.
>>
>> Without updating your datawindows, the only thing I can think of is
>> putting code in the SQLPreview event to parse and reconstruct the SQL as
>> needed. Hopefully, you can do that in a common ancestor for your
>> datawindow controls and datastore objects.
>
>