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.

DDDW in reports

4 posts in DataWindow Last posting was on 2008-07-24 21:37:09.0Z
Todd Dake Posted on 2008-07-24 13:24:08.0Z
From: Todd Dake <todd.dake@primarysolutions.net>
Subject: DDDW in reports
Newsgroups: sybase.public.powerbuilder.datawindow
User-Agent: 40tude_Dialog/2.0.15.1
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <fi7im7ugbisg$.c1ki3da95ifg$.dlg@40tude.net>
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Date: 24 Jul 2008 06:24:08 -0700
X-Trace: forums-1-dub 1216905848 10.22.241.152 (24 Jul 2008 06:24:08 -0700)
X-Original-Trace: 24 Jul 2008 06:24:08 -0700, vip152.sybase.com
Lines: 11
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.datawindow:87444
Article PK: 416699

I would just like to get some feedback on the practice of using dddw within
reports for table lookups.

When a co-worker mentioned that our reports were dependent upon a number of
dddw objects I questioned the practice of using them for this purpose. It
is my contention that it would be much better to join in the tables with
the display columns or use a sub-select to get the display values. I am
wondering if there is any compelling reason to modify existing reports that
use dddw for table lookups. Performance issues perhaps?

Thanks Todd


"Jason 'Bug' Fenter [TeamSybase]" <NO_SPAMMING_jason.fenter_ Posted on 2008-07-24 16:06:49.0Z
From: "Jason 'Bug' Fenter [TeamSybase]" <NO_SPAMMING_jason.fenter_@_teamsybase.com>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
Newsgroups: sybase.public.powerbuilder.datawindow
Subject: Re: DDDW in reports
References: <fi7im7ugbisg$.c1ki3da95ifg$.dlg@40tude.net>
In-Reply-To: <fi7im7ugbisg$.c1ki3da95ifg$.dlg@40tude.net>
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: <4888a899$1@forums-1-dub>
Date: 24 Jul 2008 09:06:49 -0700
X-Trace: forums-1-dub 1216915609 10.22.241.152 (24 Jul 2008 09:06:49 -0700)
X-Original-Trace: 24 Jul 2008 09:06:49 -0700, vip152.sybase.com
Lines: 24
X-Authenticated-User: teamsybase
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.datawindow:87446
Article PK: 416702

Here's my $0.02:

Look-up lists are great for data entry. For reports, I prefer getting
the actual values from the database.
1) You have a datawindow in memory for each column that has a DDDW edit
style. It's *NOT* for each row, so the performance hit isn't that major,
but it's something.
2) If you want to add run-time sorting to your reports, you have to use
LookUpDisplay() instead of just sorting on the column itself.
3) You eliminate any possible problems with saving reports to a file.

Todd Dake wrote:
> I would just like to get some feedback on the practice of using dddw within
> reports for table lookups.
>
> When a co-worker mentioned that our reports were dependent upon a number of
> dddw objects I questioned the practice of using them for this purpose. It
> is my contention that it would be much better to join in the tables with
> the display columns or use a sub-select to get the display values. I am
> wondering if there is any compelling reason to modify existing reports that
> use dddw for table lookups. Performance issues perhaps?
>
> Thanks Todd


"Jerry Siegel [TeamSybase]" <jNOsSPAMsiegel Posted on 2008-07-24 16:20:11.0Z
From: "Jerry Siegel [TeamSybase]" <jNOsSPAMsiegel@yahoo!.com>
Newsgroups: sybase.public.powerbuilder.datawindow
References: <fi7im7ugbisg$.c1ki3da95ifg$.dlg@40tude.net> <4888a899$1@forums-1-dub>
Subject: Re: DDDW in reports
Lines: 42
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4888abbb$1@forums-1-dub>
Date: 24 Jul 2008 09:20:11 -0700
X-Trace: forums-1-dub 1216916411 10.22.241.152 (24 Jul 2008 09:20:11 -0700)
X-Original-Trace: 24 Jul 2008 09:20:11 -0700, vip152.sybase.com
X-Authenticated-User: TeamSybase
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.datawindow:87447
Article PK: 416703

If you have a table with a lot of rows being retrieved but few values
actually used, or the same table is used for multiple columns, a join is
probably the way to go. Once a value is retrieved with a join it probably
stays in the DBMS buffers and doesn't need to be read again, and each
occurrence of a DDDW must be separately retrieved (that could be avoided
with a retreive to a datastore and ShareData). The example I'm thinking of
was a Medicare form that had 7 possible diagnosis codes, with a table of
1500 possible values.

"Jason 'Bug' Fenter [TeamSybase]"

<NO_SPAMMING_jason.fenter_@_teamsybase.com> wrote in message
news:4888a899$1@forums-1-dub...
> Here's my $0.02:
>
> Look-up lists are great for data entry. For reports, I prefer getting the
> actual values from the database.
> 1) You have a datawindow in memory for each column that has a DDDW edit
> style. It's *NOT* for each row, so the performance hit isn't that major,
> but it's something.
> 2) If you want to add run-time sorting to your reports, you have to use
> LookUpDisplay() instead of just sorting on the column itself.
> 3) You eliminate any possible problems with saving reports to a file.
>
>
> Todd Dake wrote:
>> I would just like to get some feedback on the practice of using dddw
>> within
>> reports for table lookups.
>>
>> When a co-worker mentioned that our reports were dependent upon a number
>> of
>> dddw objects I questioned the practice of using them for this purpose.
>> It
>> is my contention that it would be much better to join in the tables with
>> the display columns or use a sub-select to get the display values. I am
>> wondering if there is any compelling reason to modify existing reports
>> that
>> use dddw for table lookups. Performance issues perhaps?
>>
>> Thanks Todd


"John Olson [Team Sybase]" <john.olson Posted on 2008-07-24 21:37:09.0Z
From: "John Olson [Team Sybase]" <john.olson@nospam_teamsybase.com>
Newsgroups: sybase.public.powerbuilder.datawindow
References: <fi7im7ugbisg$.c1ki3da95ifg$.dlg@40tude.net>
Subject: Re: DDDW in reports
Lines: 28
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.3138
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4888f605@forums-1-dub>
Date: 24 Jul 2008 14:37:09 -0700
X-Trace: forums-1-dub 1216935429 10.22.241.152 (24 Jul 2008 14:37:09 -0700)
X-Original-Trace: 24 Jul 2008 14:37:09 -0700, vip152.sybase.com
X-Authenticated-User: TeamSybase
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.datawindow:87450
Article PK: 416706

my 2 cents....

It's a minor issue. For large lookup tables it's almost always better to
join. For smaller ones there may not be enough of a performance cost to be
noticeable. With complex reports sometimes it's nice to simplify them a bit
by using DDDWs rather than joins to get some values. I usually do the
join...

John

"Todd Dake" <todd.dake@primarysolutions.net> wrote in message
news:fi7im7ugbisg$.c1ki3da95ifg$.dlg@40tude.net...
>I would just like to get some feedback on the practice of using dddw within
> reports for table lookups.
>
> When a co-worker mentioned that our reports were dependent upon a number
> of
> dddw objects I questioned the practice of using them for this purpose. It
> is my contention that it would be much better to join in the tables with
> the display columns or use a sub-select to get the display values. I am
> wondering if there is any compelling reason to modify existing reports
> that
> use dddw for table lookups. Performance issues perhaps?
>
> Thanks Todd