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.

DW.NET bugs

2 posts in DataWindow .NET Last posting was on 2004-10-05 17:26:01.0Z
upscale Posted on 2004-10-05 15:50:34.0Z
From: "upscale" <up@scale.com>
Newsgroups: sybase.public.datawindow.net
Subject: DW.NET bugs
Lines: 13
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
NNTP-Posting-Host: 12.32.34.2
X-Original-NNTP-Posting-Host: 12.32.34.2
Message-ID: <4162c2ca$1@forums-1-dub>
Date: 5 Oct 2004 08:50:34 -0700
X-Trace: forums-1-dub 1096991434 12.32.34.2 (5 Oct 2004 08:50:34 -0700)
X-Original-Trace: 5 Oct 2004 08:50:34 -0700, 12.32.34.2
X-Authenticated-User: pbtenbeta
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.datawindow.net:480
Article PK: 124905

1. Stored Procedure update gives object error on dw_1.Update()
2. rowchanged trigger does not always fire unless you click on an editable
item.
3. SQL Server ADO.NET connection gives runtime error of "Does not support
SQL Server yet..." (or something like that)
4. No way to issue SQL commands to a transaction object. Therefore, a 2nd
connection must be created just for this purpose. Yuck.

I am running the latest EBF for DW.NET that was included as part of the
latest PB10 EBF. Is there a newer one? Schedule for fixes? 1.5 beta
availability?


Jim O'Neil [Sybase] Posted on 2004-10-05 17:26:01.0Z
From: "Jim O'Neil [Sybase]" <joneil_at_sybase_dot_com>
Newsgroups: sybase.public.datawindow.net
Subject: Re: DW.NET bugs
Message-ID: <jdl5m0tm4pq9tbusgmb4tg71eo775pcq9d@4ax.com>
References: <4162c2ca$1@forums-1-dub>
X-Newsreader: Forte Agent 2.0/32.652
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Original-NNTP-Posting-Host: joneilw2k.sybase.com
X-Original-Trace: 5 Oct 2004 10:25:58 -0700, joneilw2k.sybase.com
Lines: 45
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 5 Oct 2004 10:25:59 -0700, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 5 Oct 2004 10:26:01 -0700
X-Trace: forums-1-dub 1096997161 10.22.108.75 (5 Oct 2004 10:26:01 -0700)
X-Original-Trace: 5 Oct 2004 10:26:01 -0700, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.datawindow.net:483
Article PK: 124911


On 5 Oct 2004 08:50:34 -0700, "upscale" <up@scale.com> wrote:

>1. Stored Procedure update gives object error on dw_1.Update()

This has been fixed; however, I don't believe it made the recent EBF.

>2. rowchanged trigger does not always fire unless you click on an editable
>item.
This is actually by design and consistent with the way that
PowerBuilder works. I personally find it annoying as well, but I'm
not hopeful for a change coming soon.

>3. SQL Server ADO.NET connection gives runtime error of "Does not support
>SQL Server yet..." (or something like that)
That's not really a bug either. Support for MS Sql Server is coming
though. The challenge here is that ADO.NET has no common mechanism
for obtaining database metadata like ODBC and OLE-DB do, so each
back-end database requires specific tweaking to get the lists of
tables, stored procedures, etc. The decision was made to support the
OLE-DB namespace first since it is general purpose and can be used for
a multitude of databases. Integration of DBMS-specific drivers will
continue. I would agree though that we should make this more clear in
a roadmap.

>4. No way to issue SQL commands to a transaction object. Therefore, a 2nd
>connection must be created just for this purpose. Yuck.
You can issue SQL commands on the System.Data.IDbConnection interface
as you would in any .NET application. Your datawindows can use that
same connection via the Sybase.DataWindow.AdoTransaction object. I
suspect you are using the Sybase.DataWindow.Transaction class, which
is most like what people are used to in PowerBuilder; however, for the
purposes of DataWindow.NET, I'd say you shouldn't use it except in
rare circumstances that the ADO.NET driver is not viable for you.

>
>I am running the latest EBF for DW.NET that was included as part of the
>latest PB10 EBF. Is there a newer one? Schedule for fixes? 1.5 beta
>availability?
I believe we are still looking for a 1.5 beta this quarter and EBFs
are released on a revolving schedule given there are three active
versions of the related PowerBuilder product. I would expect another
EBF in a few weeks, but don't have a definite date for one at this
point. I'll see what I can find out on that though.

>