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.

LookUpDisplay Problem

5 posts in Objects Last posting was on 2007-09-13 19:23:18.0Z
neil Posted on 2007-09-05 05:05:44.0Z
Sender: 7126.46de349f.1804289383@sybase.com
From: Neil
Newsgroups: sybase.public.powerbuilder.objects
Subject: LookUpDisplay Problem
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <46de3928.717d.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 4 Sep 2007 22:05:44 -0700
X-Trace: forums-1-dub 1188968744 10.22.241.41 (4 Sep 2007 22:05:44 -0700)
X-Original-Trace: 4 Sep 2007 22:05:44 -0700, 10.22.241.41
Lines: 44
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.objects:9448
Article PK: 736606

Hi,

I have a datawindow with dropdowndatawindow in it. I mean a
column with a property of a dropdownDW. I need to get the
value of this column, i mean the value being displayed, not
the underlying data. So, I created a computed column like
LookUpDisplay(col1). I named it col1_display.

In my script, I put like this:

dw_2.object.col1.primary = dw_1.object.col1_display.primary

the result of this assignment is garbage. I also tried
something like this just to check:

string ls_col1[]
long ll_ctr
ls_col1 = dw_1.object.col1_display.primary

for ll_ctr = 1 to 10
messagebox(" ",ls_col1[ll_ctr])
next
--- the message still contains garbage characters.

I also tried this:
string ls_col1
long ll_ctr
for ll_ctr = 1 to 10
ls_col1 = dw_1.object.col1_display[ll_ctr]
messagebox(" ",ls_col1)
next
--- here it is okay. returns the correct value.
But I dont want to loop the datawindow like this because
this is a lousy one. I have more than 2thousand rows. and
looping like this is not advisable I think.


I dont have problem In PB6.5. This only occurs in PB10.0. Is
there any workaround in this?

Any ideas are much appreciated.

Thanks,
Neil


Christian Freund Posted on 2007-09-07 09:04:22.0Z
From: "Christian Freund" <freundattsfminusdatentechnikdottnospamde>
Newsgroups: sybase.public.powerbuilder.objects
References: <46de3928.717d.1681692777@sybase.com>
Subject: Re: LookUpDisplay Problem
Lines: 59
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: p54847364.dip.t-dialin.net
X-Original-NNTP-Posting-Host: p54847364.dip.t-dialin.net
Message-ID: <46e11416$1@forums-1-dub>
Date: 7 Sep 2007 02:04:22 -0700
X-Trace: forums-1-dub 1189155862 84.132.115.100 (7 Sep 2007 02:04:22 -0700)
X-Original-Trace: 7 Sep 2007 02:04:22 -0700, p54847364.dip.t-dialin.net
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.objects:9458
Article PK: 736616

Hello,

to get the dipsplayed value you can use the describe and evaluate functions.
e.g.
dw_1.DESCRIBE ( "Evaluate('LookUpDisplay(" + ls_column + ")'," + string (
ll_row ) + ")" )

ls_column is the column whith the dddw. ll_row is the row you want to get
the value for.

Christian

<Neil> schrieb im Newsbeitrag news:46de3928.717d.1681692777@sybase.com...

> Hi,
>
> I have a datawindow with dropdowndatawindow in it. I mean a
> column with a property of a dropdownDW. I need to get the
> value of this column, i mean the value being displayed, not
> the underlying data. So, I created a computed column like
> LookUpDisplay(col1). I named it col1_display.
>
> In my script, I put like this:
>
> dw_2.object.col1.primary = dw_1.object.col1_display.primary
>
> the result of this assignment is garbage. I also tried
> something like this just to check:
>
> string ls_col1[]
> long ll_ctr
> ls_col1 = dw_1.object.col1_display.primary
>
> for ll_ctr = 1 to 10
> messagebox(" ",ls_col1[ll_ctr])
> next
> --- the message still contains garbage characters.
>
> I also tried this:
> string ls_col1
> long ll_ctr
> for ll_ctr = 1 to 10
> ls_col1 = dw_1.object.col1_display[ll_ctr]
> messagebox(" ",ls_col1)
> next
> --- here it is okay. returns the correct value.
> But I dont want to loop the datawindow like this because
> this is a lousy one. I have more than 2thousand rows. and
> looping like this is not advisable I think.
>
>
> I dont have problem In PB6.5. This only occurs in PB10.0. Is
> there any workaround in this?
>
> Any ideas are much appreciated.
>
> Thanks,
> Neil


Jamal Ahmad Posted on 2007-09-10 00:02:24.0Z
Reply-To: "Jamal Ahmad" <jamal.ahmad@logicacmg.com>
From: "Jamal Ahmad" <jamal.ahmad@logicacmg.com>
Newsgroups: sybase.public.powerbuilder.objects
References: <46de3928.717d.1681692777@sybase.com>
Subject: Re: LookUpDisplay Problem
Lines: 51
Organization: LogicaCMG
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1807
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1896
NNTP-Posting-Host: 202.53.35.62
X-Original-NNTP-Posting-Host: 202.53.35.62
Message-ID: <46e48990$1@forums-1-dub>
Date: 9 Sep 2007 17:02:24 -0700
X-Trace: forums-1-dub 1189382544 202.53.35.62 (9 Sep 2007 17:02:24 -0700)
X-Original-Trace: 9 Sep 2007 17:02:24 -0700, 202.53.35.62
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.objects:9461
Article PK: 736620

Please Update the latest ebf for PB 10. There was a problem in PB 10 earlier
versions thats you could not access child data window properties thru dot
notations.

<Neil> wrote in message news:46de3928.717d.1681692777@sybase.com...
> Hi,
>
> I have a datawindow with dropdowndatawindow in it. I mean a
> column with a property of a dropdownDW. I need to get the
> value of this column, i mean the value being displayed, not
> the underlying data. So, I created a computed column like
> LookUpDisplay(col1). I named it col1_display.
>
> In my script, I put like this:
>
> dw_2.object.col1.primary = dw_1.object.col1_display.primary
>
> the result of this assignment is garbage. I also tried
> something like this just to check:
>
> string ls_col1[]
> long ll_ctr
> ls_col1 = dw_1.object.col1_display.primary
>
> for ll_ctr = 1 to 10
> messagebox(" ",ls_col1[ll_ctr])
> next
> --- the message still contains garbage characters.
>
> I also tried this:
> string ls_col1
> long ll_ctr
> for ll_ctr = 1 to 10
> ls_col1 = dw_1.object.col1_display[ll_ctr]
> messagebox(" ",ls_col1)
> next
> --- here it is okay. returns the correct value.
> But I dont want to loop the datawindow like this because
> this is a lousy one. I have more than 2thousand rows. and
> looping like this is not advisable I think.
>
>
> I dont have problem In PB6.5. This only occurs in PB10.0. Is
> there any workaround in this?
>
> Any ideas are much appreciated.
>
> Thanks,
> Neil


neil Posted on 2007-09-13 05:59:55.0Z
Sender: c41.46e8c454.1804289383@sybase.com
From: Neil
Newsgroups: sybase.public.powerbuilder.objects
Subject: Re: LookUpDisplay Problem
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <46e8d1db.cd4.1681692777@sybase.com>
References: <46e48990$1@forums-1-dub>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 12 Sep 2007 22:59:55 -0700
X-Trace: forums-1-dub 1189663195 10.22.241.41 (12 Sep 2007 22:59:55 -0700)
X-Original-Trace: 12 Sep 2007 22:59:55 -0700, 10.22.241.41
Lines: 55
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.objects:9471
Article PK: 736626

what build is the latest ebf for PB 10. I have installed the
build 5064 and I think this is the latest.

> Please Update the latest ebf for PB 10. There was a
> problem in PB 10 earlier versions thats you could not
> access child data window properties thru dot notations.
>
> <Neil> wrote in message
> > news:46de3928.717d.1681692777@sybase.com... Hi,
> >
> > I have a datawindow with dropdowndatawindow in it. I
> > mean a column with a property of a dropdownDW. I need to
> > get the value of this column, i mean the value being
> > displayed, not the underlying data. So, I created a
> > computed column like LookUpDisplay(col1). I named it
> col1_display. >
> > In my script, I put like this:
> >
> > dw_2.object.col1.primary =
> dw_1.object.col1_display.primary >
> > the result of this assignment is garbage. I also tried
> > something like this just to check:
> >
> > string ls_col1[]
> > long ll_ctr
> > ls_col1 = dw_1.object.col1_display.primary
> >
> > for ll_ctr = 1 to 10
> > messagebox(" ",ls_col1[ll_ctr])
> > next
> > --- the message still contains garbage characters.
> >
> > I also tried this:
> > string ls_col1
> > long ll_ctr
> > for ll_ctr = 1 to 10
> > ls_col1 = dw_1.object.col1_display[ll_ctr]
> > messagebox(" ",ls_col1)
> > next
> > --- here it is okay. returns the correct value.
> > But I dont want to loop the datawindow like this because
> > this is a lousy one. I have more than 2thousand rows.
> > and looping like this is not advisable I think.
> >
> >
> > I dont have problem In PB6.5. This only occurs in
> > PB10.0. Is there any workaround in this?
> >
> > Any ideas are much appreciated.
> >
> > Thanks,
> > Neil
>
>


Jim O'Neil [Sybase] Posted on 2007-09-13 19:23:18.0Z
From: "Jim O'Neil [Sybase]" <joneil@sybase.com>
Newsgroups: sybase.public.powerbuilder.objects
Subject: Re: LookUpDisplay Problem
Message-ID: <ve3je3l42driju05p67vi2j3dj8lfiiesd@4ax.com>
References: <46e48990$1@forums-1-dub> <46e8d1db.cd4.1681692777@sybase.com>
X-Newsreader: Forte Agent 4.2/32.1118
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 10.18.62.165
X-Original-NNTP-Posting-Host: 10.18.62.165
Date: 13 Sep 2007 12:23:18 -0700
X-Trace: forums-1-dub 1189711398 10.18.62.165 (13 Sep 2007 12:23:18 -0700)
X-Original-Trace: 13 Sep 2007 12:23:18 -0700, 10.18.62.165
Lines: 62
X-Authenticated-User: TeamSybase
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.objects:9472
Article PK: 736630

Well that's the latest for 10; however, you should be updating
maintenance release as well, so the very last EBF for the 10.x series
is actually BUild 9948 of 10.2.1 release earlier this month. FYI,
10.0/10.2 is now end-of-lifed as well.

On 12 Sep 2007 22:59:55 -0700, Neil wrote:

>what build is the latest ebf for PB 10. I have installed the
>build 5064 and I think this is the latest.
>
>
>> Please Update the latest ebf for PB 10. There was a
>> problem in PB 10 earlier versions thats you could not
>> access child data window properties thru dot notations.
>>
>> <Neil> wrote in message
>> > news:46de3928.717d.1681692777@sybase.com... Hi,
>> >
>> > I have a datawindow with dropdowndatawindow in it. I
>> > mean a column with a property of a dropdownDW. I need to
>> > get the value of this column, i mean the value being
>> > displayed, not the underlying data. So, I created a
>> > computed column like LookUpDisplay(col1). I named it
>> col1_display. >
>> > In my script, I put like this:
>> >
>> > dw_2.object.col1.primary =
>> dw_1.object.col1_display.primary >
>> > the result of this assignment is garbage. I also tried
>> > something like this just to check:
>> >
>> > string ls_col1[]
>> > long ll_ctr
>> > ls_col1 = dw_1.object.col1_display.primary
>> >
>> > for ll_ctr = 1 to 10
>> > messagebox(" ",ls_col1[ll_ctr])
>> > next
>> > --- the message still contains garbage characters.
>> >
>> > I also tried this:
>> > string ls_col1
>> > long ll_ctr
>> > for ll_ctr = 1 to 10
>> > ls_col1 = dw_1.object.col1_display[ll_ctr]
>> > messagebox(" ",ls_col1)
>> > next
>> > --- here it is okay. returns the correct value.
>> > But I dont want to loop the datawindow like this because
>> > this is a lousy one. I have more than 2thousand rows.
>> > and looping like this is not advisable I think.
>> >
>> >
>> > I dont have problem In PB6.5. This only occurs in
>> > PB10.0. Is there any workaround in this?
>> >
>> > Any ideas are much appreciated.
>> >
>> > Thanks,
>> > Neil
>>
>>